[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: can't configure networking for static IP address



Sorry… I'm a couple of days behind on the list, but it doesn't look like this was ever solved for the OP.

On 2008-Aug-10, at 7:32 PM, Vwaju wrote:

I have an RCN cable modem (probably proprietary and not DOCSIS
compliant) which connects to a Dell TrueMobile 2300 Wireless Broadband
Router. The wireless router broadcasts to a Dell Inspiron 8500 running
Windows.  In addition there are 2 computers connected through Ethernet
ports on the router. One of these is a Windows box, and the other is my
Debian system.

On 2008-Aug-10, at 3:48 PM, Vwaju wrote:

I installed Debian on my Dell Dimension 4100 and, with networking
configured for DHCP, I am able to connect to the Internet, ftp, http,
etc.


Based on the description in your most recent message, your Debian system is *not* connecting to the Internet when you use DHCP. Technically, it is connecting to the TrueMobile router. Everything in your house is on a private network, including the router. What makes the router special is that it is also on the Internet and it can pass certain traffic from one network to the other. Your publicly addressable IP, static or not, belongs to the router (or whatever happens to be connected to the cable modem).

If you want the Debian system to use that IP, it's going to have to be plugged directly into the cable modem. This introduces some security concerns that have already been discussed, so only you can decide if that's really what you want.

Since you're learning your way around, I think you should leave your Debian system on the private network for now. If there are particular services you'd like to access from the outside world, you can probably forward the appropriate ports to it using the router's config. (Again, this introduces additional risk, but not as much as putting the machine on the Internet directly.)

If you just want to learn about configuring Debian with a static IP, you should be able to do that. Just use an available IP on the private network (192.168.2.X). Preferably, choose an address that's outside the range the router uses for DHCP assignments.

---
Rob McBroom
<http://www.skurfer.com/>


Reply to: