On Friday 17 January 2003 11:39 am, Adam Thornton wrote: > On Fri, Jan 17, 2003 at 08:36:15AM -0500, Peter J. Farley III wrote: > > My base RH system is behind a router, and the router is connected to a > > cable modem. The base RH system sports an internet address of > > 192.168.1.100, DHCP'd by the router. What more do I need to specify in > > the Debian/390 image? > > Uh, maybe you mean NATted by the router?
Probably. I must admit to very newbie-hood when it comes to networking, apologies if I mis-state things when using terms I only half-understand. I said DHCP because that's how my systems get their address when they boot. > In any event, 192.168/16 is an RFC 1918 local address, and therefore is > *not* what the outside world sees connecting to it when you hit a site. No, it isn't. My "outside" address (which only the router knows) *is* DHCP from my ISP's server. > > 0A00 3088 CTCI /dev/net/tun 2000 192.168.10.2 192.168.10.1 > > 255.255.255.252 > > 0A01 3088 CTCI /dev/net/tun 2000 192.168.10.2 192.168.10.1 > > 255.255.255.252 > > Your router probably doesn't know how to reach 192.168.10.1 and 10.2; > you need to do the moral equivalent of > > route add -host 192.168.10.1 gw 192.168.1.100 > route add -host 192.168.10.2 gw 192.168.1.100 > > on the router. But since you are getting the initial install fine, > maybe this isn't the problem.... Would this be on my base RH system? Or do you mean somehow adding addresses to the router itself? How does one go about doing *that*? > > /etc/resolv.conf: > > > > nameserver aaa.bbb.ccc.eee.fff > > nameserver aaa.bbb.ccc.eee.ggg > > nameserver aaa.bbb.ccc.eee.hhh > > search ISP.net > > I assume these are really filled in with actual addresses. Of course. Addresses and names munged to protect my privacy. > > > > 0% [Connecting to 192.168.0.1 (198.168.0.1)] > > > > Err http://security.debian.org stable/updates/main Packages > > > > Could not connect to 192.168.0.1:3128 (192.168.0.1), connection > > > > timed out ... > > > > > > Looks like the connection swapped out protocols on you. > > > > And that means...? A bug in the Debian configuration scripts? Is there > > something I can do about it? > > Looks to me like the lookup for security.debian.org failed! Unless your > router is doing some sort of bizarre proxying? You should be hitting > 194.109.137.218 port 80, not 192.168.0.1:3128. You might try > configuring the IP address in /etc/apt/sources.list and see if that > helps any. > > What sort of router *is* this? Linksys BEFW11S4 wireless access point with built-in router with four wired ports. I run the house laptops and one other desktop over the net through it. My base system is wired directly to the router (cat5). WAN side is connected to a cable modem. > > No, I don't think so. Those errors were for additional apt sites to > > check for security updates. The basic ftp sources (I used > > ftp.us.debian.org) were used to retrieve the deb packages without a > > hitch, as far as I could tell. > > Weird. It's as if "ftp" names resolve OK, but http does not. Can't figure this one out myself, that's why I'm asking for help here. Any further assistance you can provide is appreciated. Peter
