On Thursday 16 January 2003 11:31 pm, Steven Adams wrote: <Snipped> > > In order to use the ftp method for download and configuration, I had to > > create a non-empty /etc/resolv.conf with my ISP's DNS servers specified. > > And did you use a local gateway that resides on a *nix machine? Possibly on > an appliance that supports NAT?
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? Here's the Debian/390 hercules.cnf, the /etc/resolv.conf and the /etc/sysconfig/ipchains from the base RH system: hercules.cnf: CPUSERIAL 002623 # CPU serial number CPUMODEL 3090 # CPU model number MAINSIZE 64 # Main storage size in megabytes XPNDSIZE 0 # Expanded storage size in megabytes OSTAILOR LINUX # OS tailoring ARCHMODE ESA/390 # Architecture mode S/370, ESA/390 or ESAME 0009 3215 #0300 3390 dasd/Debian-3.0r0.3390 0300 3390 dasd/Debian-3.0r1.3390 #0400 3088 CTCI /dev/net/tun 1500 192.168.10.1 192.168.10.2 255.255.255.0 #0401 3088 CTCI /dev/net/tun 1500 192.168.10.1 192.168.10.2 255.255.255.0 # Uncomment these for CTC networking # device MTU Hercules IP Host IP Netmask 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 /etc/resolv.conf: nameserver aaa.bbb.ccc.eee.fff nameserver aaa.bbb.ccc.eee.ggg nameserver aaa.bbb.ccc.eee.hhh search ISP.net /etc/sysconfig/ipchains: # Firewall configuration written by lokkit # Manual customization of this file is not recommended. # Note: ifup-post will punch the current nameservers through the # firewall; such entries will *not* be listed here. :input ACCEPT :forward ACCEPT :output ACCEPT -A input -s 0/0 -d 0/0 -i lo -j ACCEPT # -A input -p udp -s 0/0 -d 0/0 53 -i tun0 -j REJECT -A input -s 0/0 -d 0/0 -i tun0 -j ACCEPT -A input -p tcp -s 0/0 -d 0/0 0:1023 -y -j REJECT -A input -p tcp -s 0/0 -d 0/0 2049 -y -j REJECT -A input -p udp -s 0/0 -d 0/0 0:1023 -j REJECT -A input -p udp -s 0/0 -d 0/0 2049 -j REJECT -A input -p tcp -s 0/0 -d 0/0 6000:6009 -y -j REJECT -A input -p tcp -s 0/0 -d 0/0 7100 -y -j REJECT <Snipped> > > 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? <Snipped> > These look like the OS reporting that it failed to install certain deb > packages. I think the greater problem in the connection failing - solve it > and the rest will likely work. 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. Thanks for your help. Peter
