Comments
-
My understanding was that the underlying Operating System is automatically updated to keep the system secure and there was a reason for it trying to get updates.
-
I see. So, yes - to link monitor on the primary WAN interface, but no - to adding modem to multi-wan in failover mode? Setting up multi-wan failover mode allows to configure some other options like "Gradual Failback" or multi-wan notifications. I think that is a good idea?
-
Yes, I meant enabling link monitor on the other external interface, not the modem interface. The external interface will go down only when the device connected to it (ISP router) is off as much as I understand. But when there are Internet connection issues at the ISP, the ISP router does not really power off, so, Firebox…
-
I read "In Fireware v12.1 and higher, the modem is available as an external interface, and modem failover is enabled. The modem has a higher metric (lower priority) than other external interfaces. If all other external interfaces become unavailable, traffic automatically fails over to the modem interface." Does this mean I…
-
Thank you, James. I will see how it goes. Firs time is always interesting :smile: I also need a failover of BOVPN Virtual Interface for AWS tunnel, and not sure about this either.
-
Thank you, James. I will try that and post back.
-
Thank you for your response, James. Good to know that status type users can use the CLI and export config command too. I suppose the Firebox is using its external IP, as FTP server at AWS is on a different subnet. Like I mentioned earlier the VPN Interface on the firewall tunnels the traffic between the local Firebox…
-
I think about adding FTP packet filter with policy based routing from Firebox to the Auvik server on 172.31.0.0/16 subnet and route outbound traffic via that VPN Interface. Will then Firebox use its local IP address as source IP?
-
So, this route was added automatically when VPN Interface was created (picture below) But the Firebox seems to use 0.0.0.0 as source IP when sending the FTP traffic to the server on 172.31.0.0/16 subnet and that is not working.
-
Thank you for clarifying this. It was confusing because a switch usually has two fixed positions, on and off, and the power switch on the back functions like a broken switch that has only one position :)
-
The Auto Gateway setting in Automatic Broadcast Control section of one of the HP ProCurve switches was set to Yes and was causing this issue. Switching that to No resolved the issue.
-
I replicated the issue on another desktop computer running Windows 10. Apparently, this is not Surface or dock related. I am looking at HP ProCurve switches, that computers and firebox are connecting to: the desk, where the computers get the default gateway assigned by DHCP correctly, is connected to the same switch as…
-
Thank you Bruce. I will take a look at that setting.