Update:
It looks like some new firewall rules that are introduced in newer
versions of trunk are stopping IPv6 from working.
I turned off Allow-MLD, and 2 blank rules which seem to be there by
factory default accept forward any esp and any udp port 500. Also
disabled SYN flood protection and Drop Invalid Packets...
IPv6 now works.
Very weird indeed.
Now the only extra thing I need to do is after the router has booted, I
need to restart the firewall via /etc/init.d/firewall restart and IPv6
works just fine.
Seems the b0rked IPv6 addresses was corrected during the past 1500
commits somewhere and so that is also now working fine.
Boils down to firewall rules.
Heh. A few less hairs on my head.
On 10/02/16 16:27, Adam Kuklycz wrote:
Further to this, I have compiled trunk versions 47750 and 47458 which
both exhibit the same IPv6 non-routing issue, however with 47458 the
IPv6 address is a bit less b0rked...
inet6 addr: xxxx:xxxx:xxxx:xxxx:xxxx:561e:7d31:631e%3/64 Scope:Global
PING ipv6.google.com(sin04s05-in-x0e.1e100.net) 56 data bytes
ping: sendmsg: Network unreachable
ping: sendmsg: Permission denied
ping: sendmsg: Network unreachable
ping: sendmsg: Network unreachable
ping: sendmsg: Network unreachable
ping: sendmsg: Network unreachable
^C
--- ipv6.google.com ping statistics ---
6 packets transmitted, 0 received, 100% packet loss, time 5022ms
Some commits which caught my eye are the following:
47514 47493 47487 47460/47459 & 47288
Could be totally wrong however and it could be a download during the
compile process that causes things to break...but so far I've spent
the whole day compiling and trying to narrow down what is causing IPv6
to not work.
A build I did on Oct 25, 2015 for revision 47245 works fine with IPv6.
Note that I am using Ubuntu 14.04.3 x64 to compile.
Any help appreciated
TIA
Adam
On 10/02/16 12:05, Adam Kuklycz wrote:
Hi all,
I've noticed with current trunk (Designated Driver) and revisions
down to 48272 that IPv6 native does not work.
Infact when checking via ifconfig -a, on the pppoe-wan interface, the
IPv6 address ends up as follows:
inet6 addr: xxxx:xxxx:xxxx:xxxx:bd9f:ac2e:e659:67ee%2010362168/64
Scope:Global
I've attached the config file to this email that I used to compile.
The /etc/config/network file is as follows:
root@rear-gw:~# cat /etc/config/network
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fd10:bc2e:49e1::/48'
config interface 'lan'
option force_link '1'
option type 'bridge'
option proto 'static'
option netmask '255.255.255.0'
option ip6assign '64'
option dns '150.101.158.130'
option ipaddr '172.18.18.1'
option _orig_ifname 'eth0.1 wlan0 wlan0-1 wlan1'
option _orig_bridge 'true'
option ifname 'eth0.1'
config interface 'wan'
option proto 'pppoe'
option username 'akukl...@dynamic.internode.on.net'
option password 'gc7qvhy8v'
option peerdns '0'
option dns '150.101.158.130'
option ifname 'eth0.2'
option ipv6 'auto'
config interface 'wan6'
option proto 'dhcpv6'
option dns '2001:44B8:41DC:FE00::3'
option peerdns '0'
option reqaddress 'try'
option reqprefix '64'
option ifname '@wan'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0t 2 3 4 5'
config switch_vlan
option device 'switch0'
option vlan '2'
option ports '0t 1'
root@rear-gw:~#
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel