I have an odd issue that I seem to have traced to my wireless bridge/router..
I have a linux machine as my router, so my wireless routers are in AP/media bridge modes.. They're both RT-AC66Us, and they seemed to work so much better than the linksys ones I had running dd-wrt....
But as I was setting up ipv6 on my network, I noticed that while all the systems connected to the router via wired only, or directly to the AP over wireless are working fine, and all the linux systems downstream of the wireless bridge are getting ipv6 addresses and default routes set correctly.. but can't actually get any traffic to the internet. If I manually change the ipv6 default routes of one of the linux systems to my router's LAN interface global address (As opposed to its link-local address), suddenly those devices can connect.. and if I change the route back, they continue to work for a while. I THINK the client bridge is not passing NDP packets properly, but I don't have validation of that.. I just know that if I run 'ip neigh' on my router, it shows the client as FAILED.. if I change the client's default gateway, and ping6 something, it switches to reachable immediately.
If I took the time to get some packet traces at various points (the client machine and the router at least.. though perhaps on each of the ASUS routers would be possible too, though a lot more work I think) to identify what packets aren't being passed (and where they're actually being dropped, at the client bridge vs. at the AP?) would Merlin be able to fix this?
I have a linux machine as my router, so my wireless routers are in AP/media bridge modes.. They're both RT-AC66Us, and they seemed to work so much better than the linksys ones I had running dd-wrt....
But as I was setting up ipv6 on my network, I noticed that while all the systems connected to the router via wired only, or directly to the AP over wireless are working fine, and all the linux systems downstream of the wireless bridge are getting ipv6 addresses and default routes set correctly.. but can't actually get any traffic to the internet. If I manually change the ipv6 default routes of one of the linux systems to my router's LAN interface global address (As opposed to its link-local address), suddenly those devices can connect.. and if I change the route back, they continue to work for a while. I THINK the client bridge is not passing NDP packets properly, but I don't have validation of that.. I just know that if I run 'ip neigh' on my router, it shows the client as FAILED.. if I change the client's default gateway, and ping6 something, it switches to reachable immediately.
If I took the time to get some packet traces at various points (the client machine and the router at least.. though perhaps on each of the ASUS routers would be possible too, though a lot more work I think) to identify what packets aren't being passed (and where they're actually being dropped, at the client bridge vs. at the AP?) would Merlin be able to fix this?
