I've just done a full installation of Slackware 12.2 on a Dell Inspiron 6000 (which was running Slackware 12.1 just fine) and cannot get to my router; i.e., I cannot ping the gateway at address 192.168.1.1 (or, of course, anything else). Been scanning through all the blurbs and I don't find anything about not being able to use (or some special something you have to do to use) static IP addressing -- I traditionally use static addressing on my internal network).

Gotta be something I'm not seeing or missing somewhere -- like, is wireless trying to take over instead of hard wire?

Any advice more than welcome and thank you.

What does the route command say?

It should have a default route using the device that connects to your router, something like:

If not there you can add it manually as root:

and set it permanently by editing /etc/rc.d/rc.inet1.conf

(assuming your interfaces are up and configured).

Post the output of route and ifconfig if you can't get it going.

Hmm. Executing route takes about 30 seconds to display the "default" line in the output! "localnet" and "loopback" display immedately, "default" takes forever plus a week.

ifconfig, doing a line-by-line compare to another is... well, line-by-line the same.

Mumble grumble.

Dang if I know -- netconfig is set up exactly the way it always is (with address 192.168.1.20, netmask 255.255.255.0, gateway 192.168.1.1) and I haven't fiddled with anything else.

Thanks for the replay.

It takes a long time if the destination is not reachable... which is of course, your problem.

You might try manually cycling the device that the default route is on, like

Try setting your /etc/resolv.conf file to match your router IP/Gateway. That got me up and running with static.

A little digging in /var/log/messages: eth0 seems to be assigned to the damnfool wireless and eth1 assigned to Broadcom 44xx/47xx 10/100BaseT Ethernet (which is the hardwire Ethernet connection). Dammit!

OK, it's gotten a little past me here. I think it's something to do with this new(?) ESSID stuff and, so far, I've no clue what to to do assign eth0 where I want it instead of to a radio controller that I just flat don't use (or, if I was going to, it would be on eth1 so it doesn't interfere with eth0).

Is there some thing to comment out, turn off, whatever to get the services flipped?

Maybe try swapping the "Names" in /etc/udev/rules.d/70-persistent-net.rules

Hi,
If you don't want to use the wlan device then just goto your BIOS and disable the onboard device. When you reboot then the eth device should be recognized. You can always edit '/etc/rc.d/rc.inet1.conf' file. Then restart the inet with '/etc/rc.d/rc.inet1 restart' from the 'cli' as root.

Thank you for the suggestion. I edited the BIOS and disabled the wireless device and, well, I still can't access the network (...Destination Host Unreachable... when I ping -c 5 192.168.1.1). Sigh.

In /var/log/messages where eth0 is mentioned there are lines about iwconfig eth0 essid "any" -- never seen these before (they're not in my 12.1 systems). Near as I can figure, this has to do with iwconfig, so I scanned through all the stuff I could in /etc/rc.d and changed the mode of rc.wireless (executed from /etc/rc.d/rc.inet1 to 644 to see if that would fix it. It did not: eth1 is the NIC, eth0 is the wireless, there is no joy in Mudville (yeah, it's really muddy right now).

So, I dunno. Looks to me like and un-Slackware-like "do it for (to!) me" or I am missing something really, really simple here like maybe I'm not allowed to have a fixed IP address any more or something. S'pect I'm going back to 12.1 to get back in business.

Thanks again for all the advice.

Did you try what I suggested?

Hi,
You did run 'netconfig'? What does your '/etc/rc.d/rc.inet1.conf' contain?

What does the 'dmesg |grep i eth' from the cli show?

If you delete '/etc/udev/rules.d/70-persistent-net.rules' it will be regenerated at boot now that you have disabled the wireless device in the BIOS.

Wow, zowie: that worked (both NIC and transceiver are active)! Thank you.

Now, the question is why did it work; i.e., why does the installation default to the transceiver instead of the the NIC and what can be done to not have this happen on the other five systems I'll be updating. I cannot imagine that I'm the only guy on the plant that's using fixed IP addressing with a mixture of both NIC and transceiver on one or more machines (and I usually assume that I'm doing something incorrectly when things don't go as the should).

Enough whining -- thanks to all for the help.

The /etc/udev/rules.d/70-persistent-net.rules is created by a script.
The order that the devices are found and the modules are loaded on the first boot will determine the ordering of the ethX devices.

Hi,
Yes it is created by a script. If you are having naming issues sometimes you can delete that file and it will be regenerated when you select or de-select a device;

Ah, but there's the rub: the script that does the setup defaults to transceiver first, NIC second; the result of which is the problem I've experienced. That makes life difficult and that ain't the "Slackware Way" methinks. I kind of suspect that if I'd done netconfig with DHCP then manually edited /etc/rc.d/rc.inet1.conf to add the fixed IP addresses to eth1 that it might just have worked -- but how in blazes would I know to do that (or, for that matter, to manually edit /etc/udev/rules.d/70-persistent-net.rules)?

I may just try the DHCP-manual-edit thing after I get everything else done just to see but right now things work and that's good enough for the moment.

Again, I thank you for your help and advice and wish you a happy, healthy and prosperous new year.