Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 48 replies
  • Answers 1 answer
  • Subscribers 41 subscribers
  • Views 119085 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

Still can't access default IP!

ChristopherGault

Hello, I am still unable to connect to the default address with the home version of XG Firewall. I have tried everything under the book and this is just a nightmare! It appears that the DHCP server during initial setup isn't working and my network (even IP scanners) can't find any live address of 172.16.16.16, it appears not to be broadcasting anything! If I hardline into the server that is running XG and set a static IP what am I supposed to do with Gateway and DNS? Also during first boot there were error messages containing to page cache, I dont know if thats a problem but I am sure having hell with this small mistake Sophos made...



This thread was automatically locked due to age.
Parents
  • 0
    Tried with all the suggestions given in this forum. I still cannot access the XG Firewall web interface over the default IP.
    However when I install the firewall in HyperV everything work smoothly.
  • 0 in reply to KshemankarBhore
    My theory is that you are both suffering from some kind of incompatible hardware with the Sophos. Can you list the NIC specifications here and that may help determine if it is the drivers for the NIC? I am using a atom d2500cc with intel 82574L onboard NICs. I also added a broadcom 10/100 fast ethernet PCI expansion NIC to the build. I don't remember the NIC specifics but it is using the broadcom netxtreme II CNIC Driver and is working fine.

    My opinion is that getting ESXi or Hyper-v working is not too difficult. I does make the networking concepts more difficult because you will be dealing with virtual networks and interfaces as well as the physical ones. I think it is a great way to continue learning but if this is an essential router in your home I would try something else.
Reply
  • 0 in reply to KshemankarBhore
    My theory is that you are both suffering from some kind of incompatible hardware with the Sophos. Can you list the NIC specifications here and that may help determine if it is the drivers for the NIC? I am using a atom d2500cc with intel 82574L onboard NICs. I also added a broadcom 10/100 fast ethernet PCI expansion NIC to the build. I don't remember the NIC specifics but it is using the broadcom netxtreme II CNIC Driver and is working fine.

    My opinion is that getting ESXi or Hyper-v working is not too difficult. I does make the networking concepts more difficult because you will be dealing with virtual networks and interfaces as well as the physical ones. I think it is a great way to continue learning but if this is an essential router in your home I would try something else.
Children
Unfiltered HTML