Seem to have an odd problem - whenever I reboot, it "appears" that rc.inet1 isn't executing. I can't get any internet access until I run "rc.inet1 restart" manually. The file itself is set as executable in /etc/rc.d. Anything particular log file I could look at for info? dmesg doesn't seem to indicate anything, nor do I see anything in /var/log/messages, although I DO see a log entry there after I do the restart...

Thanks,

What card have you got, are you using static IPs
or DHCP?



Cheers,
Tink

It's a 3Com 3c905c. I'm using static IP. Note that this didn't start (that I'm aware of) until after I upgraded from Slackware 10.1 to 10.2 (using the procedure outlined in "UPGRADE.TXT".) I'm still using rc.inet1 and rc.inet1.conf that I used with Slackware 10.1.

Thanks,

In that case check the invocation of rc.inet1 inside
of rc.M ... also make sure that both rc.inet1 and rc.inet1.conf
have been upgraded, and aren't just sitting in /etc/rc.d as
*.new ...


Cheers,
Tink

I just did the same thing yesterday with my second box (updating to 10.2). Initially, networking would not work on my box either. My scribble pad of notes shows an entry of "networking fails."

I think the problem was related to the update automatically enabling (chmod +x) rc.wireless and rc.hotplug. That seemed to cause problems for my box. Somewhat Microsoftish of PV to assume how my existing box should be reconfigured.

I don't think the old rc.inet1 and rc.inet2.conf files are the problem because I somehow got networking to initialize before I merged the existing rc.d scripts with the *.new scripts. For me I think the problem disappeared after I disabled (chmod -x) rc.wireless. I hope this helps.

Hmmm... I'll try disabling rc.wireless - I certainly don't need it for this machine...

Thanks for the tip

Sorry, but I don't believe it has anything to do with x file mode for rc.wireless.

I had the same problem after upgrading from 10.1 to 10.2. First, everything seemed ok, but then I thought it was easier to use netconfig to configure my network instead of merging the old configuration into the .new config file. In netconfig I accidentally selected the loopback configuration instead of the DHCP option. That was my mistake.

As it didn't help to run netconfig again and choosing DHCP I installed anew (because looking for the loopback network related error seemed to be time-consuming...).

So, maybe you have the same problem. It's about the loopback network and DHCP. Maybe someone can provide a few words of explanation, here. For me, a re-install was the solution.

BTW, I think the text describing the options in netconfig seems misleading or buggy. loopback is recommended for dial-up machines, but DHCP is what you actually need for a modem connection to your ISP. Loopback only makes sense for direct connections to other machines when you assign your own, non-global IP addresses to your network interfaces. If you are reading this, Pat, please provide a clearer textual description for netconfig options in Slack 11.0. Thank you!

gargamel

Maybe you're confused with the terminology ... if you're using
a modem (a serial, USB or built-in device that communicates with
your ISP over a 56KBit) connection you DON'T want DHCP at all,
all you need is loop-back.

You need DHCP if you have a router (ADSL-router, other routers)
that provides DHCP leases and hands out details about gateways
and name-servers.

If you have one of the above but chose NOT to use DHCP you'll
want static IPs for the networked machines.




Cheers,
Tink

PROBLEM RESOLVED

Boy, do I feel dumb now - it most certainly WASN'T anything to do with rc.wireless - turns out all I needed to do was to backup my 10.1 version of rc.inet1 and replace it with the 10.2 version (rc.inet1.new). On the next reboot all was well...

Sigh... it's usually the simplest things that cause the most headscratching.

Thanks, guys, for at least giving me some idea what to look for...

In other words: my 2nd post in your thread held the answer? :}


Cheers,
Tink

Yep. Had to re-read it before I figured out what you were trying to say (Too much left-over turkey this weekend, I guess...)