Thanks for the suggestion. I tried chmodding the one inet file that didnt have executable all the way through but this made no difference.Then I found this http://www.slackware.com/config/network.php, and so I ran netconfig. All seemed to go well, but after reboot still no joy.Worse - now my manual fix no longer works so I have no Internet access from the VL PC at all Anyone got any ideas ?In /etc/rc.d I now have rc.inet1.conf, rc.inet1 and rc.inet2 (the last 2 have identical contents).

# Change this to "yes" for debugging output to stdout. Unfortunately,# /sbin/hotplug seems to disable stdout so you'll only see debugging output# when rc.inet1 is called directly.DEBUG_ETH_UP="yes"!comments removed

Did an AUTOSETUP from text mode and discovered that INETD hadn't been running, so I included that this time. Upon reboot, however, things look worse : ifconfig now only shows the loopback interface !Tried VASM again, but no result.

Tried "ifconfig eth0 <addr> netmask <mask>" and that worked - i.e. etho now shows up if I do "ifconfig".

The inet1 file now looks weird - it has the loopback address inserted for etho. So I manually edit that so that inet1 looks right & reboot. Now go into VASM and get it to "start" inet1. This gives me a VASM error"starting inet1 failed"..

A weird thing : I looked in my router arp cache, and it has 2 (old) entries for the Linux PC with different MAC addresses Ifconfig says my mac addr is "00 01 40 00 00 00" and this is one of the arp entries, but the other is "00 01 50 00 00 00".

Just tried "dhcpcd -d eth0" and that worked. Can ping router (which now sees the ...40... mac address).Thats a bit of progress anyway.

progress I found in /var/log/messages a message from ifplugd saying "link beat not detected". I think that explains why ifplugd is not running (it has terminated) and why it hasn't started the interface.

But where do I add this ? I looked in /etc/ifplugd and found a file called "ifplugd.conf.bak" but no "ifplugd.conf". So I created one by copying the bak file and renaming it, and then I edited it to include the "-F" argument. Upon reboot, however, no change : still the same "link beat not detected" message but no change in interface status.

When I do "cat /var/log/messages | grep etho" I see that today ifplugd thinks my mac address is 00:01:00:00:01:00 whereas yesterday it thought it was 00:01:40:00:00:00 ! This is probably a red-herring though, as (irrespective of which mac address is being assumed) I can still start the interface successfully manually.

I think you can use the -s flag to see the output of ifplugd instead of the syslog. Should be an arguments section in ifplugd.conf, something like

Quote

ARGS="-fwI -u0 -d10 -s"

If you issue /etc/rc.d/ifplugd start on the console you should be able to see the error message.If your mac adress is changing, you could check the udev rules for the interface. Do you have more than one nic card?

Logged

"There is a concept which corrupts and upsets all others. I refer not to Evil, whose limited realm is that of ethics; I refer to the infinite."Jorge Luis Borges, Avatars of the Tortoise. --Jumalauta!!

thanks. I edited "my" ifplugd.conf file to include "-F -s" , then I killed the existing ifplugd (weird - how come it was running when it wasn't last time I looked ?) and then I ran "/etc/rc.d/init.d/ifplugd start".All I got was "Starting Network Interface Plugging Daemon : eth0". When I then did "tail /var/log/messages" I saw the usual "link beat not detected".

Looks to me like ifplugd is *not* reading my ifplugd.conf file

I ought to be able to invoke the -F -s flags on the CL hadn't I ? I tried "/etc/rc.d/init.d/ifplugd start -F -s" and it came back with "Starting Network Interface Plugging Daemon : -F -s "...looks like it thinks the interface is called "-F -s" . Sure enough - message log shows it looking for those "interfaces"

Then I reboot, after which I see that ifplugd *is* running (so it didnt shut itself down, good). Looking in /var/log/messages, there is *nothing* from ifplugd...so maybe it did read my conf file this time..but , in that case, how come eth0 still has no IP address ?

I just tried disabling ifplugd as a boot option, hoping that the default behaviour would then be to auto-enable eth0 - but this just results in eth0 disappearing entirely from the "ifconfig" output (although I can still get eth0 working just by running "/etc/rc.d/rc.inet1 start" from the CL).