I've had absolutely same issue with builds starting from 04/01. Reverted back to 03/19 build, everything works perfectly. Not completely clear what r43k3n means under "Doing a firstboot or installing the firmware again". After performing sysupgrade with 04/01 and 04/02 builds(both with or without settings preservation), I've tried tftp restore with factory images of same builds, same reboot behavior always, immediately after connecting WAN port.
No logs too, this case definitely requires remote syslog server setup.
I was originally referring to the issue of router restarting itself as soon as it connected to the internet. The solution to this problem might be doing a firstboot and doing the a clean configuration from the start. You can also use sysupgrade -n that will install the firmware again erasing the current configuration.
I've seen reports of similar issue on another forum and this was the proposed solution.
@r00t I have been comparing installed packages from my previous working vanilla LEDE 17.01 with no logged messages ("IP packet with unknown IP version=15 seen") and I found 3 packages that your images does not have, maybe this can help.
The packages are:
- kmod-ipt-nat-extra
- kmod-nf-conntrack-netlink
- kmod-nf-nathelper-extra
I don't know if you can try to add or at least compile aside and I give a try adding it to see if with this the error message goes away.
Thanks.
These packages were included before April and I think another user also asked about the same error message before, so I doubt that would help.
@r00t If I'm not wrong I'm on the build of 2017-04-01 (r3902) and with that this packages were not included. Will try later with latest stable build (2017-04-04) I will report about it.
Exactly, builds including and after 2017-04-01 don't contain these packages. You'd need to try 2017-03-19, which includes most or all of the modules you mentioned (you need to check - I don't recall).
@kyledawg92 @xakep Could you please this image https://data.oesterling.me/f/60b306e71e/?dl=1 and let me know if you have the same issues with it? It lacks all patches. Just want to see if one of them causes this problem and if it does, it would be awesome if one of you could volunteer to try a couple of builds in a row because we'd then need to narrow it down to a particular patch and I can't reproduce this issue on my end. If you have a chance please also try the latest nightly first just to make sure the issue didn't appear because of some upstream issues that's already fixed in the latest trunk. Thanks!!
I might be able to try more builds later, but I'd have to wait for the roommates to go to sleep ha. I can tell you this though: I'm using the build hobbsAU posted here, if you can somehow compare patches and deduce the problem via that way.
@r00t if you get any spare time and compile Unbound that would make it easier for me. I will try to work on it and see if I can get it to work with dnscrypt.
The problem is that I don't have older builds to test. So far I have flashed latest stable firmware, it have the very same problem with "IP packet with unknown IP version=15 seen" but VPN works.
If you want to cross check package list, this were all the packages installed over vanilla 17.01 and there were no message: https://pastebin.com/iqKBmRLn.
You can just go through the commits on github and download any build you need. Here's a direct link to the one I mentioned: https://github.com/infinitnet/lede-ar71xx-optimized-archer-c7-v2/blob/26fa472ae2d3f042b3eba4622558bb0b492af729/lede-ar71xx-generic-archer-c7-v2-squashfs-sysupgrade.bin
Right! I forgot to check the commits. Will try later and report back.
Thanks, I'll try this image tomorrow(ie Friday).
Will these patches also work for Archer V7 V1, or does this depend on the packages individually?
Tried the build you said and OpenVPN still shows the message every minute, but I think I found the cause and for now a solution, but I don't know if you can implement it in your builds.
The idea came from here: https://www.toofishes.net/blog/openvpn-and-aoe-interaction/, the problem is with the ata over ethernet, with the same solution of that page "echo 'lo' > /sys/module/aoe/parameters/aoe_iflist" the warning stops appearing.
The packet can be seen with a tcpdump:
22:09:40.016232 mac-address (oui Unknown) > Broadcast, ethertype AoE (0x88a2), length 32:
0x0000: 1000 ffff ff01 0000 0000 0000 0000 0000 ................
0x0010: 0000 ..
22:09:40.017532 IP xxx.xxx.xxx.xxx.xxxx > xxx.xxx.xxx.xxx.xxxx: Flags [.], ack 220529, win 207, length 0
22:09:40.020533 mac-address (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 36:
0x0000: 1000 ffff ff01 0000 0000 0000 0000 0000 ................
0x0010: 0000 ..
While I was checking packages I see your builds have a few packages that vanilla 17.01 does not have and one in special I think is the problem:
kmod-aoe - 4.4.59-1
kmod-arptables - 4.4.59-1
kmod-ata-ahci - 4.4.59-1
kmod-ata-artop - 4.4.59-1
kmod-ata-core - 4.4.59-1
kmod-ata-marvell-sata - 4.4.59-1
kmod-ata-nvidia-sata - 4.4.59-1
kmod-ata-pdc202xx-old - 4.4.59-1
kmod-ata-piix - 4.4.59-1
kmod-ata-sil - 4.4.59-1
kmod-ata-sil24 - 4.4.59-1
kmod-ata-via-sata - 4.4.59-1
I'm not sure if all this packages are required, but the kmod-aoe I think it is the ATA over Ethernet that caused the warning.
So far I have the very last stable build and so far it is working flawlessly and with no openvpn warning.
Build from https://data.oesterling.me/f/60b306e71e/?dl=1 works absolutely same way as from 04.01 and 04.02, ie non stop reboots after connecting WAN.
Thanks for testing. It's not one of the patches then, which makes this harder to debug. Could you:
1.) Apply the sysctl.conf from https://raw.githubusercontent.com/lede-project/source/master/package/base-files/files/etc/sysctl.conf (reboot afterwards because sysctl -p doesn't reset all settings) before plugging in your WAN port?
2.) Try a vanilla trunk build newer than April 1st? I can compile one for you if you like.
Most changes apart from the patches and the sysctl.conf have been removing unused packages which shouldn't cause reboots, so it's not too unlikely that this is caused by upstream changes.
Hey @r00t just d/l your latest nightly and ran iperf. Same test setup as before.
Connecting to host 192.168.1.20, port 5201
[ 4] local 192.168.1.63 port 58204 connected to 192.168.1.20 port 5201
[ ID] Interval Transfer Bandwidth Retr Cwnd
[ 4] 0.00-1.00 sec 46.5 MBytes 390 Mbits/sec 0 2.18 MBytes (omitted)
[ 4] 1.00-2.00 sec 62.0 MBytes 520 Mbits/sec 0 2.84 MBytes (omitted)
[ 4] 0.00-1.00 sec 46.1 MBytes 387 Mbits/sec 0 2.84 MBytes
[ 4] 1.00-2.00 sec 45.8 MBytes 384 Mbits/sec 1 2.84 MBytes
[ 4] 2.00-3.00 sec 60.0 MBytes 503 Mbits/sec 0 2.84 MBytes
[ 4] 3.00-4.00 sec 62.0 MBytes 520 Mbits/sec 0 2.84 MBytes
[ 4] 4.00-5.00 sec 55.1 MBytes 462 Mbits/sec 0 2.84 MBytes
[ 4] 5.00-6.00 sec 58.8 MBytes 493 Mbits/sec 0 2.84 MBytes
[ 4] 6.00-7.00 sec 52.5 MBytes 440 Mbits/sec 0 2.84 MBytes
[ 4] 7.00-8.00 sec 60.1 MBytes 504 Mbits/sec 0 2.84 MBytes
[ 4] 8.00-9.00 sec 59.5 MBytes 499 Mbits/sec 0 2.84 MBytes
[ 4] 9.00-10.00 sec 46.0 MBytes 386 Mbits/sec 0 2.84 MBytes
[ ID] Interval Transfer Bandwidth Retr
[ 4] 0.00-10.00 sec 546 MBytes 458 Mbits/sec 1 sender
[ 4] 0.00-10.00 sec 550 MBytes 461 Mbits/sec receiver
iperf Done.
Awesome, thank you! So there's some larger improvement finally, but still plenty of room for more. Seems to be same improvement you got from removeing link layer iptables modules. Something else must still slow this build down compared to vanilla LEDE.
@dacarrs Thanks a lot for figuring this out. AOE modules are indeed not needed normally. I removed them in today's release - let me know if that fixed the error.
@xakep You could try today's release as well. I re-added a couple of netfilter modules I removed with the April 1st release. I doubt this would cause reboots, but who knows.