Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 7 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 3011 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Port shows Disconnected

sneader

Hi All. Long time Astaro > Sophos UTM9 home user, finally making the switch to Sophos XG Home, due to 50 IP limit.  I have a PC with an on-board NIC, plus two additional 1000MB PCI NICs installed. Port1 is LAN, Port2 is WAN #1 and Port3 is WAN #2.  No matter what I do, one of the NICs (Port2) is in a "Disconnected" state. As soon as I plug the Cable modem into Port2, the lights all come on and everything looks great, but in the XG GUI it says the port is "Disconnected".  If I put that same Cable modem onto Port3, it immediately gets an IP from the ISP and all is well.  Other things I've tried:

  • Set the Zone to None, then back to WAN again, but no change. 
  • Set the Zone to DMZ and set a Static IP in a unique private range, then the interface changes to "Disabled" (that's something!)
  • From CLI, issued the command 'ifconfig Port2 up' but it always responds "Cannot assign requested address" 

Ultimately, I want dual WAN / WAN failover capability, so it's important for me to get this Port2 working.  Any ideas?

Thank you!

-Scott



This thread was automatically locked due to age.
Parents Reply Children
  • 0 in reply to rfcat_vk

    Hi Ian.  Thanks for your willingness to assist.  My original plan was:

    Port1: LAN
    Port2: WAN with Cable Modem, via DHCP
    Port3: WAN with DSL Modem, via PPPoE

    Port1 LAN is OK, and Port3 came up fine with a Public IP via PPPoE.  Port2 is "Disconnected" even though there is connectivity showing on the NIC and the Cable Modem.

    Simply as a test, I switched the configuration around and moved the modems around like this:

    Port1: LAN
    Port2: WAN with DSL Modem, via PPPoE
    Port3: WAN with Cable Modem, via DHCP

    Right away, Port3 received an IP from the Cable Modem provider via DHCP, and Port2 is still "Disconnected".

    Again, to just test things out, I switch them AGAIN, reconfiguring Port2 and Port3 as I originally had them:

    Port1: LAN
    Port2: WAN with Cable Modem, via DHCP
    Port3: WAN with DSL Modem, via PPPoE

    As you can guess, now the DSL works and has a Public IP via PPPoE, and Port2 is "Disconnected".  Port 2 is always "Disconnected". It makes no difference what you do with it.

    Does this help?  How can I make it not be "Disconnected" (or "Disabled" when assigning a Static IP to it, while testing)?

    - Scott

  • 0 in reply to sneader

    Hi Scott,

    you will need to make some changes in the network - WAN Link manager settings for the failing connection.

    Ian

  • 0 in reply to rfcat_vk

    Hi Ian. I am open to your ideas, but I do not think this is an issue with WAN Link Manager.   I have tried setting one port or the other to "Backup" instead of "Active", but Port2 always says "Disconnected".  In WAN Link Manager, Port2 always has a "red" button under "Status".  

    Again, I am open to your ideas of what I should be changing in WAN Link Manager in order to make Port2 start to work.

    - Scott

  • 0 in reply to sneader

    Hi Scott,

    you need to change the setting used by the port to check connectivity.

    My XG setup.

    Ian

  • 0 in reply to rfcat_vk

    Unfortunately, none of this is helping the situation.  The port is still suck in "Disconnected" mode, no matter what I do.  If I plug a switch into it, and call it the DMZ zone, and throw a static IP on it, it's still "Disconnected".  It never leaves this state.  I'm going to buy a new NIC and see if that magically solves the problem, because I don't know what else to do. 

    - Scott