LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)
-   -   DHCP client issue (https://www.linuxquestions.org/questions/linux-software-2/dhcp-client-issue-930612/)

nsit_poison 02-21-2012 10:31 PM

DHCP client issue
 
'm working on 2.6.15 kernel running on a cisco IPTV. When the box is coming up, the DHCP client hangs up. The reason for this is that the DHCP client does not get fetch the broadcasted DHCP offer message.

When I read /proc/net/dev file, it shows that ethernet device (eth0) has not received any packet. I then ran tcpdump on the box and it also shows that no packet is been received on the ethernet interface.

Then I ran wireshark on the test PC (on which DHCP server is running), it shows that a DHCP offer message is broadcasted by the DHCP server.

This DHCP client and server are working fine with other boxes so there are less chances that these programs have any issues. There must be an issue in the ethernet drivers.

I'm really confused. How should I proceed to this problem. Please help me.

mdlinuxwolf 02-22-2012 04:22 AM

Use the ifconfig command. Do man ifconfig in a terminal. KDE has several good graphical network tools too.

nsit_poison 02-22-2012 11:18 PM

I have used ifconfig command to give a static IP to the ethernet interface. Thena I created appropriate route so that I can ping to the box but still it is not pinging.

What else can I try ?

makbul 02-22-2012 11:33 PM

Is there any activation in TCP wrappers, or firewall issues,

mdlinuxwolf 02-23-2012 01:04 AM

hidden or not?
 
Quote:

Originally Posted by nsit_poison (Post 4609791)
I have used ifconfig command to give a static IP to the ethernet interface. Thena I created appropriate route so that I can ping to the box but still it is not pinging.

What else can I try ?

Make sure that the client broadcasts and answers pings and has no MAC filters on or any other security or SE-Linux issues. Once you connect, you can re-hide the client later. Check out cables NICs etc to make sure the hardware is good. Ditto for routers or switches.

nsit_poison 02-23-2012 11:21 PM

I have disabled all the security checks, firewalls and MAC filters. I have used cross cable to connect PC and box. The cross cable is ok.

But the good thing is that I'm able to resolve this issue. The problem was in the VLAN configuration of Marvell switch. I had the data sheet for 88E6061 but box have 88E6063. I have corrected it and it is working fine now.

But thanks for your help guys.

mdlinuxwolf 02-24-2012 03:25 AM

No problem. Vlans are "interesting". The devil is in the details. I figured it was some switch or router or something.


All times are GMT -5. The time now is 08:39 PM.