[lug] Networking Question

jd lug at taproot.bz
Thu Jun 26 15:03:25 MDT 2003


looks like you might need aroute or some port forwarding on the
dlink because its doing nat?

jd



On Thu, 2003-06-26 at 13:50, Joseph McDonald wrote:
> Hi gang,
> 
> I have a question regarding my new home network setup and here's
> a pretty lengthy explanation:
> 
> Configuring an MSN Broadband (a-la Qwest) to work with a 4 port
> Linksys BEFSR41 and a D-link DI-614+ wireless router. Qwest told
> me that they would only support a single PC connected to their
> DSL router and I'd be responsible for configuring the network
> should I decide to add a DSL router. 
> 
> I have the following equipment connected and working: 
> 
> 1. Microsoft Broadband DSL 1000 Router
> 2. Linksys BEFSR41 4 port DSL router
> 3. Dell PC 
> 4. Dell PC 
> 5. Sun Ultra Sparc II (Solaris 8)
> 6. D-link DI-614+ wireless router.
> 7. Dell Insperon 5000 Laptop
> 
> They network starts with the Microsoft 1000 DSL router. The
> external connection is DHCP assigned and the internal (gateway)
> address is always 192.168.1.1. The subnet mask is 255.255.255.252
> which means I only get one IP to use (so you can't plug in a hub
> and expect to be able to get more than one IP). I configured my
> Linksys to do DHCP off the MSN 1000, then the LAN was configured
> to use 10.0.0.0/24 (Linksys internal static address of 10.0.0.1).
> 
> This worked, but for the next 3 or 4 days, every 20 or 30 minutes, 
> I'd drop packets for about 30 - 60 seconds. So, I decided to assign 
> the Linksys an external static IP of 192.168.1.2, which cleared up 
> that problem. I guess it was trying to get a new DHCP lease from 
> the MSN 1000 every 20 or 30 min.
> 
> I connected 3 PC's to the Linksys and gave them all static
> addresses in 10.0.0.x with a gateway of 10.0.0.1 and subnet mask
> of 255.255.255.0. All worked fine.. Then I ran some cat5 upstairs
> and plugged in the D-Link. I assigned the D-Link an external IP
> of 10.0.0.3 and have it's internal IP as 192.168.0.1. It's handing
> out DHCP addresses in that range (/24).
> 
> Now, all PC's can get to the internet although systems on the
> 10.0.0.0 network can't ping systems on the 192.168.0.0 network.
> I've added a static route to the Linksys as follows: 
> 
> 192.168.0.0		255.255.255.0	10.0.0.3	1	LAN 
> 
> but that doesn't seem to do the trick. Does anyone think they 
> know what the problem could be? Here's my network layout:
> 
> 						Internet 
> 							^
> 							|
> 							|
> 							|
> 							|
> 						65.103.x.x (DHCP)
> 					----------------------
> 					| 1 port MSN Router  | 
> 					----------------------
> 						192.168.1.1	(static)
> 							|
> 							|
> 							|
> 						192.168.1.2 (static)
> 					------------------
> 					| 4 port Linksys |
> 					------------------
> 						10.0.0.1 (static)
> 							|
> 							|
> 							|------Joey PC (Dell) 10.0.0.100 (static)
> 							|	\--->Network Printer
> 							|
> 							|------Diana PC (Dell) 10.0.0.102 (static)
> 							|
> 							|------Sparc (Solaris 8) 10.0.0.10 (static)
> 							|	\--->Network File Server (Samba 2.2)
> 							|
> 							|
> 						 ( HUB )
> 							|
> 							|
> 						10.0.0.3
> 					-------------------
> 					| D-Link Wireless |
> 					|   (upstairs)    |
> 					-------------------
> 						192.168.0.1
> 							o
> 							o
> 							o o o o Joey Laptop (Windows XP) 192.168.0.x (DHCP)
> 							o
> 							o
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug






More information about the LUG mailing list