sudhaatu wrote:ISP is rcom.
...
eth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet6 addr: fe80::2f8:30b0/64 Scope:Link
inet6 addr: 2405:204:xxxx:xxxx::2f8:30b0/64 Scope:Global
Well, there is some good news. rcom is Reliance, right? Based on short googling, the 2405:204:: address space belongs to Reliance, so the address looks correct and genuine.
http://www.tcpiputils.com/browse/ipv6-a … :ffff:ffff
There is some ipv6 connectivity from your ISP to you ;-)
option ip6addr '2001:470::2/64'
Like I said earlier, assigning a randomly selected public address is wrong and will break things in LAN. You should remove that.
Divide the problem to two steps:
1) first making sure that the router itself has ipv6 connectivity
2) after 1) is completed you can then think about ipv6 connectivity for LAN clients.
Does your router get full ipv6 functionality?
Does ipv6 name detection work?
Can you ping ipv6.google.com from router console?
Is a route visible?
root@OpenWrt:~# nslookup ipv6.google.com
Server: (null)
Address 1: ::1 localhost
Address 2: 127.0.0.1 localhost
Name: ipv6.google.com
Address 1: 2a00:1450:400f:805::200e arn06s07-in-x0e.1e100.net
root@OpenWrt:~# ping -6 ipv6.google.com
PING ipv6.google.com (2a00:1450:400f:805::200e): 56 data bytes
64 bytes from 2a00:1450:400f:805::200e: seq=0 ttl=56 time=10.149 ms
64 bytes from 2a00:1450:400f:805::200e: seq=1 ttl=56 time=10.127 ms
64 bytes from 2a00:1450:400f:805::200e: seq=2 ttl=56 time=10.138 ms
^C
--- ipv6.google.com ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 10.127/10.138/10.149 ms
Route to the internet "::/0" should be shown in the ipv6 router table with the link-local address of the ISP's next router. Something like fe80::200:5eff:fe00:101
root@OpenWrt:~# route -A inet6
Kernel IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
::/0 :: !n -1 1 273798 lo
::/0 fe80::200:5eff:fe00:101 UG 512 4 0 eth1
::/0 fe80::200:5eff:fe00:101 UG 512 2 0 eth1
2001:14b9:1000::1/128 fe80::200:5eff:fe00:101 UGC 0 0 2 eth1
2001:14b9:1000::2/128 fe80::200:5eff:fe00:101 UGC 0 0 4 eth1
2001:14ba:8033:1d00:84bb:aaaa:bbbb:9544/128 :: UC 0 1 1 br-lan
2001:14ba:8033:1d00:f5b2:cccc:dddd:fe12/128 :: UC 0 3 18 br-lan
2001:14ba:8033:1d00::/64 :: U 1024 2 0 br-lan
2001:14ba:8033:1d00::/56 :: !n 2147483647 0 0 lo
2001:14ba:8300::/64 :: U 256 0 0 eth1
2a00:1450:400f:805::2008/128 fe80::200:5eff:fe00:101 UGC 0 1 2 eth1
2a00:1450:4010:c09::bc/128 fe80::200:5eff:fe00:101 UGC 0 1 2 eth1
Depending on the transition mechanism, or prefix delegation mechanism, the exact items will vary.
When you get ipv6 working from the router console, then it is time to think about connectivity from devices in the LAN.
EDIT:
rcom's home page seems to contain an "ipv6" link in the footer, but that leads to a Indian government site...
http://www.rcom.co.in/Rcom/personal/home/index.html
(Last edited by hnyman on 24 Nov 2015, 09:42)