| Quote from: AndyH |
| Quote from: chrcoluk | There is no way for merlin or whatever dev to send that MTU to dnsmasq, it simply does not have the functionality to do it.
|
Actually, this is incorrect. You can force an MTU within the dnsmasq.conf file (dhcp-option=26,1492), however it will apply to both IPv4/6.
I'm more than aware as I've been discussing it with Asus' R&D Team for months now. There are issues with native v6 and VPN tunnels (particularly IPSec).
What they should do is allow users to specify the IPv6 MTU in /proc/sys/net/ipv6/*/mtu as this would resolve any issues with the RA (if my understanding is correct).
|
testing this now, seems to be doing nothing tho.
Windows client still reporting 1500 MTU and ipv6 pages refusing to load.
http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2013q2/007173.htmlOk I may have fixed it or at least have a workaround, it isnt really a fix.
Thankfully /proc/sys/net/ipv6/conf/br0/mtu is writeable and it doesnt cause anything to go down, so a simple echo 1492 > /proc/sys/net/ipv6/conf/br0/mtu followed by restarting dnsmasq gets ipv6 working. The dhcp trick seems to do nothing.
After the dnsmasq trick
C:\Windows\system32>netsh int ipv6 show interfaces
Idx Met MTU State Name
--- ---------- ---------- ------------ ---------------------------
1 50 4294967295 connected Loopback Pseudo-Interface 1
11 10 1492 connected Local Area Connection
If I dont do anything and set the above windows setting to 1492, then dnsmasq resets to 1500, this is why I had to fix it on the router. Not to mention fixing every client is much worse than fixing the router.
