Backup WAN

[Milkman]

So I was thinking of the backup WAN functionality. I wonder how the average person affords such a thing.

That said, there is a service out there that is basically very very low cost LOW USAGE 3G/4G functionality. The only thing is if I have a Torrent running, and I am not home, I don't want that thing burning through my data.

Is there any good way on a PC to prevent that, and more importantly is that something planned for the backup WAN where you can have alternate rules???

 

[RMerlin]

No idea what are Asus's plans regarding Dual WAN. On my end I have no plan on changing the current implementation.

 

[Nerre]

The only thing is if I have a Torrent running, and I am not home, I don't want that thing burning through my data.

I had similar thoughts earlier, for non-corporate use a backup WAN need to be handled very differently (because it's genreally slower, more expensive and might have traffic limits).

http://forums.smallnetbuilder.com/showthread.php?t=8788

 

[Martineau]

So I was thinking of the backup WAN functionality. I wonder how the average person affords such a thing.

That said, there is a service out there that is basically very very low cost LOW USAGE 3G/4G functionality. The only thing is if I have a Torrent running, and I am not home, I don't want that thing burning through my data.

Is there any good way on a PC to prevent that, and more importantly is that something planned for the backup WAN where you can have alternate rules???

I use the wan-start and firewall-start events to only allow limited services if a switch to 3G modem has occurred.

Alas 374.33-SDK5 (RT-N66U) still doesn't automatically switch back to ADSL from 3G, so my wan-start script still has to address this ASUS ommission.

As can be seen in the log below, when the switch to 3G occurs, I issue '-j DROP' for the Transmission port 51843 and only reinstate the '-j ACCEPT' when the ADSL WAN connection is restored.

Perhaps you can modify your 'iptables' to futher limit your 3G modem traffic?

17:58:49 WAN Connection: Ethernet link down.
17:58:49 stop_nat_rules: apply the redirect_rules!
17:59:45 rc_service: wanduck 307:notify_rc restart_wan_if 0
17:59:45 pppd[873]: Terminating on signal 15
17:59:45 pppd[873]: Connect time 450.1 minutes.
17:59:45 pppd[873]: Sent 47496536 bytes, received 1549619518 bytes.
17:59:45 miniupnpd[1239]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
17:59:46 pppd[873]: Terminating on signal 15
17:59:47 stop_wan(): perform DHCP release
17:59:47 kernel: br0: port 1(vlan1) entering disabled state
17:59:47 kernel: vlan1: dev_set_promiscuity(master, 1)
17:59:47 kernel: br0: port 1(vlan1) entering listening state
17:59:47 kernel: br0: port 1(vlan1) entering learning state
17:59:47 kernel: br0: topology change detected, propagating
17:59:47 kernel: br0: port 1(vlan1) entering forwarding state
17:59:54 miniupnpd[1239]: Failed to get ip address for interface ppp0
17:59:56 rc_service: wanduck 307:notify_rc restart_wan_line 1
17:59:56 rc_service: restart_wan_line 1 is waitting restart_wan_if 0...
17:59:57 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp1__dev_ttyUSB0)!
17:59:57 (nat-start): 2020 Martineau NAT customisation starting.... []
17:59:57 (wan-start): 2013 Martineau customisation starting.... /jffs/scripts/wan-start 1
17:59:57 (wan-start): 2013 wan-start LOCKED Sat Oct 5 17:59:57 DST 2013
17:59:57 (wan-start): 2013 wan-start Interface 1 Secondary WAN start detected....
17:59:57 (nat-start): 2020 nat-start LOCKED Sat Oct 5 17:59:57 DST 2013
17:59:57 (nat-start): 2020 Adding NAT route for Martineau TP-LINK TD-8816 ADSL modem : DSL.xxx.xxx.xxx eth0
17:59:57 (nat-start): 2020 nat-start UNLOCKED Sat Oct 5 17:59:57 DST 2013
17:59:57 (wan-start): 2013 Attempting to identifying the WAN-start event - DSL or 3G
17:59:57 (firewall-start): 2089 firewall-start LOCKED Sat Oct 5 17:59:57 DST 2013
17:59:57 ddns: clear ddns cache file for server/hostname change
17:59:58 ddns update: ez-ipupdate: starting...
17:59:58 (firewall-start): 2089 Blocking Port 51413 for Transmission BitTorrent as using 3G Modem
17:59:58 (firewall-start): 2089 Blocking ALL alternative DNS access from xxx.xxx.xxx.0/255.255.255.0
17:59:58 (IPTablesDump.sh): 2116 Started [Firewall-start]
17:59:58 (firewall-start): 2089 firewall-start UNLOCKED Sat Oct 5 17:59:57 DST 2013
17:59:59 ddns update: connected to members.dyndns.org (DYN.xxx.xxx.xxx) on port 80.
18:00:00 ddns update: request successful
18:00:00 ddns update: asusddns_update: 0
18:00:00 ddns: ddns update ok
18:00:01 (TrackUPTime.sh): 2199 RT-N66U Uptime logged to /tmp/mnt/RT-N66U/Session_UPTIME.txt
18:00:01 (ledsoff.sh): 2197 LEDs now switched OFF
18:00:02 WAN Connection: WAN was restored.
18:00:04 rc_service: service 2222:notify_rc restart_leds
18:00:33 pppd[1998]: Timeout waiting for PADO packets
18:01:48 pppd[1998]: Timeout waiting for PADO packets
18:02:01 (wan-start): 2013 This is the 3G Failover starting event.....
18:02:01 (wan-start): 2013 Scheduled 03:00 Reboot to restore ADSL connection.....
18:02:01 (Unblock-US.sh): 2523 Updating Unblock-US authentication
18:02:31 (Unblock-US.sh): 2523 Status 2013-10-05 18:02:31 (40.0 KB/s) - '/tmp/mnt/RT-N66U/Unblock-us-status' saved [6/6]
18:02:31 (Unblock-US.sh): 2523 Unblock-US authentication complete
18:02:31 (Notify_WAN_IP.sh): 2542 Notification WAN start e-mail running...
18:02:31 (Notify_WAN_IP.sh): 2542 Notification WAN start e-mail DEBUG wan0_primary=0
18:02:31 (Notify_WAN_IP.sh): 2542 3G Modem connection...!!!!!! 3G.xxx.xxx.xxx
18:02:31 (Notify_WAN_IP.sh): 2542 Previous WAN IP xxx.xxx.xxx.xxx
18:02:31 (Notify_WAN_IP.sh): 2542 Current WAN IP 3G.xxx.xxx.xxx
18:02:31 (Notify_WAN_IP.sh): 2542 WAN IP changed!!!
18:02:38 (Notify_WAN_IP.sh): 2542 Notification WAN start e-mail sent using smtp-mbb.three.co.uk:25
18:02:38 (IPTablesDump.sh): 2603 Started [Wan-start]
18:02:38 (wan-start): 2013 Martineau customisation complete....

Regards,