dealing with the runlevels
 

Hello all

Help me with this one:

----some details for prob #1----

I have recently installed apache server, as well as ddclient - a dynamic IP reporting tool. Good for hosting a webserver from a dynamic IP machine.
My connection is a PPPoE one, and for that I use an USB modem. Naturally, linux does not support this kind of crap ootb, so I managed some bridging between a virtual ethernet interface and the physical modem (which speaks ATM). I have found some tutorials over the web describing a method to automatically bring up that connection upon boot. Using a script. Called S96dial. ran from rc5.d.

----problem #1---

Thing is, I have been trying to convince my system to behave as follows: first bring up the internet, then start ddclient, and then httpd. I have managed to do just so, but ... :D however, in the course of action, I have also managed to annoy iptables. /var/log/prcsys now says:

I have inspected my iptables config, its all ok, and iptables runs ok (apparently, anyway). Is there something to worry about? Because those 2 lines definitely were not showing up at boot.

----problem #2----

And guess how I made my system first load the net connection, and only then those 2 daemons http and ddclient ?
:D

S51network and S52network-up scripts from runlevel 5 now have new names:
_S51network and _S52network-up. Yes, those 2 do not make it through anymore. So right now I have no support for my ethernet NICs, but I am not at all bothered. That is just fine if u ask me, but I wanted to ask some other persons too, just to be sure I aint doing anything dangerous to my configuration.

---details to prob# 2-----

Why I have chosen to do this - cause my S64dial (renamed it so it would start before the targeted daemons) script would just not get along with whatever those 2 'network' scripts did. Always got <<[Failed]>> lines complaining about ppp0 and nas0 interfaces (used for internet); then, when X loaded everything I could see my connection to the net (which was opening okay because of S64dial script) was now dead or corrupted (and nonfunctional). Sigh.


Thanks

You're giving a lot of irrelevant information and skipping very important parts. For example, what modem do you have? Linux will run with most (if not all) PPPoE modems via the ethernet cable and Linux will also run with quite a few modems which use a USB connection. For all we know, you could be doing things the hard way (and the wrong way).

hey,

believe me on this one. No other way to get online with a ST330 Thomson modem. Tried it very hard to make it work as close as possible to OOTB about an year ago. And failed. However, connectivity is not an issue. Just wanted to find out if I really broke iptables (#1) and anything else besides my ethernet NICs (#2). Anything else I need to stdinput ?

Thanks
kellogs

It is possible you are just doing some things in the wrong order. If you actually do alter the iptables rules it is also fairly easy to isolate your computer. Can you provide a link to the information you used to set up? It's impossible to guess what might have gone wrong if we don't even know what you did.

Ok . there goes:

- configuring the internet connection:
http://forum.mandriva.com/viewtopic....653472c20f3cd3
(last post on the thread). This left me with a S96dial script for runlevel 5. And worked ok.

-my rc5 folder looks now like this like this:
S64dial was renamed from S96dial

Basically that was it. Cant remember anything else besides attempting to rename S96dial -> Sxxdial for about 4-5 times, and commenting / uncommenting _S51network and _S52network-up scripts. Oh, and also added K44dial to runlevels 0,1,6. Does it matter is K44 and not K64 ?

Thanks for helping.

I suspect that shorewall complains because you don't have any interfaces configured at all. Your network connection script needs to run before shorewall so that shorewall can set up the rules correctly.

Since shorewall is S53 and your network setup scripts (which you disabled) are S51,S52, I suggest you set those older scripts to 50,51 and your dialup script should be S52; you will also have to move the resolvconf and syslog to S49. There should be no need to completely disable your network startup scripts as you have done. If you don't want to use a particular interface, just configure it so that it's not activated. So aside from changing the priority of those links, activate those network scripts again and tell us about the errors which come up.

The startup/shutdown priorities are usually different (after all, the shutdown will usually proceed in the opposite order). What is important is that dependent services are shut down in the correct order. For example, let's say you have "networking" and "ssh" - when they start, "networking" will be run first to set up your network interface, then "ssh" will be run to set up the ssh daemon (which will probably use the interface which you had just configured). When shutting down, "ssh" must be shut down first - if you shut down "networking" first then any current ssh sessions have their connections cut without any warning. Shutting down in the wrong order can cause more serious problems for some things.

What script do you use to start; the one referenced at http://www.linux-usb.org/SpeedTouch/mandrake/index.html ?

The only scripts I can see are not proper service startup/shutdown scripts; they only do one thing (start up) but they cannot stop or restart the service.

Done as you have said. Result:

My ppp connection was non-functional imediately after login. It acquired a valid IP address, but could not be used for browsing / chating (havent tried anything else). It needed a restart, and everything worked thereafter.



My bad. Now the script looks like this: