derekperrin / rt-n56u

Automatically exported from code.google.com/p/rt-n56u
0 stars 0 forks source link

PPPoE reconnect results in WiFi connection blocked by Firewall #1429

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Connect to ISP using PPPoE (via ADSL2 modem in bridge mode)
2. Connection is reset (by ISP, or modem or a bug in pppd demon, which resets 
exactly at 24th hour mark)

3. Try using internet via any WiFi clients after making sure the connection is 
alive (log has "RT-N56U: WAN up (ppp0)" entry)

What is the expected output? What do you see instead?
WiFi clients should continue to get internet access, but in reality all WiFi 
clients seems to have lost access to internet. they can't even access 
http://my.router

What version of the product are you using? On what operating system?
Firmware: 3.4.3.9-091 

Please describe the problem as detailed as it's possible.
The connections from WiFi clients seems to have blocked by Firewall. The 
transmission demon will happily continue to use the internet connection.
I found that executing "restart_firewall" command seems to fix the issue.

I have set the "Run After WAN Up/Down Events:" script to below

#!/bin/bash

### Custom user script
### Called after internal WAN up/down action
### $1 - WAN action (up/down)
### $2 - WAN interface name (e.g. eth3 or ppp0)
logger "WAN Event" $1 $2
    logger "Restart Firewall"
    restart_firewall
    logger "Done!"

fi

Original issue reported on code.google.com by Adarsha...@gmail.com on 20 Feb 2015 at 5:48

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
ISP with PPPoE also.
I have similar problems after upgrading from 3.4.3.9-081 to .091, the router 
would block some random connections, like verifying Hotmail e-mail addresses in 
Windows Live Mail or blocking that annoying KMPlayer side panel that connects 
to internet when the player starts, causing a 10-15 seconds delay in opening 
KMPlayer.
The browsers still have access to internet.
This is on LAN connection, not WLAN. Disabling ad enabling back the LAN fixes 
the problem, or rebooting the router. 
I moved back to 3.4.3.9-081, will update this post if the problem still appears.

Original comment by samarea...@gmail.com on 23 Feb 2015 at 10:04