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 119084 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
    Make sure the ether 0 is connected to your LAN switch. Set your IP V4 on our client nic to 172.16.16.17 , and your gateway to 172.16.16.16 If your your client is already on the domain use the domain controller IP for your clients DNS and the XG firewall as your secondary DNS
Reply
  • 0
    Make sure the ether 0 is connected to your LAN switch. Set your IP V4 on our client nic to 172.16.16.17 , and your gateway to 172.16.16.16 If your your client is already on the domain use the domain controller IP for your clients DNS and the XG firewall as your secondary DNS
Children
  • 0 in reply to TalaRyu

    Just to keep this going to the extent it helps the OP, I am having the exact same issue, and it's driving me a little batty...

    Circumstances: (1) installed current version of firewall software successfully (as denoted by final line "password" after install sequence, and first boot and install of default config)... I've repeated this several times with bootable USB's from OSX, Windows and Ubuntu; (2) hardware being used is a Jetway Intel dual NIC Celeron N2930 Quad Core w/ 8GB RAM and a Crucial 250GB mSATA drive (tested and runs a variety of linux distro's just fine); (3) other data points: (i) it successfully configures the client connected to it with the DHCP server at 172.16.16.17 every time; (ii) I can SSH admin@172.16.16.16 w admin password indicating I've accessed the firewall, however I have to login to the https page to sign the license; (iii) I can successfully ping 172.16.16.16; (iv) confirmed gateway and DNS are 172.16.16.16 on the client; (v) have tried swapping the ethernet ports but connection fails from client; (vi) have tried accessing the https://172.16.16.16:4444 from Mac, Windows and Linux and failed every time and on every platform; (vii) have tried direct ethernet connection from Jetway/Sophos to the client and through a network LAN bridge; (viii) I've left it running for hours at a time to clear the "4 hours" referenced here multiple times; (ix) reviewed settings in BIOS of Jetway and all seem fine although open to brainstorms here on the CSM settings; (x) when an internet source is plugged into the second NIC ethernet port it passes internet traffic through to the DHCP client while still preventing access to the default admin IP.  I've read other reports of Jetway setups working with the Sophos XG firewall.

    So what am I missing....  

  • 0 in reply to silverlight
    Not sure. Try accessing it from the public IP, and/or adding the IP the trusted sites in you browser. Other that that I can't think of anything else to try. But if I do I will post it.
  • 0 in reply to TalaRyu
    Thanks for the quick response. Building another little unit over the long weekend to see if I can get it working...
  • 0 in reply to silverlight
    Just an update, I assembled a low cost PC last night and accessed the default IP on the first try. So I definitely suspect it's a hardware issue with the Jetway hardwire and perhaps drivers in the sophos linux install. FWIW for other folks building a little setup in the future, successfully used the following gear. total cost under $300 from Amazon prime and one could easily cut corners to reduce cost (I just spec'd up a little in case this didn't work and I had a computer capable of doing other things well).
    (1) Gigabyte + Celeron J1900 motherboard/CPU (GA-J1900N-D3V)
    (2) 2x 4GB Patriot RAM (PSD34G1333L2S)
    (3) Kingston SSD 120gb (SV300S37A/120G)
    (4) MiniBox M350 Mini ITX case
    (5) Binzet B00PK0N14M external power supply
    (6) Mini-Box picoPSU-160-XT power supply
    (7) Noctua 40mm quiet fan (NF-A4x10)
  • 0 in reply to silverlight

    I have the same problem as silverlight - I have a little micro PC, runs Windows 7 fine, just blew it away and loaded on Sophos XG.

    I read about this 172.16.16.16 thing, thought it was a little odd but just thought "no worries, I'll just plug it into my layer 2 switch here, just add a secondary address on my old XP VM at 172.16.16.10 then log in and change the IP address..."

    First thing I didn't realise was that it runs a DHCP server so after about 15 mins my wife gets cut off the VOIP conference call she was on (with people in the US, Asia and Australia!), loses her VPN and everything starts hanging. Turns out she just picked up an IP off this effing firewall and she's really mad at me. So I pulled out the network cable and got her sorted with an ipconfig/release&renew. Now I plugged my PC directly into the first port, got an IP, I can ping 172.16.16.16 fine but can I get to https://172.16.16.16:4444? Chrome just says unable to access the network.

    Now I understand people might be blaming the NICs but Windows was running fine on this little thing and I can ping it fine. I just cannot believe Sophos make you jump through this stupid EULA acceptance thing via the web URL, why can't I do this at the console then set some "sensible" network parameters, if you are going to use something as stupid as 172.16.16.16 at least let me change it.

    If I get this working, can I change the network config before doing the license activation, because trying to get this thing to talk to the internet means I'm going to have to configure a vyos router and plug it into my vmware lab? I mean this just seems really retarded to do it like this.

    Anyway I'm getting to the point now where I'm just going to reformat and load on Smoothwall or something else and just not bother with this.

    Has anyone got a fix for this?

  • 0 in reply to PaulRoberts
    Ok I just found another post that said check the time in the BIOS. Sure enough mine was set to 2012, so 4 years out! I set it to the correct date and voila, I can now get into the web interface. I guess this is because they are using https over port 4444, clocks need to be in sync for https to work.

    First thing I need to do is shut down this bloody DHCP server.
Unfiltered HTML