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

firewall home - WAN interface not allowing me to register firewall but is allowing traffic through

Setup Sophos Firewall Home edition, booted and needed to change WAN interface from default DHCP to Static IP (due to ISP).  I must have missed a step as devices on my home network can get out to the internet.  -- i.e. my PC I'm typing this up on is inside and is getting to sophos community site. --

However if I try to register firewall it times out and asks if I want to change interface configuration.  (Can't connect to registration service)

So what did I miss?

General settings

Name PortB

Hardware PortB

Network Zone WAN

IPv4 configuration is checked

IP assignment Static is checked

IPv4/mask  x.x.x.47 / 255.255.255.128 

Gateway name PortB_GW

Gateway IP x.x.x.126



Edited TAGs
[edited by: Erick Jan at 12:42 AM (GMT -7) on 30 Sep 2024]
Parents
  • I did try that and didn't fix it. So went back to basic like double checking how I cabled my firewall device.  oops, wrong cable for WAN.  swapped that and now my firewall can get to internet and register my firewall but everything on my home network can't get to the internet.

    my switch has a WAN port., once I noticed my mistake in cabling, I placed the cable that was in this port into the firewall WAN port, and moved the firewall LAN cable to the switch WAN port. I then check the switch and not getting a connection to the firewall.  So I checked and made sure the GuestDHCP was running on the firewall and even made a static IP for the switch based on MAC address.  switch still not getting connected. says WAN IP is 0.0.0.0

    I've tried setting the switch to use DHCP and use static IP, On static I used the "reserved" (yah I know not true DHCP reserved) and the firewall IP.  still get 0.0.0.0 for WAN IP.

    So what do I have to do to get the firewall and the switch to play nice and talk to each other?

    NOTE: I currently have the switch cabled like before firewall (directly connected to ISP router), I have the firewall LAN connected to switch (non-WAN port) and also directly connect to ISP router.  Just to make easy of troubleshooting, all devices can get to the internet and I can connect to firewall for management.

  • Hi,

    why do you feel the need of a switch between the XG and the internet modem? The XG can manage many different types of interfaces.

    Ian

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v21 GA

    If a post solves your question please use the 'Verify Answer' button.

  • While checking both cabling and configuration on firewall & my D-Link DSR-250, I noticed one thing.  Some where along the way I change the firewall LAN port to an IP that’s inside the DSR-250 DHCP range.  I changed the firewall LAN back to 172.16.16.16 and now can’t connect to web console.  Since the 172.16.16.16 is not within the DSR-250 IP range it tried to go to the internet.  Have to figure out how to keep it from doing that, maybe static route and or lvan setup.

     

    My original setup was as follows. My DSR-250 was connected to ISP router and the DSR-250 had two non-managed routers (so had enough ports) in two other rooms.  The DSR-250 did my DSCP internally and have about 20 reserved IPS.  My original thought to place the firewall between the ISP router and the DSR-250, then over time migrate to using firewall DHCP as lots of configuration changes both in devices and scripts, etc. if switching DHCP setup.  Or, do switch on mass once had everything researched and ready to change.

     

    Since that all blew up in my face I am where I am now.  I can get access to the firewall console (IP set to one of DSR-250’s) but can’t get WAN port on the DSR-250 to connect to firewall I think that is because the IP is within the DSR-250 DHCP range and not allowed.  OR I can’t get to the firewall console (IP 172.16.16.16), and nothing works.

     

     guess back to drawing board. :-(

  • The 172 address is an internal address used by the XG, if you have setup firewall rules then the 172 address would be nat'ed and not seen on the WAN interface..

    You will need to disable the NAT on your DSR and enable a dynamic IP address on the DSR for the XG to connect to. Change the XG WAN interface to dynamic.

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v21 GA

    If a post solves your question please use the 'Verify Answer' button.

Reply
  • The 172 address is an internal address used by the XG, if you have setup firewall rules then the 172 address would be nat'ed and not seen on the WAN interface..

    You will need to disable the NAT on your DSR and enable a dynamic IP address on the DSR for the XG to connect to. Change the XG WAN interface to dynamic.

    XG115W - v20.0.2 MR-2 - Home

    XG on VM 8 - v21 GA

    If a post solves your question please use the 'Verify Answer' button.

Children
No Data