[03:30] *** sga0_ has quit IRC (Read error: Connection reset by peer) [06:18] *** sga0 has joined #arpnetworks [10:34] *** xales has joined #arpnetworks [11:49] *** sga0_ has joined #arpnetworks [11:53] *** sga0 has quit IRC (Ping timeout: 246 seconds) [11:57] *** medum has quit IRC (Ping timeout: 246 seconds) [11:59] *** medum has joined #arpnetworks [13:08] *** SpaceDum1 has quit IRC (Ping timeout: 255 seconds) [13:08] *** SpaceDump has joined #arpnetworks [13:11] quiet in here. [13:13] "yeah... a little TOO quiet" [13:17] :) [13:19] *** SpaceDump has quit IRC (Ping timeout: 244 seconds) [13:20] *** SpaceDump has joined #arpnetworks [14:36] BryceBot: yes [14:36] Okay! twss! ':)' [14:41] :) [14:41] hmm? [14:41] i dunno how brycebot works [14:51] @google nexus 6 [14:51] 1,260,000 total results returned for 'nexus 6', here's 3 [14:51] Nexus 6 release date, news and rumors | News | TechRadar (http://www.techradar.com/us/news/phone-and-communications/mobile-phones/nexus-6-release-date-news-and-features-1232946) 13 hours ago ... Nexus 6 release date, news and rumors - All the latest on the Nexus 6, and if you believe the rumors we're in for a giant phone from Motorola. [14:51] Nexus 5 (16GB, Black) - Devices on Google Play (https://play.google.com/store/devices/details/Nexus_5_16GB_Black?id=nexus_5_black_16gb&hl=en) Real life doesn't fit in 4” x 6”, so Nexus 5 comes with Photo Sphere. Create the effect of an immersive 360° view that no traditional camera can match. When you ... [14:51] Motorola Nexus 6 - Full phone specifications (http://www.gsmarena.com/motorola_nexus_6-6604.php) Motorola Nexus 6 Android smartphone. Announced 2014, October. Features 3G, 5.96″ AMOLED capacitive touchscreen, 13 MP camera, Wi-Fi, GPS, Bluetooth. [14:52] 1440 x 2560 pixels, 5.96 inches (~493 ppi pixel density) [14:52] That's what she said!! [14:52] BryceBot: no [14:52] Oh, okay... I'm sorry. '1440 x 2560 pixels, 5.96 inches (~493 ppi pixel density)' [14:57] mercutio (and mnathani): It's bayesian learning [14:57] :) [14:57] twss? [14:57] That was 50% what she said. ':)' [14:58] I love when it's hard [14:58] twss? [14:58] That was 92.63% what she said. 'I love when it's hard' [14:58] twss [14:58] Okay! twss! 'I love when it's hard' [14:58] twss? [14:58] That was 92.77% what she said. 'I love when it's hard' [15:00] Bryce: i meant how to trigger it [15:00] the new samsung 840 evo firmware update is out. [15:00] Say something >97% [15:01] (or is it 96?) [15:01] i wish samsung made updates easy on linux. [15:03] mercutio: ooh thanks for the reminder [15:06] lol their software tells me I have the latest firmware [15:07] static: it's only in the performance restoration tool atm [15:08] which takes ages to run, i'm running it on my windows box atm. [15:08] it rewrites all teh data or something, but it needs available space, so it's doing some remap or something. [15:08] :o [15:08] magician wasn't showing me the update either, but it may be some caching thing. [15:08] yeah [15:09] i'm wondering if linux will like me running the restoration tool plugged into windows box. [15:09] i hate having to use the windows box to do firmware updates. [15:09] i really wish they'd add linux support. [15:09] i'm using mdadm/zfs. [15:09] so i'm wondering if i can get a firmware update done, and kill the drive readd. [15:10] mdadm means you can just unplug the drive and it'll rewrite everything, but zfs is more intelligent than that. [15:10] also their progress bar sucks. it got to 80% pretty quick, and then it's been between 80 and 86% for longer than it was up to 80% [15:12] but oh well somehow should be resolvable. it was kind of disconcerting when i used to get 1gb/sec then it went down to less than 200mb/sec [15:14] ah i have two EVO drives in separate machines, no RAID [15:14] its gonna be annoying to update the one in the NUC [15:14] there's actually an iso boot thingy. [15:14] which runs dos and so on. [15:14] which you can probably get going on a usb stick. [15:14] yeah [15:15] i just thought that may be more problematic than stickign in windows box. [15:15] maybe i should try that. [15:15] they're not even listing the new firmware other than restoration tool on their site yet though [15:15] http://www.samsung.com/global/business/semiconductor/minisite/SSD/us/html/support/downloads.html [15:15] under performance restoration is what i used [15:15] oh that's not even on iso [15:18] i dunno if raid on ssd is overkill, but one of them has been dropping out of array occassionally, and it's the same one. [15:18] i was running swap striped rather than on raid, and linux really doesn't like it when swap is unavailable. [15:18] but it doesn't actually crash, just applications crash. [15:20] 89% [15:21] so i imagine update is on the over an hour side [15:33] mercutio: I dont see the update on ther website [15:34] Samsung 840 EVO that is [15:34] under firmware restoration till it lists the firmware [15:34] oh sweet it finished [15:35] now what [17:44] *** dj_goku has quit IRC (Remote host closed the connection) [17:50] If you are trying to establish an Internet connection using BGP, what kind of interconnect between the providers must first be present? [17:52] Any sort of IP interconnect [17:53] Typically RFC1918 [17:53] (because why waste public addresses and possible routing headaches) [17:54] would those RFC1918 ever show up in traceroutes? [17:54] Yes [17:54] You can see a 10. address tracerouting out of ARP sometimes [17:54] thats the OpenBSD box, correct? [17:55] 2 s7.lax.arpnetworks.com (208.79.88.135) 1.385 ms 1.359 ms 1.334 ms [17:55] 3 10.10.10.6 (10.10.10.6) 1.273 ms 1.264 ms 1.244 ms [17:55] 4 any2ix.coresite.com (206.72.210.41) 1.232 ms 1.576 ms 1.756 ms [17:55] That's in the peering with any2ix [17:55] unrelated to the OpenBSD box [17:56] so the any2 side would also have an RFC1918 within that same segment as the 10. [17:56] or that is the any2ix side, but you get the idea [17:57] While I'm no expert ( up_the_irons would be best person to explain ARP's routing)... basically s7 has a bunch of interfaces, one for each interconnect peer, each interface has a private address and a route to the upstream peer's router [17:57] fiber I would assume? [17:58] mnathani: no, the 10.10.10.5/30 is between s7.lax and r1.lax (which is the .6) [17:58] (my bad, sorry) [17:58] no worries brycec [17:58] I'd assume copper, since 10GbE copper is pretty cheap. But I'm just guesing [17:58] *guessing [17:59] it's r1.lax that carries all the peer traffic [17:59] I remember seeing flickr images of fiber runs [17:59] yes, data center porn [17:59] <3 data centre porn [17:59] who doesnt? [17:59] better than real porn [18:00] sometimes [18:00] Most spouses, for starters :p [18:00] lol up_the_irons [18:00] ;) [18:01] so do ARP <> other Transit, or Peers BGP go over RFC1918 Address Space? [18:01] hardly aanyone uses rfc1918 space to reach others. [18:01] as it means that traceroutes don't show [18:01] people usually block responses from rfc1918 addresses into their own network [18:02] no, i just have a couple RFC1918 addresses between our own equipment (why waste a perfectly good public /30? ;) [18:02] (oh I was totally wrong, my bad) [18:02] up_the_irons: for pretty traceroutes! [18:02] indeed, it *does* make the traceroutes better [18:02] brycec: np [18:02] it's normal to use /30s to interconnect to other providers, but it can vary who's ip address space is used. [18:02] some people alternate. [18:03] some people assume the other end can't maintain reverse lookups properly so just decide to use their own ip's. [18:03] I guess it depends on who wants mroe control over PTR records [18:03] s/mroe/more [18:03] I guess it depends on who wants more control over PTR records [18:03] mnathani: all my transits and peers do not use rfc1918 address space [18:03] mnathani: you can delegate sometimes too [18:04] but yeah, it varies a bit [18:04] s/who's/whose/ [18:04] it's normal to use /30s to interconnect to other providers, but it can vary whose ip address space is used. [18:04] up_the_irons: are you 129.250.198.185 for connecting to ntt? [18:05] it can be hard to tell sometimes which ip hits inside the network [18:05] mercutio: yes [18:05] 129.250.198.185 is their side [18:05] so yaeh, that in itself is weird. [18:05] 129.250.198.186 is mine [18:05] That's what she said!! [18:05] oh [18:06] i thought it was other way around [18:06] but yeah that makes sense. [18:06] usually the provider has the lower number [18:06] so yeah that looks like ntt ip [18:06] up_the_irons: yeah. [18:06] but sometimes it's the other way around [18:06] sometimes [18:06] i used to always use 192.168.1.254 as a gateway address on home networks [18:06] then i found everyone using 192.168.1.1 [18:07] i usually use gateway high, but some people usually use gateway low. [18:07] I use .254 for that very reason :D [18:07] my home network is a /16 with gw at 10.10.10.10 [18:07] heh. [18:07] Because idiots may bring a .1 onto the network and risk fucking shit up [18:07] well i have a /29 with high too [18:07] Or just to avoid bad programs that assume a gateway at .1 [18:07] i've actually got 192.168.1.13 as my gateway atm [18:08] bryce.. or sensible people may bring an adsl modem onto the network or such [18:08] .251 and .252 are my gateways, with .254 as the carp'd address :D [18:08] and want to reconfigure it [18:08] mercutio: There is that too sometimes, lol [18:08] when using dhcp it doesn't really matter what the address is [18:09] Indeed, indeed. [18:09] speaking of annoying things, why does coresite show all of it's hosts with the same dns name [18:10] s/it's/its/ [18:10] speaking of annoying things, why does coresite show all of its hosts with the same dns name [18:10] heh [18:10] (speaking of annoying things :P) [18:10] mercutio: How is the ARP lg coming along? [18:10] That's what she said!! [18:10] twss? [18:10] i was thinking possessive. [18:10] BryceBot: no [18:10] That was 96.82% what she said. 'mercutio: How is the ARP lg coming along?' [18:10] Oh, okay... I'm sorry. 'mercutio: How is the ARP lg coming along?' [18:10] mnathani: it's working, but incomplete. [18:11] mercutio: you were thinking it, but you didn't write the possessive form [18:11] What, why isn't that something "she" would say? :P [18:11] brycec: my typing/thinking/whatever is pretty messy sometimes :) [18:12] mnathani: we have r1.lax and s7.lax routes in the lg, still need to hook up s1.lax and ipv6 (s3.lax) [18:12] k, cool [18:16] is anyone from canada in here? [18:16] yup [18:16] ahh. [18:16] i'm canadian... not technically from canada though [18:16] lol [18:17] If you are wondering *.*.149.228 is me [18:17] heh [18:17] yeah figured [18:17] was going to see if anyone figured out where it was. [18:18] will it eventually get the wildcard ARP SSL Cert? [18:18] probably not? [18:18] i wouldn't myself. [18:18] That's what she said!! [18:18] as it's another place for the ssl cert security to leak. [18:18] and it really shouldn't need to be encrypted. [18:19] and if proxypassing for it, then it would rely on web server working. [18:19] and looking glasses can be handy wehn things are semi-broken. [18:20] what do you thinko of it mnathani ? [18:20] Its quick [18:20] compared to other looking glasses [18:21] yeah that's what i thought [18:21] but I guess that cos theres no traffic hitting it really [18:21] also cos it's not using perl [18:21] it's c code [18:21] and BGP sessions to the VPS [18:21] right [18:21] rather than forward queries to a router [18:21] yeah actually quagga is so much quicker than ciscso [18:22] for route servers [18:22] for the ones with telnet [18:22] this one wont support telnet will it? [18:24] i don't think so [18:24] that would be pretty cool [18:27] surprised that bryce didn't pipe up [18:27] That's what she said!! [18:27] I didn't? [18:27] and try the looking glass. [18:27] mercutio: Why am I piping up here? [18:28] Is the lg up yet? [18:28] mnathani found it :) [18:28] And if so, what's the address? [18:28] lol [18:28] guess :) [18:28] * brycec found it too [18:28] Ewww why is this ipv4 only? [18:28] haha [18:29] Guess that explains why my cmd=ping6 failed [18:29] it won't be ipv4 only for long [18:29] i knew someone would complain about ipv4 only hah [18:29] we haven't hooked up ipv6 yet [18:29] * brycec is the preeminent complainer about lack of ipv6 [18:31] hmm i reckon icmp traceroute would be better [18:33] I wonder why show ip bgp as doesnt work for AS25795 [18:34] I wonder why a traceroute to 174.136.103.130 fails miserably [18:34] (my arp vps) [18:34] i don't think 25795 advertisements are included atm [18:34] i think UDP trace being blocked. [18:35] yeah you're blocking udp traceroute and icmp traceroute works [18:35] i wonder if it's easy to change that [18:35] Am I? Hm [18:35] lots of people do [18:35] I can traceroute and traceroute -I from home just fine [18:36] you may have an allow on from your ip? [18:36] Oh wait, my home IP is whitelisted, lol [18:36] yeah [18:36] could have something to do with s1.lax not hooked up yet [18:36] bgplg.h: { TRACEROUTE, "-ASl", NULL } }, \ [18:36] IN=eth0 OUT= MAC=52:54:00:27:23:74:00:0d:65:ab:c8:bf:08:00 SRC=208.79.88.163 DST=174.136.103.130 LEN=40 TOS=0x00 PREC=0x00 TTL=1 ID=36118 PROTO=UDP SPT=36114 DPT=33438 LEN=20 [18:37] (blocked packet) [18:37] Sorry for the false alarm :) [18:37] hah no write permissions [18:40] try now [18:41] bam worked [18:41] yeah i modified the code [18:41] YOU HACKER [18:41] jsut to add -I in [18:42] it's beter overall. [18:42] i did it for traceroute6 too [18:42] but can't tes tthat. [18:42] lol how the first hop has higher latency than my VPS [18:42] yeah cisco [18:42] mercutio: you could use ::1 :P [18:42] ::1 will work with or without icmp [18:43] www.arpnetworks.com has the same issue [18:43] but it seems to work with and without -I on ipv6 [18:45] what's your hostname bryce? [18:46] vps3.cobryce.com [18:46] yeah -I fixes it for ipv6 too [18:47] * brycec notes some ipv6 hits [18:47] so should be good to go [18:49] twss [18:49] Okay! twss! 'so should be good to go' [18:51] y'know, the traceroute updates bit by bit so much better than most of the looking glasses. [18:52] most show huge chunks of information, but it basically shows things as they're happening [18:54] whats a query I can request to show all prefixes originating from a certain AS ? [18:54] source-as [18:55] i wonder if the timeout should be bumped up too for hops that don't respond [18:55] cool, crazy fast response [18:55] i'd kind of like to see mtr added. [18:55] Winter is coming, it's getting colder... Time to start using more monitors (which happen to put off a good chunk of heat) :D [18:55] heh my pva monitor gets so hot [18:56] but newer ones don't really use that much power [18:57] Mine don't use that much power, but there's still plenty of heat from them. IR therm reads around 100F on the screen surface [18:59] my dehumidifier warms my room up a little. [18:59] i was using heater a bit before, but dehumidifer actually seems more useful to me. [19:00] heh [19:00] I avoid running a heater at all costs [19:01] for cost reasons? :) [19:01] Feels like I've lost the battle [19:01] mercutio: Hmmm more like principle [19:01] I have all this tech that puts of heat [19:01] i used to never use heaters. [19:01] I should be able to stay warm by it [19:01] i'd even sleep with the window open in winter. [19:01] but my health seems to prefer having some heat now days. [19:01] I did that back when I lived in AZ... [19:02] and to me health is more important than principle :) [19:02] cos it sucks being sick. [19:03] * brycec doesn't get sick easily, much less from the cold [19:03] apparently original reasons for using udp rather than icmp for traceroute was about icmp needing higher privileges on unix [19:04] brycec: i was like that too! [19:04] damnit, why can't i be like that again. [19:04] Because you're an old man now? [19:04] actually i think for me it's more about wet and cold together. and i'm in a wetter place. [19:04] like dry cold doesn't phase me as much [19:19] why do some routes look like: I 202.28.12.0/24 208.79.88.135 100 289 2914 4651 7470 7470 7470 7470 7470 58806 58806 58806 58806 58806 58806 58806 i [19:19] uhh [19:19] i'll lookup that route [19:19] it doesn't paste well :) [19:19] you mean with so many damn prepends? [19:20] yes, the prepends [19:20] well it's just as basd here [19:20] flags destination gateway lpref med aspath origin [19:20] I*> 202.28.12.0/24 202.49.71.55 100 0 17746 17746 4610 4826 38082 7470 58806 58806 58806 58806 58806 58806 58806 i [19:20] * 202.28.12.0/24 202.49.70.165 100 0 23655 23655 4648 2914 4651 7470 7470 7470 7470 7470 58806 58806 58806 58806 58806 58806 58806 i [19:20] so yeah blame AS58806 [19:21] i assume the reason is because it's in asia, and they're trying to keep traffic to close places when they can [19:22] the 7470 thing seems to be about normal load shifting though [19:23] ie 38082 is preferred over 4651 [19:23] and it looks like thailand. [19:23] with 190 msec ping from nz, so not too bad routing from here [19:24] I see [19:24] and 230 from arp [19:24] hmm [19:24] i dunno what's normal for thailand [19:24] i've seen more than 200 from nz before though [19:26] erk [19:26] that ntt route from here goes via hong kong [19:26] ntt around singapore actually kidn of sucks. [19:27] surprisingly so considering they're japanese based. [19:27] but i think it's cos they have some of their own transit links, and wnat to use those because they're cheaper. [19:34] makes sense now [19:37] cool. [20:23] *** acf_ has quit IRC (Quit: leaving) [20:24] Is true that just because you peer with someone, you need not advertise all your routes? [20:25] *** acf_ has joined #arpnetworks [20:25] I am looking at an Amazon route: I 205.251.221.0/24 208.79.88.135 100 0 3356 3549 16509 i [20:25] which is being preferred via Level 3 even though Amazon is a peer apparently? [20:29] yeah you don't have to advertise all of your routes [20:29] often people will advertise local routes but not remote routes. [20:29] so they don't have to carry traffic [20:30] yeah see that is ages away. [20:31] but 216.137.44.0 is local [20:32] it's worse than it seems [20:32] amazon aren't even advertising san jose routes [20:33] but yeah it's pretty much up to them what they advertise. [20:33] only 4 routes I see [20:33] and all with pings of like 1 msec? [20:34] out of a potential 400 [20:34] 205.251.228.0 is an example of san jose [20:34] but it may just be near there [20:36] could it also be because they have cloud type services and want the Ips as portable as possible [20:37] only updating prefixes with major transit providers? [20:37] i doubt it [20:37] they just don't want to carry traffic across the country [20:37] they why peer in the first place? [20:38] s/they/then [20:38] then why peer in the first place? [20:38] well the expectation is that you peer in multiple locations [20:38] so you carry traffic as close as possible to them, then they don't have to carry traffic [20:38] it's the lowest cost for them that way [20:38] and then the same thing is meant to happen in reverse. [20:38] so they carry traffic as close to you as possible, then offload it onto you [20:39] which is all good if people play by the rules [20:39] but some people try and offload traffic as soon as they can [20:39] so that they don't have to carry the traffic [20:39] but that means user experience can be compromised. [20:39] it's hot potato vs cold potato routing if you want to read about it [20:40] http://en.wikipedia.org/wiki/Hot-potato_and_cold-potato_routing [20:40] Knock that off you jackass, mercutio [20:40] thanks [20:40] whats up with BryceBot [20:41] he doesn't like me :) [20:42] google and facebook seem to try to bring traffic into their network asap [20:42] but it can actually work out worse. [20:42] like they will bring traffic in then send it to a data centre ages away [20:43] like my facebook seems to go to east coast, but come in at fb on west coast. [20:43] it says frc [20:43] dunno what location that is [20:43] @iata frc [20:43] FRC: Not a valid IATA. [20:43] hmm it goes from sjc to frc [20:43] sjc is obvious [20:43] maybe it's a city [20:44] fremont,ca ? [20:44] i dobut it [20:44] forest city data centre? [20:44] north carolina [20:44] i think that's what it is [20:45] frc-nat.thefacebook.com [20:45] Menlo Park [20:45] http://en.wikipedia.org/wiki/Hot-potato_and_cold-potato_routing [20:45] oosp [20:45] Power::Datacenter.add 2, "FRC", "forest-city" [20:45] https://dazzlepod.com/ip/173.252.71.1/ [20:46] geoip lookups are probably wrong [20:46] that's probably where facebook is based [20:46] amazon are just saying US for ip's too btw [20:46] i looked it up before :) [20:47] yeah wikipedia confirms that's where they're based [20:47] but california costs more for power. [20:47] so people don't usually want to have huge server farms there [20:47] what would Amazon do with traffic you send to it that is destined for its AS Number, as in originated by it but for which it has not sent you routes [20:47] as well as land cost. [20:47] well that's technically illegal [20:48] but will often work if you static route [20:48] basically if you're caught doing it they'll drop your peer. [20:48] is most likely what would happen. [20:48] but if they had advertised route and withdrawn it just recently, and some traffic still flowed along it, then it would give false positives. [20:49] actually i don't know if it's illegal so much but rude, and likely to be not allowed in contracts. [20:50]