Skip to content
TheChatArchiveThe Chat Archive
Claudeclaude-3-7-sonnet-20250219-thinking-32k· AnthropicHugging Face LMArena Human Preference 140K

I have an Edgerouter 6P at my home acting as the main router. Some while I go I set up…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with grok-3-mini-high’s answer.
  1. User

    I have an Edgerouter 6P at my home acting as the main router. Some while I go I set up load balancing with my dad. We somehow locked our home server to only a single interface, basically removing it from the balancing process cause it hosts some public facing stuff and load balancing would have broken it. I would like to disable that now and instead of load balancing set up just a failsafe where eth0 is prioritized and eth1 is just a backup that will only get used if eth0 fails. I do not remember how we locked the home server to eth0... can you help me find out how we likely did it and then roll back these settings?

  2. Claude Assistant

    To find how you locked your home server to eth0 and then set up failover instead of load balancing, try these steps:

    First, let's figure out how you likely restricted the server to eth0:

    1. SSH into your EdgeRouter or use the CLI tab in the web interface

    2. Run these commands to check for policy-based routing:

      show configuration | grep modify
      show firewall group
      show firewall name
      
    3. Check for server-specific NAT rules:

      show nat rules
      
    4. Look at your load balancing configuration:

      show load-balance
      

    The most common method would be using policy-based routing or creating a specific firewall rule that forces traffic from your server's IP to use eth0.

    Once you identify how it was done, you can:

    1. Remove the load balancing and server restriction:

      configure
      delete load-balance group WAN_GROUP  # Your group name might differ
      # Delete the server-specific rule you found
      commit
      
    2. Set up failover instead:

      configure
      set load-balance watchdog pinghost-1 address 8.8.8.8
      set load-balance group WAN_FAILOVER interface eth0 weight 10
      set load-balance group WAN_FAILOVER interface eth1 weight 1
      set load-balance group WAN_FAILOVER interface eth1 failover-only
      set protocols static route 0.0.0.0/0 next-hop-interface eth0 distance 10
      set protocols static route 0.0.0.0/0 next-hop-interface eth1 distance 20
      commit
      save
      

    Would you like me to explain any of these commands in more detail?

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.