Link to home
Start Free TrialLog in
Avatar of joelisthedude
joelisthedude

asked on

Public IP setup with AT&T and WatchGuard XTM

Ok Experts, I'm calling on you in my most desparate time. I have a situation that is complicated, and there is a lot to read, I will try to keep it clear.

I am currently at one of my field offices setting up the network and connecting the BOVPN. I am running into problems getting everything synced up. Here are the key players:

AT&T DSL Service with 5 Static IPs
WatchGuard XTM 22 router/firewall

Here are the logistics:

AT&T DSL was installed with a Motorola Netopia 3347-02 Modem/Router

My IP Block is as follows:
Public IP 99.x.x.169 to 99.x.x.173 (Usable)
Default Gateway is 99.x.x.174
Subnet Mask is 255.x.x.248

The modem was configured with a PPPoE of xxx@static.att.net


The WatchGuard XTM 22 is configured using a Static IP of 99.x.x.169/29 and Gateway of 99.x.x.174

Ok, so I have tried to set the Motorola Netopia to Bridge mode, basically disabling all of its settings, except for the modem portion. The WAN IP interface has been configured to use the PPPoE settings. From what I can see, the modem tells me it is bridge mode.

When I have the Watchguard box external interface to the 99.x.x.169, my network has no internet access. If I set the external interface to PPPoE using the supplid info, and using either "obtain IP" or setting the IP to the 99.x.x.169, my network has internet access, but my XTM 22 reads it's IP as 99.x.x.174 and has a completely different subnet mask and default gateway.

I also cannot ping the 99.x.x.169 or 99.x.x.174 or any of my other Static IPs. However, when I have the XTM set to use the PPPoE settings, and I set a laptop to the 99.x.x.169 credentials, I have internet access, and I can ping that IP from the outsite, however, I am at that point connecting to the modem, and not my XTM.

I have made 5 calls into AT&T, ranging from Home Tier 1 to Business Tier 1, and all they canm say is that their equipment is working. I am at a loss, I am asking for anyone who has experience dealing with AT&T DSL for thier business network to help me out on this. I have gone through all the settings pages for the modem, and it just won't work the way it should.

So if anyone out there can give me some pointers on where to look on this particular modem, or has dealt with this mess before and knows what needs to be done, you'll be a life saver!! If you need more info, please don't hesitate to ask!!!

Thanks Experts!
Avatar of Kendzast
Kendzast
Flag of Slovakia image

If I understood it right you want to bridge your public IP address range from AT&T DSL to WatchGuard?
Leave the Netopia "unbridged"
Its LAN port should have the 99.x.x.174 IP address.

This leaves the rest of the IPs (169-173) available for you to use.
Your WatchGuard gets 99.x.x.169 on its WAN (or all 5 IPs if it's capable of multiple WAN IP addresses)
Avatar of joelisthedude
joelisthedude

ASKER

Kendzast, Yes. Kdearing, I will try that to see if that works.
Ok, so I did that, and the internet is accessible by the network. And WatchGuard is registering its IP address is the 99.x.x.169, the problem is, I can't ping 99.x.x.169 from the outside, but 99.x.x.174 is. Question is, can I use the 99.x.x.174 address for the BOVPN and HTTP, or is this setup still not configured right? I thought that 99.x.x.169 would be accessible once the modem and WatchGuard were talking correctly, but it still isn't working the way I thought.
Well I can't connect to my XTM 22 using the 99.x.x.174 address, so that address, while it can be pinged, is useless to me.
99.x.x.169 is your correct public IP
The WAN interface of your WatchGuard box is set to ingore pings by default.
I have policies in place already to accept pings.
Are there any other settings you can think of in the modem that could still be interfering?
I can enable remote access if you want to log in and peek around, because I am running out of ideas and time, my flight leaves in 6 hours lol
OK
Let's make sure we have everything straight.

The netopia is not bridged and not in any type of "gateway" mode.
Its WAN side IP address is some ATT address
Its LAN side IP address is 99.x.x.174 /248

Your WatchGuard WAN side IP address is 99.x.x.169 /248
WatchGaurd default gateway is 99.x.x.174
WatchGaurd accepts pings

From the outside world you can ping 99.x.x.174 but not 99.x.x.169  ?
Netopia is not bridged, the settings are still from the pre-configuration from AT&T.

The WAN side IP is also 99.x.x.174, along with a Peer Address of 67.36.167.167

All WatchGuard settings are correct.

I can ping 99.x.x.174 but not 99.x.x.169
ASKER CERTIFIED SOLUTION
Avatar of kdearing
kdearing
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
The 99.x.x.174 is on both sides, LAN and WAN.
sorry for the delay
I still think yo need to get a hold of ATT
that config doesn't sound right
Called AT&T, they ended up sending out a new router that I will setup and hopefully it will work!