Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The best thing is autoconfiguration, of course.

It not evident if you are an admin of localhost, but working with hundreds devices make you really appreciate it.

This is the whole config what allows the device to talk to IPv6 and provide IPv6 addresses to the clients in the vlan3003. No DHCP, no ip helpers, nothing.

    interface Vlan2999
     ipv6 address 2000:1111:1:1::2/126
    !
    interface Vlan3003
     ipv6 address 2000:1111:1:4::1/64
    !
    ip forward-protocol nd
    !
    ipv6 route ::/0 2000:1111:1:1::1
> in case anyone is wondering why IPv6 is where it’s at after a decade

But.. I'm tired to juggle this nonsense. We have /21, a couple of /24 and a bunch of /28. I recently decided to move out our services from /21 and /24 to some specific /28 and despite what all those /28 are pretty close (most of them sits in one /23) I can't have a few laconic network rules with aggregates for separating our own and customers traffic. I would need to have a whole let of rules, almost for each /28.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: