Menu
What's new
By:
Filters Better Search

IPv6 Trouble

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

casaper

casaper

Occasional Visitor
Hi Everyone

I'm using the latest Merlin Asuswrt (RT-AC66U_378.56_2) on my Asus AC-66U.
Two years ago, I happened to get my FTTH, which is great. :)
As my ISP is highly involved into spreading the use of IPv6, my WAN access is IPv6 enabled and equipped with a Fix IPv6 address and a Range etc..

But since then, I've been trying to get that IPv6 connection up and running several times. But, I never managed to get that thing going … really.
Gave up on it (until now and so on, life without IPv6 is still possible), and came back trying every few months again (curiosity, technophile).

So here comes my strange issue:

I put in the IPv6 Settings provided by my ISP.
So I use Asus-WRT's static-IPv6 pane, put in all the stuff provided by my ISP.
3469b9t.jpg


Hitting "Apply" AC-66U works a little to updates it's setting, and as soon as I'm back and my 2 interfaces gained they're IPv6, it works … but only for maybe 10 to 15 seconds tho.

This is from my OSX Shell:
Code: 
kaspi at comper in ~
$ $ sh -c 'ifconfig en0 && ifconfig en1'& sh -c 'ping6 -c 1 ipv6.google.com || ping -c 1 google.com'& sh -c 'dig -t any google.com @2001:4860:4860::8888'
[1] 6823
[2] 6824
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
   options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
   ether 3c:07:54:43:7b:d1
   inet6 fe80::3e07:54ff:fe43:7bd1%en0 prefixlen 64 scopeid 0x4
   inet 192.168.1.76 netmask 0xffffff00 broadcast 192.168.1.255
   inet6 2001:1620:4064::3e07:54ff:fe43:7bd1 prefixlen 64 autoconf
   inet6 2001:1620:4064::b813:ab69:b6b7:e405 prefixlen 64 autoconf temporary
   nd6 options=1<PERFORMNUD>
   media: autoselect (1000baseT <full-duplex,flow-control>)
   status: active
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
   ether 28:cf:da:f3:9a:16
   inet6 fe80::2acf:daff:fef3:9a16%en1 prefixlen 64 scopeid 0x5
   inet 192.168.1.120 netmask 0xffffff00 broadcast 192.168.1.255
   inet6 2001:1620:4064::2acf:daff:fef3:9a16 prefixlen 64 autoconf
   inet6 2001:1620:4064::8c11:b9b3:fe99:19cf prefixlen 64 autoconf temporary
   nd6 options=1<PERFORMNUD>
   media: autoselect
   status: active
[1]  - 6823 done       sh -c 'ifconfig en0 && ifconfig en1'
PING6(56=40+8+8 bytes) 2001:1620:4064::b813:ab69:b6b7:e405 --> 2a00:1450:400a:806::1001
16 bytes from 2a00:1450:400a:806::1001, icmp_seq=0 hlim=59 time=1.091 ms

--- ipv6.l.google.com ping6 statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 1.091/1.091/1.091/0.000 ms
[2]  + 6824 done       sh -c 'ping6 -c 1 ipv6.google.com || ping -c 1 google.com'
;; Truncated, retrying in TCP mode.

; <<>> DiG 9.8.3-P1 <<>> -t any google.com @2001:4860:4860::8888
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63549
;; flags: qr rd ra; QUERY: 1, ANSWER: 24, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.         IN ANY

;; ANSWER SECTION:
google.com.    299   IN A  173.194.40.34
google.com.    299   IN A  173.194.40.40
google.com.    299   IN A  173.194.40.36
google.com.    299   IN A  173.194.40.35
google.com.    299   IN A  173.194.40.32
google.com.    299   IN A  173.194.40.33
google.com.    299   IN A  173.194.40.46
google.com.    299   IN A  173.194.40.41
google.com.    299   IN A  173.194.40.38
google.com.    299   IN A  173.194.40.37
google.com.    299   IN A  173.194.40.39
google.com.    299   IN AAAA  2a00:1450:400a:804::1008
google.com.    21599 IN NS ns1.google.com.
google.com.    21599 IN TYPE257  \# 19 0005697373756573796D616E7465632E636F6D
google.com.    21599 IN NS ns2.google.com.
google.com.    3599  IN TXT   "v=spf1 include:_spf.google.com ~all"
google.com.    599   IN MX 10 aspmx.l.google.com.
google.com.    599   IN MX 30 alt2.aspmx.l.google.com.
google.com.    599   IN MX 50 alt4.aspmx.l.google.com.
google.com.    21599 IN NS ns3.google.com.
google.com.    599   IN MX 20 alt1.aspmx.l.google.com.
google.com.    599   IN MX 40 alt3.aspmx.l.google.com.
google.com.    21599 IN NS ns4.google.com.
google.com.    59 IN SOA   ns1.google.com. dns-admin.google.com. 107842999 900 900 1800 60

;; Query time: 38 msec
;; SERVER: 2001:4860:4860::8888#53(2001:4860:4860::8888)
;; WHEN: Sat Nov 14 10:40:11 2015
;; MSG SIZE  rcvd: 537

This was right after updating the AC-66U's setting. Forcing dig to use googles public IPv6 DNS with "@2001:4860:4860::8888" lets me believe dig must have used IPv6 to connect to that DNS. The same thing also worked with a ping6 to that IPv6 right after updating the router's IPv6 Settings.

But now, only a few seconds later, doing the same stuff:
Code: 
sh -c 'ifconfig en0 && ifconfig en1'& sh -c 'ping6 -c 1 ipv6.google.com || ping -c 1 google.com'& sh -c 'dig -t any google.com @2001:4860:4860::8888'
[1] 6873
[2] 6874
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
   options=10b<RXCSUM,TXCSUM,VLAN_HWTAGGING,AV>
   ether 3c:07:54:43:7b:d1
   inet6 fe80::3e07:54ff:fe43:7bd1%en0 prefixlen 64 scopeid 0x4
   inet 192.168.1.76 netmask 0xffffff00 broadcast 192.168.1.255
   inet6 2001:1620:4064::3e07:54ff:fe43:7bd1 prefixlen 64 autoconf
   inet6 2001:1620:4064::b813:ab69:b6b7:e405 prefixlen 64 autoconf temporary
   nd6 options=1<PERFORMNUD>
   media: autoselect (1000baseT <full-duplex,flow-control>)
   status: active
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
   ether 28:cf:da:f3:9a:16
   inet6 fe80::2acf:daff:fef3:9a16%en1 prefixlen 64 scopeid 0x5
   inet 192.168.1.120 netmask 0xffffff00 broadcast 192.168.1.255
   inet6 2001:1620:4064::2acf:daff:fef3:9a16 prefixlen 64 autoconf
   inet6 2001:1620:4064::8c11:b9b3:fe99:19cf prefixlen 64 autoconf temporary
   nd6 options=1<PERFORMNUD>
   media: autoselect
   status: active
[1]  - 6873 done       sh -c 'ifconfig en0 && ifconfig en1'
PING6(56=40+8+8 bytes) 2001:1620:4064::b813:ab69:b6b7:e405 --> 2a00:1450:400a:806::1001

--- ipv6.l.google.com ping6 statistics ---
1 packets transmitted, 0 packets received, 100.0% packet loss
PING google.com (173.194.116.35): 56 data bytes
64 bytes from 173.194.116.35: icmp_seq=0 ttl=59 time=1.112 ms

--- google.com ping statistics ---
1 packets transmitted, 1 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.112/1.112/1.112/0.000 ms
[2]  + 6874 done       sh -c 'ping6 -c 1 ipv6.google.com || ping -c 1 google.com'

; <<>> DiG 9.8.3-P1 <<>> -t any google.com @2001:4860:4860::8888
;; global options: +cmd
;; connection timed out; no servers could be reached

Does anyone have any hints, on what might be going wrong here?
The fact that it works for a few seconds shows (I assume so at least) that my settings I've put into the AC-66U where not wrong.

So is it a AC-66U/Merlin ASUS-WRT Problem?
Is it a wrong setting on my Mac?
In my LAN settings, or wherever?
I'm completely unable to find out, also begging my favorite search engine to spit any information at me.

Thank you for any advice on that in advance!

IPv6 may not be totally inevitable yet, but I assume sooner or later I will have to be able to get that thing running in order to connect to anything on the net. ;)

Regards

Cas
 
I don't know much about OSx and Macs, but you should try to check from the router itself if IPv6 works. Just login via ssh or telnet and try a trace or ping to an IPv6 address. Just to be sure the router's connection itself works, before starting to look for faults in your Mac.
 
Try changing LAN prefix length from 48 to 64...
 
Hi

If you know allot about Linux's networking, you'll be pretty fine with OS X's as well. This is because OS X's networking and allot of the stuff under the hood is heavily related with FreeBSD. So quite similar to Linux.

charlie2alpha said:
I don't know much about OSx and Macs, but you should try to check from the router itself if IPv6 works. Just login via ssh or telnet and try a trace or ping to an IPv6 address. Just to be sure the router's connection itself works, before starting to look for faults in your Mac.
Click to expand...

I did so, and as it seems, you're right. It does work directely on the router:
AC66U's traceroute6 & ping6

but from the Macosx Client it doesnt ... Most of the time:
macs ping6&traceroute6

So, this makes me wonder about the Routing??
Here is the Info from the AC66U:
Code: 
kaspi@RT-AC66U-F080:/tmp/home/root# ifconfig eth0 && ifconfig eth1 && ifconfig br0
eth0       Link encap:Ethernet  HWaddr 60:A4:4C:68:F0:80
           inet addr:77.109.184.34  Bcast:77.109.185.255  Mask:255.255.254.0
           inet6 addr: 2001:1620:5:1::74/64 Scope:Global
           inet6 addr: fe80::62a4:4cff:fe68:f080/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:840061 errors:0 dropped:0 overruns:0 frame:0
           TX packets:780940 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:434645477 (414.5 MiB)  TX bytes:453320957 (432.3 MiB)
           Interrupt:4 Base address:0x2000

eth1       Link encap:Ethernet  HWaddr 60:A4:4C:68:F0:80
           inet6 addr: fe80::62a4:4cff:fe68:f080/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:83688
           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
           Interrupt:3 Base address:0x8000

br0        Link encap:Ethernet  HWaddr 60:A4:4C:68:F0:80
           inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
           inet6 addr: 2001:1620:4064::1/48 Scope:Global
           inet6 addr: fe80::62a4:4cff:fe68:f080/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:62033 errors:0 dropped:0 overruns:0 frame:0
           TX packets:20580 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:3910640 (3.7 MiB)  TX bytes:4937022 (4.7 MiB)

kaspi@RT-AC66U-F080:/tmp/home/root# ip -6 route show
2001:1620:5:1::1 dev eth0  metric 1  expires -3839sec mtu 1500 advmss 1440 metric 10 4294967295
2001:1620:5:1::/64 dev eth0  metric 256  expires -3840sec mtu 1500 advmss 1440 metric 10 4294967295
2001:1620:4064::/48 dev br0  metric 256  expires -3840sec mtu 1500 advmss 1440 metric 10 4294967295
fe80::/64 dev vlan1  metric 256  expires -3839sec mtu 1500 advmss 1440 metric 10 4294967295
fe80::/64 dev eth1  metric 256  expires -3839sec mtu 1500 advmss 1440 metric 10 4294967295
fe80::/64 dev eth2  metric 256  expires -3839sec mtu 1500 advmss 1440 metric 10 4294967295
fe80::/64 dev br0  metric 256  expires -3839sec mtu 1500 advmss 1440 metric 10 4294967295
fe80::/64 dev eth0  metric 256  expires -3839sec mtu 1500 advmss 1440 metric 10 4294967295
default via 2001:1620:5:1::1 dev eth0  metric 1  expires -3839sec mtu 1500 advmss 1440 metric 10 4294967295
unreachable default dev lo  proto none  metric -1  error -128 metric 10 255
ff00::/8 dev vlan1  metric 256  expires -3839sec mtu 1500 advmss 1440 metric 10 4294967295
ff00::/8 dev eth1  metric 256  expires -3839sec mtu 1500 advmss 1440 metric 10 4294967295
ff00::/8 dev eth2  metric 256  expires -3839sec mtu 1500 advmss 1440 metric 10 4294967295
ff00::/8 dev br0  metric 256  expires -3839sec mtu 1500 advmss 1440 metric 10 4294967295
ff00::/8 dev eth0  metric 256  expires -3839sec mtu 1500 advmss 1440 metric 10 4294967295
unreachable default dev lo  proto none  metric -1  error -128 metric 10 255

and my mac:
Code: 
Internet6:
Destination             Gateway              Flags         Netif Expire
default                 fe80::62a4:4cff:fe   UGc             en0
default                 fe80::62a4:4cff:fe   UGcI            en1
localhost               localhost            UHL             lo0
2001:1620:4064::        link#4               UC              en0
2001:1620:4064::        link#5               UCI             en1
2001:1620:4064::1       60:a4:4c:68:f0:80    UHLWI           en0
2001:1620:4064::1b      3c:7:54:43:7b:d1     UHL             lo0
2001:1620:4064::1b      28:cf:da:f3:9a:16    UHL             lo0
fe80::%lo0              fe80::1%lo0          UcI             lo0
fe80::1%lo0             link#1               UHLI            lo0
fe80::%en0              link#4               UCI             en0
comper.local            3c:7:54:43:7b:d1     UHLI            lo0
fe80::62a4:4cff:fe      60:a4:4c:68:f0:80    UHLWIir         en0
fe80::%en1              link#5               UCI             en1
comper.local            28:cf:da:f3:9a:16    UHLI            lo0
fe80::62a4:4cff:fe      60:a4:4c:68:f0:80    UHLWIir         en1
ff01::%lo0              localhost            UmCI            lo0
ff01::%en0              link#4               UmCI            en0
ff01::%en1              link#5               UmCI            en1
ff02::%lo0              localhost            UmCI            lo0
ff02::%en0              link#4               UmCI            en0
ff02::%en1              link#5               UmCI            en1

I've been looking at those Routing tables many times, in earlyer tryes. I know only the basics about Routing. I played arround with this back then, and never had any luck.

Maybe you get more clou out of my routing tables.
In my unwise guess, RT-AC66-U's br0 interface is somehow getting wrong routes. But I'm completely unable to fix this here, nor where and how they're getting broken.

Thank you!

Reg.

CAS
 
And here another Example. See the Macping6.txt file. it shows a sequence of ping6's on my mac, right after switching, with time and date. After a while it stopped working. ??

