s1.lax has  been added to the looking glass
mercutio: ^^
this makes it complete for ipv4
cool.
21 prefixes.
should it have more?
oh that's just customers of yours atm.
i thought there was ilke 100k routes on that  router.
just  downstream customers
100k routes went over to r1.lax when any2 was moved there
ahh ok
so then it's just ipv6, and i have to finish up the documentation i did
i was going to do it last weekend, but i got distracted.
i used it the other day.  i still can't get over how much faster it is than using he's looking glass.
haha
cool
so yeah, just ipv6 left
ugh.. can't get s3.lax to send any routes to our lg
oh there we go
finally
pro-tip: put 'route-reflector' in the peer config *on the router sending routes*
heh
ugh crap the session keeps dying...  maybe route-reflector isn't good
Alright now, who's beating up the IPv6 router? In this 10 minute period, I saw "9.2% average loss" (and no ipv6 connections could connect) https://smokeping.cobryce.com/?start=2014-10-30+18%3A10&end=2014-10-30+18%3A20&epoch_start=1414714800&epoch_end=1414718573&target=Slaves.master&hierarchy=&displaymode=n&Generate%21=Generate%21
*who's been
brycec: who do you think?
brycec: it's to do with looking glass.
Isn't that odd though, that an LG would affect connectivity?
brycec: I rebooted s3.lax
YOU MONSTER
All that uptime...
on the positive side the looking glass is working with ipv6 now
Oh, well, I can accept that then.
who is 69349
6939
he.net
grr
HE
brycec: actually i rebooted s3.lax 11 days ago as well
not sure if u caught that ;)
Depends on the time of day :p
brycec watches smokeping all day :)
LOL
when he's awake
heh... I happen to be ssh'd into my server, and then that froze. That's how come I noticed.
but yeah, now the LG is officially "finished"
http://lg.arpnetworks.com/cgi-bin/bgplg?cmd=show+ip+bgp+summary&req=
all 4 neighbors are sending routes
now it needs link from main web site? :)
I'm not sure that's really necessary
well it'd help it come in google
oh
it's in google already
how'd it get there
Scrapes of the IRC logs I assume
Do we want that attention? Is it hardened against script kiddies and whatever else?
(my concern is specifically regarding DoS)
well i dunno if it's hardened dos actually
we could have a maximum number of requests/sec
actually it's probably fine
apache won't let you do hundreds of connectiosn at once by default.
Also, why is this system still running OpenBSD 5.4??
openbsd 5.6 isn't out yet
But 5.5 is
heh.
(And 5.6 in just a couple days :P)
so 5.6 update is needed sometime anyway
5.4 had install image available already was basically the reason.
it's 5.4-stable if that makes you feel better.
Not really, no
what does 5.5 add?
maybe show version needs to be taken away to please bryce :)
64bit time_t among other things
that's not relevant yet
it's a future proofing thing
Though it's less about features and more about support, fixes, etc
The 5.4 to 5.5 upgrade is a bit of a pain in the ass though, so I understand not wanting to do it
hmm openbsd 5.5 came out on the 30th of april
does this mean openbsd 5.6 will come out in the 31st of october?
heh i just updated to the latest snapshot.
and it seems to have broken outbound http downloads
disabling pf fixed it
ahh it was the altq stuff