So do I have to reset to factory defaults to get the /jffs/ directory reconstructed correctly?
The actual error message when I try to mkdir scripts is "filesystem is read only".
So if I re-flash the firmware and reset to factory defaults, should that be good enough to get me back to a good starting point?
I've done that multiple times.
/jffs/ is empty. No /scripts directory.
No luck.
I ran
nvram unset jffs2_size
nvram commit
Re-checked the format option and rebooted. /jffs/ comes back with no /scripts directory.
Will re-flashing and resetting to factory defaults fix it? If it will, I'll go ahead and do it. It's not a big deal, I just want to get it fixed.
I would like to test this rule, should we use firewall-start or nat-start?
My router uses the 10.0.0.0/24 range so I will change the rule to:
Code:ebtables -t broute -A BROUTING -p IPv4 -i wl0.1 --ip-dst 10.0.0.0/24 --ip-proto tcp -j DROP
May 29 22:17:05 kernel: wl0.1: received packet with own address as source address
May 30 10:55:23 kernel: wl0.1: received packet with own address as source address
May 30 11:41:05 kernel: wl0.1: received packet with own address as source address
May 30 17:26:47 kernel: wl0.1: received packet with own address as source address
May 30 18:10:53 kernel: wl0.1: received packet with own address as source address
May 31 15:53:03 kernel: wl0.1: received packet with own address as source address
May 31 20:13:35 kernel: wl0.1: received packet with own address as source address
Hi Merlin!
I was taking a look to the changes in latest Asus build for AC-66U (3.0.0.4.376.1123) which was released a couple of days ago and noticed that this issue doesn't seem to be included, any idea why they didn't fix it?
Thanks!
Hi Merlin!
I've recently upgraded to 376.47 from 374.43 and just curious decided to test this feature again.
On 376.47 I am able to ping the router while on guest network, and I'm almost 100% sure that this was not even possible back then when this problem was fixed.
I do see the rule that was missing at that moment and caused this issue so it is not the same cause.
Do you have any ideas of why this is happening?
Thanks in advance
But whats not normal is the guest network being able to contact the internal resources on the main network.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!