And, while ping6-ing stopped to work, traceroute had still found a route. See the newely attached macTraceroute6.txt for this (again with times between the simultaneously startet traceroute6's)
 

Attachments

  • macping6.txt
    4.2 KB · Views: 342
  • macTraceroute6.txt
    7.9 KB · Views: 650
Last edited:
and here the same thing again, with the router, just for the sake of demonstration, both shortely after switching on ipv6 with Auto Configuration Setting = stateless.
 

Attachments

  • routerPingTraceroute6.txt
    18.6 KB · Views: 341
  • newMacPingTraceroute6.txt
    14.7 KB · Views: 352
I found out now, that for some unknown reason my mac gets a wrong ipv6 default route:
Code: 
$ netstat -rn -f inet6
Routing tables

Internet6:
Destination                             Gateway                         Flags         Netif Expire
default                                 fe80::62a4:4cff:fe68:f080%en0   UGc             en0
default                                 fe80::62a4:4cff:fe68:f080%en1   UGcI            en1
::1                                     ::1                             UHL             lo0
2001:1620:4064::/64                     link#4                          UC              en0
2001:1620:4064::/64                     link#5                          UCI             en1
2001:1620:4064::1                       60:a4:4c:68:f0:80               UHLWIi          en0
2001:1620:4064::1                       60:a4:4c:68:f0:80               UHLWI           en1
2001:1620:4064::2acf:daff:fef3:9a16     28:cf:da:f3:9a:16               UHL             lo0
2001:1620:4064::3e07:54ff:fe43:7bd1     3c:7:54:43:7b:d1                UHL             lo0
2001:1620:4064::85cc:a:275f:9e0b        3c:7:54:43:7b:d1                UHL             lo0
2001:1620:4064::b88b:6a4f:c92a:3fce     link#4                          UHLWI           en0
2001:1620:4064::b9ee:8849:ad0e:6af8     28:cf:da:f3:9a:16               UHL             lo0
fe80::%lo0/64                           fe80::1%lo0                     UcI             lo0
fe80::1%lo0                             link#1                          UHLI            lo0
fe80::%en0/64                           link#4                          UCI             en0
fe80::2acf:daff:fef3:9a16%en0           28:cf:da:f3:9a:16               UHLWI           en0
fe80::3e07:54ff:fe43:7bd1%en0           3c:7:54:43:7b:d1                UHLI            lo0
fe80::62a4:4cff:fe68:f080%en0           60:a4:4c:68:f0:80               UHLWIir         en0
fe80::%en1/64                           link#5                          UCI             en1
fe80::2acf:daff:fef3:9a16%en1           28:cf:da:f3:9a:16               UHLI            lo0
fe80::3e07:54ff:fe43:7bd1%en1           3c:7:54:43:7b:d1                UHLWI           en1
fe80::62a4:4cff:fe68:f080%en1           60:a4:4c:68:f0:80               UHLWIir         en1
ff01::%lo0/32                           ::1                             UmCI            lo0
ff01::%en0/32                           link#4                          UmCI            en0
ff01::%en1/32                           link#5                          UmCI            en1
ff02::%lo0/32                           ::1                             UmCI            lo0
ff02::%en0/32                           link#4                          UmCI            en0
ff02::%en1/32                           link#5                          UmCI            en1

fe80::62a4:4cff:fe68:f080 is on the AC66 Router:
Code: 
br0        Link encap:Ethernet  HWaddr 60:A4:4C:68:F0:80
           inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
           inet6 addr: 2001:1620:4064::1/48 Scope:Global
           inet6 addr: fe80::62a4:4cff:fe68:f080/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:76461 errors:0 dropped:0 overruns:0 frame:0
           TX packets:72626 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:6615245 (6.3 MiB)  TX bytes:9304467 (8.8 MiB)

eth0       Link encap:Ethernet  HWaddr 60:A4:4C:68:F0:80
           inet addr:77.109.184.34  Bcast:77.109.185.255  Mask:255.255.254.0
           inet6 addr: 2001:1620:5:1::74/64 Scope:Global
           inet6 addr: fe80::62a4:4cff:fe68:f080/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:1042135 errors:0 dropped:0 overruns:0 frame:0
           TX packets:980126 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:474337727 (452.3 MiB)  TX bytes:494330191 (471.4 MiB)
           Interrupt:4 Base address:0x2000

it is the Scope:Link address.

But why in hell is my mac getting this address as default route?
How can I make it to get the correct 2001:1620:4064::1 as default GW?

I tried to set the router on the Mac manually, and it worked. But this is not a option - it is a mobile computer ...

TIA
Cas
 
PS: And this isn't a Mac related problem!
On my Android Phone I get exactly the same behaviour. Fresh turn on Wifi -> ipv6.google.com can be displayed in the browser.
But after a while it stopps beeing reachable.
And onece i turn of WiFi and then turn it back on, ipv6.google.com is beeing reachable for 20 secs or so again.
 
Actually, the default gateway must be the link local address of the router, it's the normal way for IPv6.

Sent from my Nexus 9 using Tapatalk
 
Some other bet, ip6tables.

I don't see the blame here, but sometimes I'm Blind, maybe there is something wrong. I deactivated ipv6 firewall in the webgui tho, in order to cut some failure.
But a "ip6tables -L" gives:
Code: 
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     ipv6-nonxt    anywhere             anywhere           length 40
ACCEPT     all      anywhere             anywhere
ACCEPT     all      anywhere             anywhere
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp destination-unreachable
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp packet-too-big
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp time-exceeded
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp parameter-problem
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp echo-request
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp echo-reply
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp type 130
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp type 131
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp type 132
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp router-solicitation
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp router-advertisement
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp neighbour-solicitation
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp neighbour-advertisement
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp type 141
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp type 142
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp type 143
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp type 148
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp type 149
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp type 151
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp type 152
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp type 153
DROP       all      anywhere             anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
DROP       all      anywhere             anywhere           rt type:0
DROP       all      anywhere             anywhere
DROP       all      anywhere             anywhere           state INVALID
ACCEPT     all      anywhere             anywhere
ACCEPT     ipv6-nonxt    anywhere             anywhere           length 40
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp destination-unreachable
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp packet-too-big
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp time-exceeded
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp parameter-problem
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp echo-request
ACCEPT     ipv6-icmp    anywhere             anywhere           ipv6-icmp echo-reply

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
DROP       all      anywhere             anywhere           rt type:0

Chain PControls (0 references)
target     prot opt source               destination
ACCEPT     all      anywhere             anywhere

Chain UPNP (0 references)
target     prot opt source               destination

Chain logaccept (0 references)
target     prot opt source               destination
LOG        all      anywhere             anywhere           state NEW LOG level warning tcp-sequence tcp-options ip-options prefix `ACCEPT '
ACCEPT     all      anywhere             anywhere

Chain logdrop (0 references)
target     prot opt source               destination
LOG        all      anywhere             anywhere           state NEW LOG level warning tcp-sequence tcp-options ip-options prefix `DROP '
DROP       all      anywhere             anywhere

Just in case this would be the merde.... TIA
 
casaper said:
I tried this, bit it didn't make any difference.
Click to expand...

Try the LAN prefix length to 64 again and reboot both the router and device after setting it. I would leave it at 64 until you get ipv6 working for more than 24 hours.
My guess about your problem is that either the radvd or dnsmasq program is upset and not advertising. Look in syslog for any error messages by either program. Could be something blocking ICMP packets since ipv6 depends more on icmp which have short lifetimes. Try to ping from the router to your LAN device to see if that restarts the connection.

Suggest you try this command for debugging ip6tables

Code: 
ip6tables -nvL --lin | grep -v "    0     0 "

Which gives the usage count of the rules with the ip6tables part, and the grep part keeps only the rules that were used.. Watch which, if any, rules increase usage count and have a target of drop.

The icmp packets must be accepted by the INPUT and OUTPUT chains.
 
You must log in or register to reply here.

Similar threads

R
IPv6 Config with VLAN WAN
2
Replies
23
Views
3K
learning_curve
L
A
help on ipv6 setup
Replies
12
Views
2K
heysoundude
heysoundude
th3viper
OpenVPN client issues
Replies
9
Views
2K
th3viper
th3viper
Bo Simonsen
Repeater mode and ipv6
Replies
0
Views
2K
Bo Simonsen
Bo Simonsen
marco92
RT-AC66U IPv6 tunnel
Replies
11
Views
5K
marco92
marco92
Similar threads
Thread starter Title Forum Replies Date
i0ntempest IPv6 traffic forwarding problem: connection hangs Asuswrt-Merlin 9
el_pedr0 How do you specify different IPv6 subnets? Asuswrt-Merlin 1
el_pedr0 Does ddns-start get passed IPv6? Asuswrt-Merlin 2
Z Ipv6 suppress_prefixlength broken on some routers? Asuswrt-Merlin 2
A WireGuard client with IPv6 enabled Asuswrt-Merlin 24
M Can't ping ipv6 with all connected devices Asuswrt-Merlin 0
zquestz Dual WAN IPv6 Asuswrt-Merlin 2
N IPv6 6RD tunnel block/allow by mac/IP Asuswrt-Merlin 3
S How to obtain and change the IPv6 prefix Asuswrt-Merlin 3
J IPv6 WAN Prefix Length Setting in WebGUI (3004.388.8_2)? Asuswrt-Merlin 14

Similar threads

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Total: 727 (members: 21, guests: 706)
Top