Modify

Opened 4 years ago

Closed 4 years ago

#17272 closed defect (fixed)

IPv6 broken on stations / router with PPPoE

Reported by: daniel.petre Owned by: developers
Priority: high Milestone: Chaos Calmer 15.05
Component: base system Version: Trunk
Keywords: ipv6, pppoe, pppd, dhcpv6 Cc:

Description

Hello,
on r41831 on a router connected dual stack via PPPoE seems like IPv6 does not work anymore on a wireless connected linux desktop.

IPv6 works okay on the router:

root@openwrt:~# route -A inet6
Kernel IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
::/0 fe80::1 UG 1024 0 0 pppoe-wan
::/0 fe80::1 UG 1024 0 0 pppoe-wan
::/0 fe80::1 UG 1024 0 0 pppoe-wan
2a02:2f0d:b178:6000::/64 :: U 256 0 0 br-lan
fdd9:ff42:650c::/60 :: U 256 0 0 br-lan
fe80::/64 :: U 256 0 0 eth0
fe80::/64 :: U 256 0 0 br-lan
fe80::/64 :: U 256 0 0 eth0.2
fe80::/64 :: U 256 0 0 wlan0
fe80::/10 :: U 1 0 0 pppoe-wan
fe80::/10 :: U 256 0 0 pppoe-wan
::1/128 :: U 0 0 1 lo
2a02:2f0d:b178:6000::/128 :: U 0 0 1 lo
2a02:2f0d:b178:6000::1/128 :: U 0 6 1 lo
2a02:2f0d:b17f:ffff::4f76:c04d/128 :: U 0 178 1 lo
fdd9:ff42:650c::/128 :: U 0 0 1 lo
fdd9:ff42:650c::1/128 :: U 0 2 1 lo
fe80::/128 :: U 0 0 1 lo
fe80::/128 :: U 0 0 1 lo
fe80::/128 :: U 0 0 1 lo
fe80::/128 :: U 0 0 1 lo
fe80::/128 :: U 0 0 1 lo
fe80::4f76:c04d/128 :: U 0 2 1 lo
fe80::20c:43ff:fe44:62ed/128 :: U 0 0 1 lo
fe80::20c:43ff:fe44:62ed/128 :: U 0 0 1 lo
fe80::20c:43ff:fe44:62ed/128 :: U 0 6 1 lo
fe80::cad3:a3ff:fe06:c82c/128 :: U 0 0 1 lo
ff02::1/128 :: UC 0 1 0 br-lan
ff02::c/128 :: UC 0 627 0 br-lan
ff00::/8 :: U 256 0 0 eth0
ff00::/8 :: U 256 0 2 br-lan
ff00::/8 :: U 256 0 0 eth0.2
ff00::/8 :: U 256 0 0 pppoe-wan
ff00::/8 :: U 256 0 0 wlan0

[dani@x61s ~]$ traceroute -6 ipv6.google.com
traceroute to ipv6.google.com (2a00:1450:4001:c02::71), 30 hops max, 80 byte packets
connect: Network is unreachable

[dani@x61s ~]$ ip -6 ro
2a02:2f0d:b178:6000::/64 dev wls3 proto kernel metric 303 mtu 1492
fdd9:ff42:650c::/64 dev wls3 proto kernel metric 303 mtu 1492
fe80::/64 dev wls3 proto kernel metric 256

Attachments (0)

Change History (6)

comment:1 Changed 4 years ago by daniel.petre

On r41527 everything works just fine:

[dani@x61s ~]$ ip -6 ro
2a02:2f0d:b178:cf00::/64 dev wls3 proto kernel metric 303 mtu 1492
fdd9:ff42:650c::/64 dev wls3 proto kernel metric 303 mtu 1492
fe80::/64 dev wls3 proto kernel metric 256
default via fe80::20c:43ff:fe44:62ed dev wls3 proto static metric 1
default via fe80::20c:43ff:fe44:62ed dev wls3 proto ra metric 1024 expires 1703sec

[dani@x61s ~]$ traceroute -6 ipv6.google.com
traceroute to ipv6.google.com (2a00:1450:4016:804::1001), 30 hops max, 80 byte packets

1 2a02:2f0d:b178:cf00::1 (2a02:2f0d:b178:cf00::1) 1.348 ms 1.727 ms 2.185 ms
2 2a02:2f0d:b17f:ff00::2 (2a02:2f0d:b17f:ff00::2) 7.342 ms 7.535 ms 7.024 ms
3 2a02:2f0d:b17f:ff01::1 (2a02:2f0d:b17f:ff01::1) 6.533 ms 6.697 ms 7.603 ms
4 2a02:2f00:1234:f02::1 (2a02:2f00:1234:f02::1) 7.897 ms 8.083 ms 8.277 ms
5 * * *
6 xr01.v6.budapesta.rdsnet.ro (2a02:2f00:8708:4:1:0:237:0) 22.725 ms 14.759 ms 14.762 ms
7 2001:4860:1:1:0:2204:0:2 (2001:4860:1:1:0:2204:0:2) 31.841 ms 31.954 ms 32.041 ms
8 2001:4860::1:0:446f (2001:4860::1:0:446f) 27.128 ms 27.311 ms 27.518 ms
9 2001:4860::1:0:336c (2001:4860::1:0:336c) 33.871 ms 36.629 ms 34.111 ms

10 2001:4860:0:1::19 (2001:4860:0:1::19) 34.665 ms 37.805 ms 31.890 ms
11 muc03s13-in-x01.1e100.net (2a00:1450:4016:804::1001) 34.739 ms 32.010 ms 32.383 ms

comment:2 Changed 4 years ago by daniel.petre

output of ifstatus wan6 on the router with r41831 :

{

"up": true,
"pending": false,
"available": true,
"autostart": true,
"uptime": 62,
"l3_device": "pppoe-wan",
"proto": "dhcpv6",
"device": "pppoe-wan",
"updated": [

"addresses",
"routes",
"prefixes",
"data"

],
"metric": 0,
"delegation": true,
"ipv4-address": [


],
"ipv6-address": [

{

"address": "2a02:2f0d:b17f:ffff::4f76:cc3d",
"mask": 128

}

],
"ipv6-prefix": [

{

"address": "2a02:2f0d:b171:7500::",
"mask": 64,
"class": "wan6",
"assigned": {

"lan": {

"address": "2a02:2f0d:b171:7500::",
"mask": 64

}

}

}

],
"ipv6-prefix-assignment": [


],
"route": [

{

"target": "::",
"mask": 0,
"nexthop": "fe80::1",
"metric": 1024,
"valid": 837,
"source": "2a02:2f0d:b171:7500::\/64"

},
{

"target": "::",
"mask": 0,
"nexthop": "fe80::1",
"metric": 1024,
"valid": 837,
"source": "::\/128"

},
{

"target": "::",
"mask": 0,
"nexthop": "fe80::1",
"metric": 1024,
"valid": 837,
"source": "2a02:2f0d:b17f:ffff::4f76:cc3d\/128"

}

],
"dns-server": [

"2a02:2f0c:8000:3::1",
"2a02:2f0c:8000:8::1"

],
"dns-search": [


],
"inactive": {

"ipv4-address": [


],
"ipv6-address": [


],
"route": [


],
"dns-server": [


],
"dns-search": [


]

},
"data": {

"passthru": "001700202a022f0c8000000300000000000000012a022f0c800000080000000000000001"

}

}

comment:3 Changed 4 years ago by cyrus

Looks good to me though. How does your /etc/config/dhcp look like? Is the odhcpd process running?

comment:4 Changed 4 years ago by daniel.petre

config dnsmasq

option domainneeded '1'
option boguspriv '1'
option filterwin2k '0'
option localise_queries '1'
option rebind_protection '1'
option rebind_localhost '1'
option local '/lan/'
option domain 'lan'
option expandhosts '1'
option nonegcache '0'
option authoritative '1'
option readethers '1'
option leasefile '/tmp/dhcp.leases'
option resolvfile '/tmp/resolv.conf.auto'

config dhcp 'lan'

option interface 'lan'
option start '100'
option limit '150'
option leasetime '12h'
option dhcpv6 'server'
option ra 'server'

config dhcp 'wan'

option interface 'wan'
option ignore '1'

config odhcpd 'odhcpd'

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

root@openwrt:~# ps | grep [d]hcp

864 root 1184 S /usr/sbin/odhcpd

1527 root 820 S odhcp6c -s /lib/netifd/dhcpv6.script -P0 -t120 pppoe-wan

comment:5 Changed 4 years ago by daniel.petre

Apologies, i think some Arch Linux updates these days broke something, tested on Mac and Android and it seems okay.

comment:6 Changed 4 years ago by cyrus

  • Resolution set to fixed
  • Status changed from new to closed

Guess I'll close this for now.

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.