Help! RedHat 7.3 Networking with DHCP

[eboladeath]

Hi!!!

I´m having bad times trying to get my RH 73 box conneted to the internet using dhcp.
I have dual booting (W98 and RH 73) and W98 works fine.

I hope this data help you find the problem.

- Bios PnP capabilities are turned off.

- eth0 (nic conneted to cable modem) is 3Com EtherLink XL TPO 10Mb Ethernet (3C900B TPO)
- Cable modem is 3Com Home Connect Cable Modem 3CR29220 (Shark wing type)

- I have two nics and their modules seems to be right

# lsmod
Module Size Used by Not tainted
via-rhine 14468 1
3c59x 28520 1

etc# cat modules.conf
alias eth0 3c59x
alias eth1 via-rhine

- This is the routing info (IPs as seen on W98 conf)

# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo

/etc# cat resolv.conf
search supercabletv.net.co
nameserver 200.47.216.19
nameserver 200.47.216.10
nameserver 200.47.216.3

- Configuration bor both nics. As im having trouble conneting, i had assign eth0 to a static
address, si i can try dhcpcd or pump later

/etc/sysconfig/network-scripts# cat ifcfg-eth0
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
USERCTL='no'
BOOTPROTO='none'
DEVICE='eth0'
HWADDR='00:01:02:3c:19:4d'
TYPE='Ethernet'
ONBOOT='yes'
NETWORK='192.168.0.0'
BROADCAST='192.168.0.255'
IPADDR='192.168.0.3'
NETMASK='255.255.255.0'

/etc/sysconfig/network-scripts# cat ifcfg-eth1
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
USERCTL='yes'
NETMASK='255.255.255.0'
BOOTPROTO='none'
HWADDR='00:07:95:0c:ae:a6'
DEVICE='eth1'
IPADDR='192.168.0.1'
TYPE='Ethernet'
ONBOOT='yes'
NETWORK='192.168.0.0'
BROADCAST='192.168.0.255'

# ifconfig
eth0 Link encap:Ethernet HWaddr 00:01:02:3C:19:4D
inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:120 errors:0 dropped:0 overruns:0 carrier:26
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:36880 (36.0 Kb)
Interrupt:5 Base address:0xec00

eth1 Link encap:Ethernet HWaddr 00:07:95:0C:AE:A6
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:2510 (2.4 Kb) TX bytes:168 (168.0 b)
Interrupt:5 Base address:0xd800

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:284 errors:0 dropped:0 overruns:0 frame:0
TX packets:284 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:171463 (167.4 Kb) TX bytes:171463 (167.4 Kb)

- dhcpcd version running on my box

# dhcpcd --help
DHCP Client Daemon v.1.3.22-pl3

- tryin to connect

# dhcpcd -r eth0

- this lecture is from tcpdump while the dhcp traffic is broadcasted. I can see cable modem activity, but
i can´t get conneted

# tcpdump -i eth0
tcpdump: listening on eth0
20:24:04.128245 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x34661171 secs:10 C:192.168.0.3 [|bootp]
20:24:04.147257 arp who-has 200.47.216.19 tell 192.168.0.3
20:24:05.138639 arp who-has 200.47.216.19 tell 192.168.0.3
20:24:06.138641 arp who-has 200.47.216.19 tell 192.168.0.3
20:24:08.248670 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x34661171 secs:10 C:192.168.0.3 [|bootp]
20:24:09.148757 arp who-has 200.47.216.10 tell 192.168.0.3
tcpdump: pcap_loop: recvfrom: Network is down

- another try

# dhcpcd -r eth0

# tcpdump -i eth0
tcpdump: WARNING: eth0: no IPv4 address assigned
tcpdump: listening on eth0
20:29:42.513865 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x731ab741 secs:10 [|bootp]
20:29:46.628672 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x731ab741 secs:10 [|bootp]
20:29:54.758669 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x731ab741 secs:10 [|bootp]
20:30:10.828670 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x731ab741 secs:10 [|bootp]
tcpdump: pcap_loop: recvfrom: Network is down

- this is dhcpcd´s syslog info

/var/log# cat dhcpcd.log
Jan 3 20:25:04 micro981 dhcpcd[1841]: timed out waiting for a valid DHCP server response
Jan 3 20:30:42 micro981 dhcpcd[1903]: timed out waiting for a valid DHCP server response

- ... and now my eth0 has disappear :(....


# ifconfig
eth1 Link encap:Ethernet HWaddr 00:07:95:0C:AE:A6
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:251 (251.0 b) TX bytes:168 (168.0 b)
Interrupt:5 Base address:0xd800

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2090 (2.0 Kb) TX bytes:2090 (2.0 Kb)

- there is no iptables or ipchais rules on the firewall. Actually, only iptables works on
this kernel!!!

If you need more info just ask for it...

Thanks in advanced

[saithan]

redhat_config_network

in the dialog there is a place that asks for the primary and secondary name servers of your ISP.
(you can get those from your windows machine )

make sure that Linux knows where to get dhcp from by entering those addresses where they go.

unless your isp uses pppoe connection.

[Magueta]

I find it odd that you're trying to use the DHCP client but your interfaces are statically configured. All that information is great but I'm still a little unclear on where the problem is and what it is you want to do. What I do understand is that you want to have DHCP configure your system when you bring the interface up and you're having problems when you startup the DHCP client daemon. I see that the hardware works ok because when you run Windows your network access is fine. However, I must ask if you have regular network and internet access with your interfaces configured the way you have them now. If yes we can look at the next level which would be something with the DHCPCD itself. I would say that if you get to this point you should clear your ifcfg-eth0 (copy it to ifcfg-eth0.old) and have only three lines, one is "bootproto = dhcp" , the next is "onboot = yes" and "device = eth0". I think that's all you need for DHCP. I think you should make sure that the DHCP server is up and restart your interfaces using the network script /etc/init.d/network restart. Let us know if you still get errors after that.

Joe

P.S. Saithan, the secondary nameserver is in the resolv.conf file in the original post

[eboladeath]

First of all, thanks for answer my request. I,m sorry about not to be able to answer your suggestions as soon as I wanted, but I was kinda busy at work.

DNS server are set ok in the resov.conf file. Anyway, i had checked again on the redhat_config_network utility and they are set alright. I dont think that is the problem.

I had set the NICs statically just to show, step by step, the output from running dhcpcd command. Actually eth0 (NIC connected to the cable modem) is right now setted as your suggestion (bootproto = dhcp, onboot = yes, device = eth0) without any positive result. The NIC cant get connected on boot time and Operation Failed message is display.

I have regular internet access on w98, and the DHCP is supposed tu be running on a 100% time basis. The proof is that as soon as I boot form w98 I actually get connected to the internet.

Thanks again

[eboladeath]

I almost forgot....

I had test yopur suggestion without any result. Here are the files and the outputs

/etc/sysconfig/network-scripts# cat ifcfg-eth0
BOOTPROTO=dhcp
ONBOOT=yes
DEVICE=eth0

I had turned off/on the cable modem and then i decided to reset it. after this i launch

# /etc/init.d/network restart
Shutting down interface eth1: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: Determining IP information for eth0...Operation failed.
failed.
[FAILED]
Bringing up interface eth1: [ OK ]

...getting the same results

heres the tcpdump output

# tcpdump -i eth0
tcpdump: WARNING: eth0: no IPv4 address assigned
tcpdump: listening on eth0
20:55:26.033477 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x3b6e2638 secs:10 [|bootp]
20:55:30.156897 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x3b6e2638 secs:10 [|bootp]
20:55:38.306896 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x3b6e2638 secs:10 [|bootp]
20:55:54.506897 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0x3b6e2638 secs:10 [|bootp]
tcpdump: pcap_loop: recvfrom: Network is down

...and dhcpcd log from syslog

# cat /var/log/dhcpcd.log
Jan 29 12:42:13 micro981 dhcpcd[612]: timed out waiting for a valid DHCP server response
Mar 27 19:40:01 micro981 dhcpcd[612]: timed out waiting for a valid DHCP server response
Mar 27 19:53:08 micro981 dhcpcd[612]: timed out waiting for a valid DHCP server response
Mar 27 20:02:57 micro981 dhcpcd[1936]: timed out waiting for a valid DHCP server response
Mar 27 20:31:40 micro981 dhcpcd[612]: timed out waiting for a valid DHCP server response
Mar 27 20:43:40 micro981 dhcpcd[622]: timed out waiting for a valid DHCP server response
Mar 27 20:56:26 micro981 dhcpcd[1940]: timed out waiting for a valid DHCP server response

again thanks in advance

Edgar

[saithan]

open the terminal and type:
setup

reset the firewall to allow dhcp

that could be blocking.

just a possability.

[Magueta]

I don't know enough to go any further, however, I'll tell you what stands out in my ignorance. I don't know why I see messages with bootpc and bootp in them because bootp apparently is different from dhcp, so perhaps there's something there. I know that you think there aren't any ipchains rules but, I might suggest that you make sure that there aren't any ipchains rules by either using ipchains -L to see them and/or ipchains -F to flush them because it seems very like something that a firewall would do. Now that we know that your ethernet card is correctly configured, what's left? All I can do is guess and you can check them if you want. I suppose it might be a problem if what you think is eth0 is actually eth1. If you did that then eth0 wouldn't be able to see the dhcp server right? Because eth0 is supposed to be on the internet side not on the internal network side. One way to check is to setup eth1 to use dhcp and restart, if it has problems as well then there goes that theory. I can't tell if the module in the kernel is correct so you might want to double check that if you're not sure. If you're using older software you might want to try upgrading but I don't think that would be the problem here but, you never know. I can't think of anything else right now.

Joe

[eboladeath]

Hi again

I had test your suggestion without anu luck. There is no rules on any of the three standard chains form iptables......, so it can't be a firewall misconfiguration.

But i had found something new.... if i switch the wires (and with this i mean: wired eth0 to my local network and eth1 to the cablemodem) the problems keeps ocurring.

I really doní know what is happening or waht its wrong. I just want to use my linux box as the only os....

any other suggestion.....

thanks again

EdgarP

[Magueta]

Here's a longshot, install RH 8, or 9 when it comes out and see if that's any easier to setup.

Joe

[baldguy]

Who is your ISP? Some ISPs will give you windows software to connect and when the dhcp request is sent, the software will send info (such as host name) to configure your connection. You might want to check this (http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/html_single/Cable-Modem.html) out. Don't know if that will help or not

I have had other problems that I can't explain, but can get around. My cable modem works fine in windows and linux. Then I started timing out on DNS lookups in linux, but not windows. This happened completely out of the blue, and I ended up on the phone with tier one help desk ... And finding out that by letting the dhcp server assign my machine a name and domain (which is not a valid internet name either) all problems go away.

[eboladeath]

Hi:

My ISP is SuperCable, (Bogotá, Colombia) http://www.supercabletv.net.co/, but i used to had CableNet (also Bogotá, Colombia and listed in the document you attached) and experienced the same problems.

As far as i know, there is no special softwre running on windows in order to be able to connect to my ISP, as i had reinstall w98 several times and haven´t experienced trouble with the connection.

Thanks

Edgar