01-07-2016 01:46 PM - edited 03-01-2019 05:49 PM
Hello, currently I try to make a configuration for a small network which consists of multiple routers, all of them should get a IPv6 network. My ISP gives me a /56 Prefix so that should be enough for me.
Currently this is the topology:
[ ISP ] -> R1 -> Switch1 -> R2 -> Client2
-> Client1
Currently the Switch1 is just a really dumb device so it only switches no web config / ssh.
Now my client gets successfully a IPv6 however on R2 I can only have autoconfig on my incoming port.
This are some snippets on my config
R1:
interface Dialer1
ipv6 address autoconfig
ipv6 enable
no ipv6 nd ra suppress
ipv6 dhcp client pd hint ::/56
ipv6 dhcp client pd prefix-from-provider
...
interface FastEthernet0
ipv6 address prefix-from-provider ::1/64
ipv6 enable
ipv6 nd other-config-flag
...
ipv6 unicast-routing
ipv6 cef
...
ipv6 route ::/0 Dialer1
So mostly this works however to get a connection to Client 2 I need to manually set a route:
ipv6 route 2003:X:XXX:1F01::/64 2003:X:XXX:1F00:21A:8CFF:FE14:F9C5
Is there an easier way of doing so, so that my FastEthernet0 also announces one or more PD's to R2 and also sets a correct route?
I tried to use:
ipv6 dhcp iana-route-add
or
ipv6 dhcp iapd-route-add
However it won't add a route, it looks like the R2 won't get discovered automatically.
Currently R2 is not a cisco device it's a Sophos UTM which does it's routing.
The config there is just the Serial interface has DHCP enabled and gets the 2003:X:XXX:1F00:21A:8CFF:FE14:F9C5 as his address and on the Prefix delegation part I need to enable "Prefix Delegation" and set a Prefix that will getting delegated i.e.:
2003:X:XXX:1F01::1
However it looks like somehow the neighborhood discovery won't handle it since I can't see R2's internal IP or the Client2 IPv6 when running show ipv6 cef
I can only see:
2003:X:XXX:1F01::/64
nexthop 2003:X:XXX:1F00:21A:8CFF:FE14:F9C5 Vlan1
Is my config correct and there isn't another way or is there a way to have some "automatic" way of getting routes into the system?
I mean if I now add some other networks / routers they won't use SLAAC, too so that is bad.
How could I do that?
Edit:
Is it true that instead of a static route my only option is OSPF? Currently Sophos speaks BGP and OSPF.
I mean a static route is easy, however since that is a testing environment I plan to expand that later so a static config isn't as feasible as wished.
01-07-2016 05:08 PM
This sounds like a Sophos problem, not a Cisco issue. The Sophos box should be advertising itself as an IPv6 RA. It sounds like it lacks this functionality.
Yes, a routing protocol may resolve it. I don't know anything about Sophos, so don't know.
01-07-2016 11:51 PM
What happens if I can get the sops to send IPv6 RA. Do I need to change my config then?
Or what would I need to add to my config to support it?
01-08-2016 12:08 AM
If it sends an RA, it is advertising that it is a router for the LAN, so you should not need to change your config.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide