I guess we need to start at the beginning, because it appears that your network card drivers are not properly installed. Did your network ever work? i.e., during installation? Debain sometimes properly configures the network during installation, and then forgets how to use the network after you are done installing. You need to make sure the proper kernel modules are loaded for your network card. (btw, which kernel are you using?) If you are using a 2.4 kernel, try running "mofconf" as root and see if you can load the network card driver. Jonathan

0

What happens when you run "ifconfig" without sepcifying an interface - does it list a block for eth0? or is it just things like lo, ppp0 and such? Jonathan

0

Hi Jonathan, Thanks for your advice. There is no problem on NIC. I have a mobile hard drive on this box running RH9. It works perfectly. # ifconfig eth0 Link encap:Ethernet HWaddr 00:50:BF:70:F6:DD inet addr:192.168.2.3 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:804 errors:0 dropped:0 overruns:0 frame:0 TX packets:535 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:114717 (112.0 KiB) TX bytes:96191 (93.9 KiB) Interrupt:5 Base address:0xec00 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:3924 Metric:1 RX packets:36068 errors:0 dropped:0 overruns:0 frame:0 TX packets:36068 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12467899 (11.8 MiB) TX bytes:12467899 (11.8 MiB) ppp0 Link encap:Point-to-Point Protocol inet addr:202.123.68.108 P-t-P:202.123.71.254 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:347 errors:0 dropped:0 overruns:0 frame:0 TX packets:158 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 RX bytes:24167 (23.6 KiB) TX bytes:3972 (3.8 KiB) sl0 Link encap:Serial Line IP inet addr:192.168.0.1 P-t-P:192.168.0.2 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:10 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Kernel = 2.2 If I could not find a solution I am prepared to make another clean installation of Debian 3.0 This time I will use net-installation. My box is connecting to 3MB broadband. It won't take long time to download. Unless the installation will start from compiling source code, like Gentoo 1.4. then it will take prolonged time to install from Debian website B.R. satimis

0

Sorry it took me so long to get back to you. It looks to me like your ethernet connection is working from your ifconfig output. It has been assigned an ip address (probably via dhcp). It looks like your problem is in the routing or firewall setup. What happens when you run "iptables -L"? Jonathan

0

Hi Jonathan, I have not setup firewall yet. iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination This Debian box is connected to broadband via ADSL modem, with dynamic IP. The PC is for testing purpose with 2 NICs and has 2 mobile drives, running XP and RH8.0 respectinve. Connection to Internet has no problem. Before installing Debian 3.0 I already removed one NIC-eth1. I can't understandy it is always searching for eth1 B.R. satimie

0

This is getting weird.... from your log, I see that eth0- really is being properly initialized (I went over it line by line and extracted the relevant bits): Dec 15 03:17:44 debian dhclient-2.2.x: DHCPREQUEST on eth0 to 192.168.2.1 port 67 Dec 15 03:17:44 debian dhclient-2.2.x: DHCPACK from 192.168.2.1 Dec 15 03:17:44 debian dhclient-2.2.x: bound to 192.168.2.3 -- renewal in 15 seconds. and then later: Dec 15 03:30:24 debian pppd[223]: not replacing existing default route to eth0 [192.168.2.1] Dec 15 03:30:24 debian pppd[223]: Cannot determine ethernet address for proxy ARP Dec 15 03:30:24 debian pppd[223]: local IP address 202.123.68.247 Dec 15 03:30:24 debian pppd[223]: remote IP address 202.123.71.254 Dec 15 03:30:24 debian pppd[223]: primary DNS address 202.123.77.197 Dec 15 03:30:24 debian pppd[223]: secondary DNS address 202.123.77.213 Dec 15 03:30:50 debian dhclient-2.2.x: DHCPREQUEST on eth0 to 192.168.2.1 port 67 Dec 15 03:30:50 debian dhclient-2.2.x: DHCPACK from 192.168.2.1 Dec 15 03:30:50 debian dhclient-2.2.x: bound to 192.168.2.3 -- renewal in 15 seconds. Dec 15 03:31:05 debian dhclient-2.2.x: DHCPREQUEST on eth0 to 192.168.2.1 port 67 Dec 15 03:31:05 debian dhclient-2.2.x: DHCPACK from 192.168.2.1 Dec 15 03:31:05 debian dhclient-2.2.x: bound to 192.168.2.3 -- renewal in 15 seconds. Dec 15 03:31:20 debian dhclient-2.2.x: DHCPREQUEST on eth0 to 192.168.2.1 port 67 Dec 15 03:31:20 debian dhclient-2.2.x: DHCPACK from 192.168.2.1 I see a couple of disturbing things in this setup..... first, your dchp renewal time is 15 seconds - this is bad. Renewal should be much longer - I think I have mine set for one week. The problem with a short time period like 15 seconds is that the DCHP client will try to obtain a new ip address every 15 seconds - meaning it will be continually requesting new ip addresses - rendering your network connection almost unusable. Also, it appears as though your computer is trying to establish a ppp connection - this must be your DSL commection. Is eth0 connected to your DSL modem, or your internal network? Jonathan

0

Hi Jonathan, >>>>> I see a couple of disturbing things in this setup..... first, your dchp renewal time is 15 seconds - this is bad. Renewal should be much longer - I think I have mine set for one week. The problem with a short time period like 15 seconds is that the DCHP client will try to obtain a new ip address every 15 seconds - meaning it will be continually requesting new ip addresses - rendering your network connection almost unusable. Also, it appears as though your computer is trying to establish a ppp connection - this must be your DSL commection. Is eth0 connected to your DSL modem, or your internal network? <<<<< 1) eth0 is connected to ADSL-modem, from there to broadband. 2) I can't control the renewal time which is operated by ISP. But other Linux distro work without problem 2) This Debian box has been connected to Internet once (ONLY ONCE) after adding "usepeerdns" to /etc/ppp/peer/provider. I reconfirmed this addition having effect by deleting it. Then re-added "usepeerdns" to /etc/ppp/peer/provider but it never worked again, cut-off from Internet, ISP connected. B.R. satimis

0

That is odd then. eth0 is being assigned an ip address for your local subnet.... i.e., like 192.168.2.3, while pppd is finding the (presumably crrect) ip address from your isp (202.123.68.247), but not assigning it to eth0. Also, I believe you can tell dhclient how often to request renewal of the dynamic IP - that is what I was saying about the 15 second renewal time. Jonathan

0

Hi Jonathan, I discover a solution; # route del default gw 192.168.2.1 # route add default gw 202.123.71.254 (my ISP's IP) # ping -c 3 www.yahoo.com PING www.yahoo.akadns.net (216.109.118.73) 56(84) bytes of data. 64 bytes from p10.www.dcn.yahoo.com (216.109.118.73): icmp_seq=1 ttl=48 time=287 ms 64 bytes from p10.www.dcn.yahoo.com (216.109.118.73): icmp_seq=2 ttl=48 time=288 ms 64 bytes from p10.www.dcn.yahoo.com (216.109.118.73): icmp_seq=3 ttl=48 time=296 ms --- www.yahoo.akadns.net ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2025ms rtt min/avg/max/mdev = 287.260/290.723/296.223/3.981 ms It works now. Internet seems connected. But I have not figured out a solution how to config the OS instead of running # route del default gw 192.168.2.1 # route add default gw 202.123.71.254 each time. Have you had any idea? B.R. satimis

0

Put those commands in a shell script, and then put a copy of the script in /etc/network/if-up.d/ - that will execute those commands everytime your network is brought up (usually only on boot up, but can happen other times if you are upgrading network drivers, etc...) Jonathan

0

Hi Jonathan, Created a file named 'startscript' as follows; route del default gw 192.168.2.1 route add default gw 202.123.71.254 and save it /etc/network/if-up.d/startscript # pon dsl-provider # ping -c 3 www.yahoo.com ping: unknown host Can't connect Internet. Rebooted the PC and ping again. No improvement found. B.R. satimis

0

Make sure it is executable - i.e., "chmod +x startscript". Jonathan

0

Hi Jonathan, Yes, I did it twice 1) # chmod +x /etc/network/if-up.d/startscript 2) # cd /etc/network/if-up.d/ # chmod +x startscript Still cut-off from Internet. I have to perform following commands manually after connecting ISP # route del default gw xxx.xxx.xxx.xxx # route add default gw xxx.xxx.xxx.xxx then I can connect Internet Seasons Greetings and B.R. satimis

0

It must be that there is something else that is run on bootup *after* the network start scripts, that is required for your network to work. I'm not sure what it could be - I'm still kinda fuzzy myself on how those scripts are executed. You could try to add those lines to /etc/init.d/networking and see if that does the trick. Jonathan

0

Hi Jonathan, As advised, add those 2 lines to /etc/init.d/network. Rebooted PC. This time it worked. Lot of thanks for your advice and time spent. Merry X'Mas and B.R. satimis Furthermore I am still interested to find out why it always looks at the gw 192.168.2.1 if possible.

0

No idea why it looks to 192.168.2.1 - there is probably a line in some obscure config file somewhere for that :) Anyway, I'm glad it works and you're welcome. Jonathan

0