tehkode
New Around Here
After flashing new firmware, doing factory reset and reconfiguring router from scratch i've met the fact IPv6 stop working.
Here is diagnosis:
ICMP is working
But anything else does not
IPv6 Firewall is disabled
BUT
IPTABLES is messed up
However flushing ip6tables doesn't help.
I believe its not iptables related problem, since counters in "ip6tables -L -v" doesn't change on curl.
However they change on ICMP (traceroute6, ping6).
HALP!
Here is diagnosis:
ICMP is working
Code:
$ ping6 ipv6.google.com
PING6(56=40+8+8 bytes) 2a02:2698:6c26:a8df:3175:a23d:ea6c:496d --> 2a00:1450:400f:803::1003
16 bytes from 2a00:1450:400f:803::1003, icmp_seq=0 hlim=55 time=30.409 ms
16 bytes from 2a00:1450:400f:803::1003, icmp_seq=1 hlim=55 time=20.383 ms
16 bytes from 2a00:1450:400f:803::1003, icmp_seq=2 hlim=55 time=20.649 ms
But anything else does not
Code:
$ curl -v -6 http://ipv6.google.com/
* Adding handle: conn: 0x7fd6a300a600
* Adding handle: send: 0
* Adding handle: recv: 0
* Curl_addHandleToPipeline: length: 1
* - Conn 0 (0x7fd6a300a600) send_pipe: 1, recv_pipe: 0
* About to connect() to ipv6.google.com port 80 (#0)
* Trying 2a00:1450:400f:803::1003...
* Failed connect to ipv6.google.com:80; Operation timed out
* Closing connection 0
curl: (7) Failed connect to ipv6.google.com:80; Operation timed out
IPv6 Firewall is disabled
BUT
Code:
# ip6tables -L
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 udp anywhere anywhere udp spt:547 dpt:546
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-icmptype 130
ACCEPT ipv6-icmp anywhere anywhere ipv6-icmptype 131
ACCEPT ipv6-icmp anywhere anywhere ipv6-icmptype 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-icmptype 141
ACCEPT ipv6-icmp anywhere anywhere ipv6-icmptype 142
ACCEPT ipv6-icmp anywhere anywhere ipv6-icmptype 143
ACCEPT ipv6-icmp anywhere anywhere ipv6-icmptype 148
ACCEPT ipv6-icmp anywhere anywhere ipv6-icmptype 149
ACCEPT ipv6-icmp anywhere anywhere ipv6-icmptype 151
ACCEPT ipv6-icmp anywhere anywhere ipv6-icmptype 152
ACCEPT ipv6-icmp anywhere anywhere ipv6-icmptype 153
[U][B]logdrop all anywhere anywhere [/B][/U]
Chain FORWARD (policy ACCEPT)
target prot opt source destination
DROP all anywhere anywhere rt type:0 segsleft:0
[B][U]logdrop all anywhere anywhere [/U][/B]
logdrop 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
IPTABLES is messed up
However flushing ip6tables doesn't help.
I believe its not iptables related problem, since counters in "ip6tables -L -v" doesn't change on curl.
However they change on ICMP (traceroute6, ping6).
HALP!
Last edited: