Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 729
  • Last Modified:

Watchguard Firewall Network configuration

Hi

I have a watchguard firewall which is currently connected to an adsl router configured in drop in mode.

I have just had a fibre connection installed and have been given the following network information for it

89.198.0.105 - default gateway
89.198.0.106 - usable IP Address

Subnet mask 255.255.255.252

What is the best way to configure the network settings in the firewall, is it best to use bridged mode?

Thanks
0
Nick_D
Asked:
Nick_D
  • 2
1 Solution
 
miller3773Commented:
what model of the watchgaurd?

is your adsl router your only Internet connection?
0
 
Nick_DAuthor Commented:
3 series, yes the watchguard currently plugs into a peplink device in drop in mode. The fibre connection is to replace the adsl connections.
0
 
dpk_walCommented:
As I understand currently your WG is in drop-in mode; which means all server behind it would be on public IP.
Now as you are changing ISP; you can continue to remain in drop-in mode; but then you would have to manually change IP address on each and every device behind WG.
OR you can configure the devices behind WG on a private IP subnet; may be also use DHCP [if applicable] and configure WG in routed mode.

The only thing you should watch out for is:
In drop-in mode there is NO NAT; whereas moment you opt for routed or gateway mode; there would be NAT.
If you have any application which BREAKS with NAT then remain in drop-in mode or convert to routed for ease of change of ISPs.

Please let know if you need any more details.

Thank you.
0
 
Nick_DAuthor Commented:
This was the issue, I forgot to enable NAT on the outbound connection.

Thanks
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now