2WAN setup

[nivuc]

But that's not all, my friend. I've also got a collection of lesser-known but equally impressive cam sites. Take ImLive, for example, this little gem may not have the same fame as the big boys, but trust me, it's got some hidden treasures waiting to be discovered. And then there's Flirt4free, a site that combines the best of both worlds with both free and private shows available. It's like a buffet of babes, and we get to try them all.

Now, I know you're probably thinking, 'But what about niche categories, do you have those covered too?' My dear friend, you underestimate me. I've got categories for all our dirty little fantasies. From the classic MILF and teen categories to more unique ones like BDSM and role play, I've got it all covered. And the best part? These performers are experts in their field, ready to take us on a wild ride and leave us begging for more.

Explore alex_meowmeow's Private Chat Room

Visit alex_meowmeow's private chat room on our free live sex site for live naked girls on cam.

thefreelivesex.com

Check out our collection of brazil webcam models from all over the world!

Get ready to explore the hottest webcam brazil models from around the world who are up for any kind of private live sex cams chat. Discover a popular strip in chat website where all your wildest desires come to life!

stripinchat.com

Hot 18 Cam Chat - Live Sex Shows on Popular Free Cams

Get ready to dive into the hottest 18 cam chat on our site. Experience live sex shows that will leave you begging for more.

nudewebcam.me

Find Hot Girls Stripping in Lingerie - Live Cam leggings Action Daily!

Hot web chicks get down and dirty in lace undies each day in our wild leggings live cams site; Worlds wildest babes in sexy lingeries for your eyes only.

thelingeriestockings.com

But enough about the sites, let's talk about the real stars here, the cam models themselves. I've got a list of the most in-demand and sought-after webcam performers out there. These are the babes that'll make us weak at the knees with just one wink and a smile. We've got the seductive Hotfallingdevil, the dominant and mesmerizing MistressAdina, and the sultry and sensual LaceyVixen. And that's just scratching the surface, my friend.

 

[Tech9]

Dual WAN doesn't work properly on Asus routers. Here is a script fixing some things:

WANFailover - Dual WAN Failover Script

WAN Failover is designed to replace the factory ASUS WAN Failover functionality, this script will monitor the WAN Interfaces using a Target IP Address and pinging these targets to determine when a failure occurs. When a failure is detected in Failover Mode, the script will switch to the...

www.snbforums.com

 

[Ranger802004]

I'm trying to make ASUSwrt-merlin's dual WAN setup work in a specific way, and I'm not sure if I even can.

ASUS router with dual wan turned on in active. LAN side is 192.168.30.1/24
WAN 1 goes to a cable modem. The cable modem is in bridge mode and assigns a public IPv4 address to WAN1. It's configuration/status page is also reachable at 192.168.100.1
WAN 2 goes to a 4G modem. This modem is in bridge mode and assigns a public IPv4 address to WAN2. It's configuration/status page is also reachable at 192.168.5.1

When WAN1 is up:
I want traffic leaving the router, from any LAN client, to public IPs exit via WAN1.
I want traffic destined for 192.168.100.1 to exit via WAN1.
I want traffic destined for 192.168.5.1 to exit via WAN2.
I expect inbound request from WAN1 to match the NAT rules and pass through to LAN IPs as appropriate.
I want inbound requests from WAN2 to be dropped.


When WAN1 is down:
I want traffic leaving the router, from specific LAN clients, to public IPs exit via WAN2.
I want traffic leaving the router, from all other LAN clients, to public IPs to be dropped.
I want traffic destined for 192.168.100.1 to exit via WAN1.
I want traffic destined for 192.168.5.1 to exit via WAN2.
I expect inbound request from WAN2 to match the NAT rules and pass through to LAN IPs as appropriate.

To determine If WAN1 is up/down, I don't want to use the built in "ping some IP" check, but rather use a script to periodically connect to http://192.168.100.1 and parse the response.

I think what I need is a script that does the up/down check via cron, and based on the results swaps between 2 different iptables and interface route definitions. As I try to build this out, the issue I think I am running into is an issue with the default WAN management functionality fighting me. Has anyone gotten something like what I describe above working; and if so, can you share your set up?

For Dual WAN in Failover Mode:
What you'll need to is put the following in a startup script, perhaps wan-event:
Modify IPS List as necessary with 1 IP per line.

# Default route for WAN0 Routing Table
if [ -z "$(ip route list default table 100 | grep -e "$(nvram get wan0_gw_ifname)")" ] >/dev/null;then
  ip route add default via $(nvram get wan0_gateway) dev $(nvram get wan0_gw_ifname) table 100
fi
# Default route for WAN1 Routing Table
if [ -z "$(ip route list default table 200 | grep -e "$(nvram get wan1_gw_ifname)")" ] >/dev/null;then
  ip route add default via $(nvram get wan1_gateway) dev $(nvram get wan1_gw_ifname) table 200
fi
# IP Rule for Traffic destined to 192.168.100.1
if [ ! -z "$(ip rule list from all to 192.168.100.1 lookup wan0 priority 100)"
  ip rule add from all to 192.168.100.1 lookup wan0 priority 100
fi
# IP Rule for Traffic destined to 192.168.5.1
if [ ! -z "$(ip rule list from all to 192.168.5.1 lookup wan1 priority 100)"
  ip rule add from all to 192.168.5.1 lookup wan1 priority 100
fi

# Delete/Create Blackhole rule based on Primary WAN
if [[ "$(nvram get wan0_primary)" == "1" ]] >/dev/null;then
  if [ ! -z "$(ip rule list from all priority 200 | grep -w "blackhole")"
    ip rule del blackhole from all priority 200
  fi
elif [[ "$(nvram get wan1_primary)" == "1" ]] >/dev/null;then
  if [ -z "$(ip rule list from all priority 200 | grep -w "blackhole")"
    ip rule add blackhole from all priority 200
  fi
fi

# Create IP Rules for IPs to be rerouted when WAN0 is down.
# Array of IPs to failover when WAN0 is down.
IPS='
192.168.1.2
192.168.1.3
192.168.1.4
'
for $IP in ${IPS};do
  if [[ "$(nvram get wan0_primary)" == "1" ]] >/dev/null;then
    if [ ! -z "$(ip rule list from $IP to all lookup 200 priority 100)"
      ip rule del from $IP to all lookup 200 priority 100
    fi
  elif [[ "$(nvram get wan1_primary)" == "1" ]] >/dev/null;then
    if [ -z "$(ip rule list from $IP to all lookup 200 priority 100)"
      ip rule add from $IP to all lookup 200 priority 100
    fi
  fi
done

Put these in the nat-start script:

# Masquerade Rule for WAN0
if [ -z "$(iptables -t nat -L POSTROUTING -v -n | awk '{ if( /MASQUERADE/ && /'$(nvram get wan0_gw_ifname)'/ && /'$(nvram get wan0_ipaddr)'/ ) print $3 }')" ] >/dev/null;then
  iptables -t nat -A POSTROUTING -o $(nvram get wan0_gw_ifname) ! -s $(nvram get wan0_ipaddr) -j MASQUERADE
fi
# Masquerade Rule for WAN1
if [ -z "$(iptables -t nat -L POSTROUTING -v -n | awk '{ if( /MASQUERADE/ && /'$(nvram get wan1_gw_ifname)'/ && /'$(nvram get wan1_ipaddr)'/ ) print $3 }')" ] >/dev/null;then
  iptables -t nat -A POSTROUTING -o $(nvram get wan1_gw_ifname) ! -s $(nvram get wan1_ipaddr) -j MASQUERADE
fi
# Masquerade Rule for 192.168.100.1
if [ -z "$(iptables -t nat -L POSTROUTING -v -n | awk '{ if( /MASQUERADE/ && /'$(nvram get wan0_gw_ifname)'/ && /192.168.100.1/ ) print $3 }')" ] >/dev/null;then
  iptables -t nat -A POSTROUTING -o $(nvram get wan0_gw_ifname) -d 192.168.100.1 -j MASQUERADE
fi
# Masquerade Rule for 192.168.5.1
if [ -z "$(iptables -t nat -L POSTROUTING -v -n | awk '{ if( /MASQUERADE/ && /'$(nvram get wan1_gw_ifname)'/ && /192.168.5.1/ ) print $3 }')" ] >/dev/null;then
  iptables -t nat -A POSTROUTING -o $(nvram get wan1_gw_ifname) -d 192.168.5.1 -j MASQUERADE
fi

The only thing I did not cover is your custom request for curl to 192.168.100.1 for output.