ROSv7.1 ipv6 not working

usovalx5 · Tue Dec 21, 2021 1:37 am

I just realized that after upgrading my HAP AC2 to ROS 7.1 IPV6 doesn't seem to work anymore.
It's quite strange actually - my uplink is BT pppoe, and I can successfully obtain ipv6 prefix from DHCP-PD.
It also correctly advertises prefixes to local machines. I can successfully ping ipv6 addresses on LAN side.
But PPPoE direction is weird, and there are few weird routing entries too:

Default route seems ok, but there are few `invalid` entries for CAPsMAN interfaces:

[usovo@hAP AC2] > /ipv6/route/print 
Flags: D - DYNAMIC; I, A - ACTIVE; c, d, v, y - COPY; H - HW-OFFLOADED; + - ECMP
Columns: DST-ADDRESS, GATEWAY, DISTANCE
      DST-ADDRESS               GATEWAY                              DISTANCE
DAd + ::/0                      fe80::22e0:9cff:fe4a:1001%pppoe-wan         1
DAv + ::/0                      pppoe-wan                                   1
DAd   2a00:23c7:c5aa:aaaa::/56                                              1
DAc   2a00:23c7:c5aa:aaaa::/64  v10-home                                    0
.....
DIcH  fe80::%guest-cAP/64       guest-cAP                                   0
DAc   fe80::%super5-cAP/64      super5-cAP                                  0
DIcH  fe80::%super-hAP/64       super-hAP                                   0
DAc   fe80::%guest-hAP/64       guest-hAP                                   0


[usovo@hAP AC2] > /ping fe80::22e0:9cff:fe4a:1001%pppoe-wan
  SEQ HOST                                     SIZE TTL TIME       STATUS                                                                                                                    
    0 fe80::22e0:9cff:fe4a:1001                  56 255 1ms594us   echo reply                                                                                                                
    1 fe80::22e0:9cff:fe4a:1001                  56 255 1ms818us   echo reply                                                                                                                
    2 fe80::22e0:9cff:fe4a:1001                  56 255 1ms808us   echo reply                                                                                                                
    sent=3 received=3 packet-loss=0% min-rtt=1ms594us avg-rtt=1ms740us max-rtt=1ms818us 

[usovo@hAP AC2] > /ping 2a00:1450:4009:81f::200e
  SEQ HOST                                     SIZE TTL TIME       STATUS                                                                                                                    
    0                                                              22 (Invalid argument)                                                                                                     
    1                                                              22 (Invalid argument)                                                                                                     
    sent=2 received=0 packet-loss=100%

I can successfully ping PPPoE gateway, but not global address, and I'm not sure why/how it results in "invalid argument"

I have tried disabling everything in IPv6 firewall and adding blanket accept all rules, but it didn't help.
Any suggestions what it can be?

eworm · Tue Dec 21, 2021 2:00 am

A default route is already added by PPPoE, and doing it again in the dhcp client was ignored in v6, but causes it to fail in v7.
So disable the default route for your dhcp client and you are fine.

usovalx5 · Tue Dec 21, 2021 1:16 pm

Thank you for helping.
I didn't notice duplicate default route myself, and disabling default route on DHCP client indeed fixed the issue.
However I still can't see pings to global addresses working, it simply says timed out.
I have tried to use torch on the pppoe interface to see if I can debug it, but I can't seem to get it working with ipv6 at all.

[usovo@hAP AC2] > /ipv6/route/print 
Flags: D - DYNAMIC; I, A - ACTIVE; c, d, v, y - COPY; H - HW-OFFLOADED
Columns: DST-ADDRESS, GATEWAY, DISTANCE
     DST-ADDRESS               GATEWAY       DISTANCE
DAv  ::/0                      pppoe-wan            1
DAd  2a00:23c7:c5aa:aaaa::/56                       1
DAc  fe80::%br1/64             br1                  0
DAc  fe80::%v10-home/64        v10-home             0
....

[usovo@hAP AC2] > /ipv6/dhcp-client/print detail 
Flags: D - dynamic; X - disabled, I - invalid 
 0    interface=pppoe-wan status=bound duid="0x00030001b869f4265c2f" dhcp-server-v6=fe80::22e0:9cff:fe4a:1001 request=prefix add-default-route=no use-peer-dns=no dhcp-options="" 
      pool-name="bt-pool" pool-prefix-length=64 prefix-hint=2a00:23aa:aaaa:2200::/56 script=/ipv6 firewall address-list add list=internal_addresses timeout=30w address=$"pd-prefix"\r\n 
      dhcp-options="" prefix=2a00:23aa:aaaa:aaaa56, 521w2d23h48m8s 


[usovo@hAP AC2] >  /ping fe80::22e0:9cff:fe4a:1001%pppoe-wan
  SEQ HOST                                     SIZE TTL TIME       STATUS                                                                                                                    
    0 fe80::22e0:9cff:fe4a:1001                  56 255 1ms616us   echo reply                                                                                                                
    1 fe80::22e0:9cff:fe4a:1001                  56 255 1ms608us   echo reply  

[usovo@hAP AC2] > /ping 2a00:1450:4009:81f::200e
  SEQ HOST                                     SIZE TTL TIME       STATUS                                                                                                                    
    0 2a00:1450:4009:81f::200e                                     timeout                                                                                                                   
    1 2a00:1450:4009:81f::200e                                     timeout      

[usovo@hAP AC2] > /tool/torch interface=pppoe-wan mac-protocol=ipv6 
-- [Q quit|D dump|C-z pause]

Running torch with `mac-protocol=ip` I can see counters for ipv4 traffic, but for some reason ipv6 is always empty - even if I run it while trying to ping link-local address of the dhcp server.

usovalx5 · Tue Dec 21, 2021 3:16 pm

As follow-up, I tried to set up Hurricane Electric tunnel to see if routing will work via it, and that seems to work fine.
Must be something specific to pppoe setup / BT?
Somewhat confused because this used to work with ROS6.

I guess I need to set up sniffer and look at the data inside pppoe for any hints.

usovalx5 · Thu Dec 30, 2021 5:49 am

As a follow-up, it seems that fixing double IPv6 default route fixed things.
I did have some other intermittent issues, but it might have been something misconfigured on my side - once I got back to looking into it, ipv6 routing works now.

ROSv7.1 ipv6 not working [SOLVED]

ROSv7.1 ipv6 not working

Re: ROSv7.1 ipv6 not working [SOLVED]

Re: ROSv7.1 ipv6 not working

Re: ROSv7.1 ipv6 not working

Re: ROSv7.1 ipv6 not working

Who is online