[00:10] erratic: nothing wrong with faster speeds [00:10] but it doesn't necesarily help :) [00:11] for some reason i seem to get faster lan 10gbe performance with linux 4.3 over linux 4.2. [00:11] but i'm still curious why linux 4.2 dips :) [00:12] but yeah, hardware is only side of the equation you have software etc too, which can greatly impact performance. [00:13] like the old default retransmit time of 3 seconds meant if you lost one of your initial packets you easily wait an extra 3 seconds for a short (say 4k) document. [00:14] but especially with smaller files stuff like that can make much more difference than link speed. [03:11] *** jpalmer_ has quit IRC (Ping timeout: 276 seconds) [03:12] *** jpalmer has joined #arpnetworks [07:09] *** shafire has joined #arpnetworks [07:10] hi [07:10] hi [07:10] can I use the ips from the ipv4 /29 subnet also for other vps? [07:35] *** ziyourenxiang has joined #arpnetworks [08:00] *** ziyourenxiang has quit IRC (Quit: Leaving) [08:33] shafire: yes [08:34] shafire: yup [08:34] obviously only here (well you could tunnel, but that'd be so slow) [08:35] mnathani_: but those foundry switches still do 4096 active vlans; that's why i chose them actually. Nothing else in the price range did that. [08:39] happy festivus! [08:41] mercutio: you can default route with just 2000::/3 ? man, ya learn something new every day... [08:42] now i'm gonna read up on vxlan too... [10:08] mkb: up_the_irons: can I also bridge the ips? [10:09] shafire: whatever you can do on the same broadcast domain should work [10:09] I am looking for following setup: internet VM1 (pfSense [firewall]) private network VM2 (some linux) [11:43] Yes you can [11:43] (Speaking as someone that has stuff behind an OpnSense VM on an ARP dedicated server [11:44] ) [11:44] (of course pfSense wouldn't be "eth") [11:49] how is opensense? [11:50] and what do you mean with "eth"? [11:50] how is your setup? [11:51] On BSDs, there is no "eth" driver. Depending on the VM setup, you'll either have em or vio. [11:51] Opnsense is great [11:52] (nb: not a typo, there are only 2 'e' in Opnsense) [11:53] And my setup is a standard bridged configuration with Opnsense sitting on the public side, performing bridging+filtering (no NAT) to a private VLAN. [11:59] thats what I want [11:59] had you pfsense on your radar too? or directly opnsense? [12:00] I've used pfSense for upwards of a decade :P I'm actually moving away from it to Opnsense. [12:13] you normally only have eth0 [12:14] well on vps's. [12:14] oh, so you're creating a vlan for eth1 bryce. [12:15] QinQ, baby [12:15] yeh qinq is a nice idea [12:16] i prefer openbsd for firewall over freebsd myself. [12:20] pfsense seemed pretty nifty for "just working" when i tried it though [12:21] And Opnsense continues that "just works"-ness [12:21] i wouldn't think you'd change if that wasn't the case :) [12:22] I love OpenBSD and use it extensively. But for certain scenarios, I need a point-and-click UI I can point less-advanced individuals at. [12:22] yeah [12:22] if using command line and vim etc pf on openbsd is nicer [12:22] and there's less crap [12:22] freebsd reminded me of slackware when i first used it [12:22] with all this dialog stuff and redundant stuff you don't need installed by default [12:22] Not to mention updates/maintenance are a bit simpler - click the update button rather than worrying about what's going to break. [12:22] pfsense i suspect gets rid of a lot of that at least. [12:23] pfSense is based off NanoBSD ;) (which is FreeBSD with all the crap stripped out) [12:23] @wiki NanoBSD [12:23] FreeBSD :: FreeBSD is a free Unix-like operating system descended from Research Unix via the Berkeley Software Distribution (BSD). Although for legal reasons FreeBSD cannot use the Unix trademark, it is a direct descendant of BSD, which was historically also called "BSD Unix" or "Berkeley Unix". The first version of FreeBSD was released in 1993, and today FreeBSD is the most widely used... http://en.wikipedia.org/wiki/FreeBSD [12:24] (FreeBSD v6 introduced "NanoBSD utility") [12:24] (https://www.freebsd.org/doc/en/articles/nanobsd/howto.html for those so inclined) [12:25] and private lan is between vps possible? [12:25] cannot find it on the page and the faq is currently not accessable [12:27] the faq isn't accessible? [12:28] normally all of your traffic is on one vlan, and you can communicate between vps's but it's over a single shared interface on each vps. [12:29] so you can create tunnels back to one vps, or like brycec was saying you could create a vlan. [12:29] yeah, not accessible: ping support.arpnetworks.com PING tenderapp.com (192.228.96.20): 56 data bytes Request timeout for icmp_seq 0 [12:29] maybe it's only me, who knows [12:29] support.arpnetworks.com is working for me [12:30] both with http and with ping [12:31] loads for me too [12:31] i suppose linking to http://support.arpnetworks.com/kb/vps/are-private-ip-addresses-available-for-vps-to-vps-communication won't work for you then [12:31] lol [12:31] no, not working [12:31] Short Answer [12:31] Yes [12:31] can you do a traceroute? [12:31] Long Answer [12:31] That's what she said!! [12:31] VPS' belonging to the same account are grouped into the same private VLAN. As such, you may assign any RFC 1918 private address to your interfaces. They will not conflict with any other customer. [12:31] Additionally, since the VPS' belong to the same private VLAN, using private addresses for VPS to VPS communication is not necessary. In fact, you can communicate between VPS' using their public IPs and since the traffic will not leave your VLAN, you will not be billed for the traffic. [12:32] BryceBot: no [12:32] Oh, okay... I'm sorry. 'Long Answer' [12:32] somewhere in voxility.net [12:32] Drop the traceroute in a pastebin to share [12:32] hmm support.arpnetworks.com is actually hosted with tenderapp [12:33] i think voxility is some kind of anti-ddos thing, and my route is going via any2ix so may bypass [12:33] http://pastebin.com/Uxnaz7tC [12:34] it worked 2-4h ago [12:34] oh voxility is your provider? [12:35] what country are you in? [12:35] UA [12:36] heh i don't have anywhere near there to test from [12:37] but when i try tracing from various places a lot of routes seem to go over he.net, so i wonder if you can get to www.he.net [12:38] he.net works [12:38] hmm [12:40] https://www.voxility.com/shop/connectivity/internet/looking-glass?hostname=support.arpnetworks.com [12:40] that's kind of nifty, not that it's working. [12:41] cute [12:41] " 4.|-- FILTER-DDoS" [12:43] do you have another location you can use it from? [12:47] yeah, I have a backup provider here [13:09] brycec: thanks for the information [13:09] the looking glass gives an error on all destinations or not? [13:13] I tried support.arpnetworks.com and arpnetworks.com - only support.arpnetworks.com gave an error, and from all sources. [13:38] because it doesn't even seem to leave voxiility's network, i'd suggest to try asking voxility why it isn't working [15:00] *** toeshred has quit IRC (Ping timeout: 272 seconds) [15:02] *** toeshred has joined #arpnetworks [19:22] *** dfshjkl has joined #arpnetworks [19:22] *** erratic has quit IRC (Read error: Connection reset by peer)