Routing Setup

[Synthetic]

First off, the current setup is:

Full T1
Netopia R5300-T T1 Router
D-Link DI-713+ WAP & Router

Currently most of the clients are plugged into the 8 port hub on the Netopia, and there is another client who is hooked up on the uplinked D-Link router.

As of now all clients are using a static IP.

What I want to setup:

DHCP & NAT on the D-Link so that non-servers can be behind the router for security, and servers can continue to use their public static IPs.

The problem is, when I set it up, it just plain doesn't work. Configuration I setup on the D-Link:

LAN IP: 192.168.0.1
WAN Type: Static
WAN IP Address: (Available Static IP in our block)
WAN Subnet Mask: 255.255.255.224
WAN Gateway: (IP of our Netopia Router)
Primary DNS: (Speakeasy Primary DNS)
Secondary DNS: (Speakeasy Secondary DNS)
DHCP is enabled.

Ok, when I have a client (In this case the client is plugged physically into the Netopia router) renew an IP address that works fine, however, the only IPs they can ping are:

Their local IP
Both the WAN and LAN Ip of the D-Link router
And the 192.168.0.255 broadcast IP

So they can't ping other users on the network or internet. I know it is uplinked fine because the single user plugged into one of the ports on the D-Link has internet access through a static IP.

Any ideas why this doesn't work?

 

[bozo1]

LAN IP: 192.168.0.1

Is that valid? (The 0 part)

 

[Synthetic]

Originally posted by: bozo1

LAN IP: 192.168.0.1

Is that valid? (The 0 part)

What?

 

[gunrunnerjohn]

Yes, 192.168.0.1 is a perfectly legal IP address.

 

[Synthetic]

Originally posted by: gunrunnerjohn
Yes, 192.168.0.1 is a perfectly legal IP address.

Yep.....still don't know why this won't work.

 

[skyking]

If you have a block of wide area network static IPs, then the gateway is not the netopia router. It is xxx.xxx.xxx.1, with the x's replaced with the first sets of your public IP range.
The netopia is routing out those packets true enough, but if you currently use public IP's on your machines, the netopia is really not the gateway.
try using that method in your DLink router, and see what happens.
Edit: Your router is acting as a bridge, if you do not currently have a set of private IPs. That was the term I was looking for!

 

[Synthetic]

Originally posted by: skyking
If you have a block of wide area network static IPs, then the gateway is not the netopia router. It is xxx.xxx.xxx.1, with the x's replaced with the first sets of your public IP range.
The netopia is routing out those packets true enough, but if you currently use public IP's on your machines, the netopia is really not the gateway.
try using that method in your DLink router, and see what happens.

Yes, I have a 32 block of WAN static IPs.

And no... that is not my gateway.

The gateway my Netopia router uses, the router at speakeasy, is of a completely different IP block.

I tried what you said, but understandbly it doesn't work. That would be bypassing the whole point of having the T1 router.

The way I am configuring the D-Link is settings as if it was just another server, the gateway has to be our T1 router as that's our gateway to the router at speakeasy, which then goes to the internet. You can't bypass the Netopia router.

 

[mboy]

Is their a specific reason why you would need/pay for a block of 32 IP's and be using them for your LAN pc's?
If you do not have at the very least, the basic firewall built into the 5300 ( I have a 5300 t1 router also), then your PC's are MIGHTY insecure.
In the Dlink settings, the WAN IP of the DLink should be the actual IP of the Netopia router (same as the Dlink's gateway setting), your other settings should be correct (for LAN subnet etc).-Note only the pc's plugged into the dlink, or a switch behind the dlink will ( or should) receive a DHCP addy.
That is a peculiar setup you have, are you hosting 25+ public servers?

I have about 60+ Lan Pc's 10 servers (only run puiblic services on a couple)-have a block of 6 public IP's and my WAN Ip for the netopia itself.

I run my Netopia in Nat/PAT mode, set up the port forwardings via PAT in the easy servers, then have the netopia into a hub--into a bridged SonicWall pro 200 FW--into 8port hub--split to LAN switches(then to LAN pc's, servers,etc), a snort box and an inernet monitoring box.-Upcoming exchange server going into the DMZ on the sonicwall.

If you aren't hosting 32 public servers, then their is NO way you should be wanting a setup like that, especially if you are paying a fee for each public IP addy.

Let me know how it goes when u change the Dlink's wan ip to the IP of the netopia. That should clear it up for u!

 

[Synthetic]

Originally posted by: mboy
Is their a specific reason why you would need/pay for a block of 32 IP's and be using them for your LAN pc's?
If you do not have at the very least, the basic firewall built into the 5300 ( I have a 5300 t1 router also), then your PC's are MIGHTY insecure.
In the Dlink settings, the WAN IP of the DLink should be the actual IP of the Netopia router (same as the Dlink's gateway setting), your other settings should be correct (for LAN subnet etc).-Note only the pc's plugged into the dlink, or a switch behind the dlink will ( or should) receive a DHCP addy.
That is a peculiar setup you have, are you hosting 25+ public servers?

I have about 60+ Lan Pc's 10 servers (only run puiblic services on a couple)-have a block of 6 public IP's and my WAN Ip for the netopia itself.

I run my Netopia in Nat/PAT mode, set up the port forwardings via PAT in the easy servers, then have the netopia into a hub--into a bridged SonicWall pro 200 FW--into 8port hub--split to LAN switches(then to LAN pc's, servers,etc), a snort box and an inernet monitoring box.-Upcoming exchange server going into the DMZ on the sonicwall.

If you aren't hosting 32 public servers, then their is NO way you should be wanting a setup like that, especially if you are paying a fee for each public IP addy.

Let me know how it goes when u change the Dlink's wan ip to the IP of the netopia. That should clear it up for u!

The 32 IP block is at no cost to us, only cost like a $15-30 one time fee. And yes we do have about 10 public servers.

No, setting the D-Link's WAN IP to the WAN IP of the netopia didn't work.

 

[jonmullen]

Just set one computer up outside of the dlink router like you normally would, when it gets online take alook at its working ip configuration. Start->Run (winipcfg for 9x or cmd->ipconfig /all for NT/2k/XP) or ifconfig in linux. Then copy down the working info ipaddress subnet default gateway and every thing then shut that computer down and plug those settings into your dlink router. You should then be good to go.

 

[Synthetic]

Problem solved in this thread:

http://www.dslreports.com/forum/remark,7768119~root=sharing~mode=flat#7780747