OpenWrt Forum Archive

Topic: IPv6 not working on Openwrt

The content of this topic has been archived on 2 May 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Hi
Am new to IPV6 and trying to setup IPV6 end-to-end connection on a router.
I have gone through the configuraitons from the below site about ipv6:
https://wiki.openwrt.org/doc/uci/network6
https://wiki.openwrt.org/doc/uci/networ … col_dhcpv6

I have configure my wan6 interface.
when i go for ifstatus on wan6, am not seeing any ipv6-prefix been assigned to it.

The clients connected to my router gets the ipv6 prefix which is statically assigned on my bridge interface.
But the end-to-end connection is not working.

Please let me know any solution or suggerstions on this how to bringup dynamic ipv6 only ened-to-end connectivity on my router.

(Last edited by sudhaatu on 23 Nov 2015, 12:51)

What kind of ipv6 connectivity your ISP provides for you?
It can be full native ipv6 or nothing, or something in between (like 6rd)...
(If isp gives you nothing, then you probably need a 6in4 tunnel from he.net, sixxs or some other tunnel provider)

You say you are assigning an ipv6 prefix on lan. Where have you got that prefix from?

How i can know what kind of ipv6 connectivity is given by ISP?
Is there any way to find it out or else i need to straight check with them?
The IPVv6 prefix on the lan, am giving my self as "2001:470::/64"

sudhaatu wrote:

How i can know what kind of ipv6 connectivity is given by ISP?
Is there any way to find it out or else i need to straight check with them?

If Openwrt does not pick automatically anything up, you need to check the ISP's website, ask them, google about ISP-specific info on discussion forums etc.

Most ISPs do not yet provide full ipv6 support, so it is quite likely that yours doesn't.

What is your ISP?

openwrt picks up the isp's ipv6 address on wan interface by itself.
but when i connect any client to openwrt, that doesn't gets end-to-end connectivity (not able to browse or ping any addresses).

sudhaatu wrote:

The IPVv6 prefix on the lan, am giving my self as "2001:470::/64"

sudhaatu wrote:

openwrt picks up the isp's ipv6 address on wan interface by itself.
but when i connect any client to openwrt, that doesn't gets end-to-end connectivity (not able to browse or ping any addresses).

Naturally it does not work if you try to mix a self-given public ipv6 address to their own config. That is like grabbing Google's or Microsoft's IP address space and starting to use it ;-)   It is likely assigned to somebody, so the traffic gets routed to somewhere else.

you should remove any self-assignments of random ipv6 addresses. Only assign something that ISP has specifically given for you.

If your wan interface really gets an address from ISP, then probably there is some ipv6 support from ISP.

If you want helpful answers, you need to provide more details. What is your ISP? What kind of address you get from them?
What does the ifconfig output look like with the Openwrt default config (also regarding ipv6).
Is there anything in the logs?
What is your current network config on ipv6?


Fox example,
I have a native ipv6 connectivity from ISP and the only ipv6 config items in are these:
(without the ipv4 items in config)

/etc/config/network:

config interface 'lan'
        option ip6assign '60'

config interface 'wan6'
        option ifname 'eth1'
        option proto 'dhcpv6'

/etc/config/dhcp:

config 'dhcp' 'lan'
        option dhcpv6 'server'
        option ra 'server'

config odhcpd 'odhcpd'
        option maindhcp '0'
        option leasefile '/tmp/hosts/odhcpd'
        option leasetrigger '/usr/sbin/odhcpd-update'

(Last edited by hnyman on 23 Nov 2015, 19:18)

ISP is rcom.
Below is the ifconfig output
br-lan    Link encap:Ethernet  HWaddr 52:29:94:10:E8:A4
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: 2001:470::2/64 Scope:Global
          inet6 addr: fe80::5029:94ff:fe10:e8a4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:1856 (1.8 KiB)

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
          inet6 addr: fe80::1034:56ff:fe78:2/64 Scope:Link
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:192 (192.0 B)  TX bytes:1054 (1.0 KiB)

wlan0     Link encap:Ethernet  HWaddr 00:90:4C:07:71:98
          inet6 addr: fe80::290:4cff:fe07:7198/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:21 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:2710 (2.6 KiB)
current network config without ipv4:
config interface 'lan'
        option ip6assign '64'
        option ip6addr '2001:470::2/64'

config interface 'wan6'
        option ifname 'eth1'
        option proto 'dhcpv6'
        option send_rs '1'
/etc/config/dhcp (ipv6 things)
config 'dhcp' 'lan'
        option dhcpv6 'server'
        option ra 'server'

config odhcpd 'odhcpd'
        option maindhcp '0'
        option leasefile '/tmp/hosts/odhcpd'
        option leasetrigger '/usr/sbin/odhcpd-update'

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)

Am not able to ping ipv6.google.com

root@OpenWrt:/# nslookup ipv6.google.com
Server:    127.0.0.1
Address 1: 127.0.0.1 localhost

Name:      ipv6.google.com
Address 1: 2404:6800:4009:804::200e bom05s05-in-x0e.1e100.net
root@OpenWrt:/# ping -6 ipv6.google.com
PING ipv6.google.com (2404:6800:4009:804::200e): 56 data bytes
^C
--- ipv6.google.com ping statistics ---
7 packets transmitted, 0 packets received, 100% packet loss

in route table "::/0" show the isp next route
root@OpenWrt:/# route -A inet6
Kernel IPv6 routing table
Destination                                 Next Hop                                Flags Metric Ref    Use Iface
::/0                                        fe80::1:25f:c0a5                        UG    1024   0        1 veth0
::/0                                        fe80::1:25f:c0a5                        UG    1024   0        0 veth0
::/128                                      fe80::25f:c0a5                          UG    1024   0        0 veth0

If connectivity from router does not work, there is no hope for devices in LAN, yet.

Possibly your ISP is not yet really providing working IPv6 connectivity, although your router gets an address.

Hmm...
which interface is veth0 ???? That is not your wan, I think.

You might need to google local discussion forums etc. in order to find out more about rcom's ipv6 offering. Various ISPs have so different ipv6 adoption strategies that there is no generic correct advice, if things don't work out-of-the-box.

In any case, if you want ipv6 now, you can always get a 6in4 tunnel from he.net or sixxs. And then configure Openwrt to use that tunnel for ipv6 traffic.

Am checking locally about the support from isp.
veth0 is my wan interface.
for 6in4 tunnel,Am trying to get isp tunnel configurations.

sudhaatu wrote:

veth0 is my wan interface.

That was not in the ifconfig that you showed earlier. :-(
Does that veth0 get the ipv6 address?
Is that a "normal" connection with dhcp etc., or is it some pppoe connection tms.

its a normal connection with dhcp, eth1 is veth0 the wan interface

The discussion might have continued from here.