New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FS#769 - Firewall stops traffic / DHCP to WAN interface. #6508
Comments
jow-: Please attach your /etc/config/firewall and the output of "iptables-save" |
ledj: Thanks. I will do this next time it happens. |
ledj: Added requested info, but I don't think it's related anyway. WAN fails to receive an IP from the ISP. Another router (Apple Airport) works and gets IP with DHCP from ISP. Also tried static IP, but the same problem occurs. It seems like the WAN interface is somehow affected by something. Even weirder is that it may suddenly work for a period of time, up to around 3 days. I had an OpenWRT community build "mrfreeze" running on the router before LEDE, and that was rock solid for many months. With LEDE the router somehow has some serious issue, at least the one I have. Wish LEDE would work, or I'll need to find the mrfreeze build again. |
zjttoefs: I'm having the same problem: My ISP provides an IPv4 address via DHCP on the WAN interface and OpenWRT/LEDE cannot retrieve that and ends up with a 169... address. Static configuration also fails. Not sure whether fiddling with the firewall helps. It may be a very popular model, but I am in fact running the same WRT1900ACS v2 as Lars above. Same hardware works fine with DDWRT, but obviously I would prefer to run OpenWRT again. I would appreciate any ideas how to diagnose the problem. |
zjttoefs: Looks like I had a different problem. Now I am suspecting some oddity with my ISP's DHCP service. At least opening the firewall had no impact on the situation. Static IP configuration did work, once I set the MAC address correctly. |
jow-: Closing this as it does not appear to be related to any firewall problem. |
ledj:
From log:
conntrack: generic helper won't handle protocol 47. Please consider loading the specific helper module.
Restarting firewall resolves the issue, and WAN gets DHCP address instant.
I don't know if it happens when a new DHCP lease from my internet service provider on the WAN interface is occurring OR if connection tracking is failing and firewall blocks traffic totally OR some other thing happens :-)
The text was updated successfully, but these errors were encountered: