LinuxQuestions.org - [SOLVED] wired network help 13.37

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - wired network help 13.37 (https://www.linuxquestions.org/questions/slackware-14/wired-network-help-13-37-a-907593/)

wired network help 13.37

I've got a problem where my new router won't give my slack box an ip address!

Nothing else has changed, just the new router (netgear WNR1000v2). This is what I get from /etc/rc.d/rc.inet1 eth0_restart

Code:

Polling for DHCP server on interface eth0:

dhcpcd[1910]: version 5.2.11 starting

dhcpcd[1910]: eth0: broadcasting for a lease

dhcpcd[1910]: timed out

dhcpcd[1910]: allowing 8 seconds for IPv4LL timeout

dhcpcd[1910]: eth0: probing for an IPv4LL address

dhcpcd[1910]: eth0: checking for 169.254.119.16

dhcpcd[1910]: eth0: using IPv4LL address 169.254.119.16

dhcpcd[1910]: forked to background, child pid 1930

I tried increasing the dhcp timeout to 10 secs and then 30 secs, but it made no difference.

here's the eth0 part of my config file /etc/rc.d/rc.inet1.conf:

Code:

# Config information for eth0:

IPADDR[0]=""

NETMASK[0]=""

USE_DHCP[0]="yes"

DHCP_HOSTNAME[0]=""

DHCP_TIMEOUT[0]="10"

DHCP_IPADDR[0]=""



# Default gateway IP address:

GATEWAY=""

All other devices are happy with the new router - other PCs, phones, games consoles and annoyingly, the windows partition on the slack box is OK too.

I don't know where to even start!

I probably should mention that I have a wireless AP in-between the slack box and the router, set-up in client mode, like this http://www.tp-link.com/mx/support/showfaq.asp?id=177

That's not a new thing though, I had that in place with the old router.

I don't have an actual solution, but I would suggest some troubleshooting steps:

1. Connect your computer directly to the Netgear router with a cable - make sure that works.
2. If the above works, try to connect via wireless to the netgear router and make sure that works.
3. If the above works, log into the TP-link AP and make sure that is still connected correctly to the Netgear router.
4. If the above works, try connecting another computer via cable to the TP-link AP and see if it works.

From your info, I would say the most likely culprit is the TP-Link AP. If you changed your Netgear router, there is a good chance the TP-Link is not connecting to it anymore.

Thanks for the suggestions.

One of the first things I had to do was log-in to the TP-LINK and connect it to the new router. It's definitely working because, as I said, the windows partition on the slack box is fine and that's using the wire from the TP-LINK. I've also had a games console working fine from the TP-LINK wire.

I tried 1. and it connects wired straight into the router, unfortunately that's not a practical solution.
Think I'll have to get a wireless card or dongle and try 2., but I've already had to replace the router so I'm not keen to shell out more cash to replace the TP-LINK which is working fine. I'll just have to use the windows partition a lot more. Or maybe I'll ditch the whole thing, it's pretty old now and I don't use it much anyway.

Just a long shot - but have a look at /etc/udev/rules.d folder - at the persistent-net file. I'm wondering if, for some reason, your real network card has somehow ended up somewhere else but eth0.

Also, try:

Code:

#ifconfig eth1 up

#ifconfig eth2 up

to see if any of them exist. Any chance you have more then one ethernet card in that system?

Of course, you can also do a:

Code:

#dmesg | grep eth*

to see what's happening during the boot, or even:

Code:

#dmesg | grep your_ethernet_kernel_module*

to see what was happening when the ethernet card was detected during boot.

Also, make sure there is no firewall active to start with. I suppose a misconfigured firewall could stop all traffic on eth0.

Like I said, a long shot (well, several long shots :-) ).

Sebastian

It's definitely eth0. I did try it with the firewall off, made no difference. I decided to give it one more chance and ordered a wireless dongle...

Thanks for the ideas anyway.

Does it work when you assign a static ip?

Quote:

Originally Posted by mrclisdue (Post 4500489)

Does it work when you assign a static ip?

Nope.

Hey it's working! I deleted the udev persistent-net file, turned off the firewall, ran netconfig and assigned a static ip address, restarted eth0 and it came up working.

Thanks for the helpful suggestions.

Edit: it didn't work for long. Next reboot it was out again and refused to come back. I gave up and am now online with a ralink wireless usb instead!