dave14305
Part of the Furniture
If you search the system log fori reran with skynet restarted & here is output:
firewall-start, does it always show wan0?
Code:
grep firewall-start /jffs/syslog.log-1 /jffs/syslog.log
If you search the system log fori reran with skynet restarted & here is output:
firewall-start, does it always show wan0?grep firewall-start /jffs/syslog.log-1 /jffs/syslog.log
no, this is the orderIf you search the system log forfirewall-start, does it always showwan0?
Code:grep firewall-start /jffs/syslog.log-1 /jffs/syslog.log
I guess this is the heart of the problem. The wan interface name is part of the Skynet rules, and yours seems to start as eth0 then change to wan0. Never seen that before.no, this is the order
Jan 4 15:13:39 custom_script: Running /jffs/scripts/firewall-start (args: wan0)
Jan 4 15:13:39 custom_script: Running /jffs/scripts/firewall-start (args: wan0)
Dec 31 18:01:11 custom_script: Running /jffs/scripts/firewall-start (args: eth0)
Dec 31 18:01:11 custom_script: Running /jffs/scripts/firewall-start (args: eth0)
Dec 31 18:01:24 custom_script: Running /jffs/scripts/firewall-start (args: wan0)
Jan 4 15:13:39 custom_script: Running /jffs/scripts/firewall-start (args: wan0)
i reposted log with lockfile arguments above, do you think that could be the issue?I guess this is the heart of the problem. The wan interface name is part of the Skynet rules, and yours seems to start as eth0 then change to wan0. Never seen that before.
We use essential cookies to make this site work, and optional cookies to enhance your experience.