On Aug 10, 5:20 pm, Andrei Popescu <[EMAIL PROTECTED]> wrote: > On Sun,10.Aug.08, 12:48:48, 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. > > > I am building an internet server, so I need to reconfigure networking > > to use a static IP address. I edited /etc/network/interfaces, using > > the static IP address leased to me by my RCN (and the other network > > parameters RCN provided). > > [...] > > > iface eth0 inet static > > address 207.237.37.110 > > netmask 255.255.255.224 > > network 207.237.37.96 > > broadcast 207.237.37.127 > > gateway 207.237.37.97 > > [...] > > > Relevant observation: > > > With the network configured for DHCP, when I run ifconfig I get: > > > Inet addr: 192.168.2.3 > > Bcast: 192.168.2.255 > > Mask: 255.255.255.0 > > How is your computer *physically* connected to the internet?
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. > (BTW, you should read on private network addresses [1] ) Reading it now... > > > Full Disclosure > > > I am running Debian sarge, because that is the version that was used > > in the book I am following to learn how to build an internet server. > > I realize this raises security issues, but I am not building a > > production server, only a *training* server. > > > More to the point: Although sarge is no longer state-of-the-art, I > > assume it should still be possible to configure it as an internet > > server with a static IP address! > > As you've been told several times, sarge is not suited for the Big Bad > Internet. I think you can use etch instead, the differences won't be > that big and the release notes can help. For someone like yourself who already knows a lot about networking, I'm sure etch would be better. For someone like me who knows very little, to make progress at rate faster than glacial it helps to have a detailed guide. It seems lucky that anyone has written such a guide (Linux System Administration , O'Reilly, 2007) in the first place, and I suppose it was not profitable for O'Reilly to update it for etch. Once I've had the experience of building the server, I expect to tear it down and use the experience to build a state-of-the-art server. Given that this server is just a lab project (with no critical data), what's the worst that could happen? Thanks again, Andrei, for your insights. Best Regards, Vwaju NYC1 > > [1]http://en.wikipedia.org/wiki/Private_network > > Regards, > Andrei > -- > If you can't explain it simply, you don't understand it well enough. > (Albert Einstein) > > signature.asc > < 1KViewDownload -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
