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.
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 ...
however, in the course of action, I have also managed to annoy iptables. /var/log/prcsys now says:
Applying iptables firewall rules:
iptables-restore v1.3.7: Problem when communicating with ipset, errno=92.
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.
And guess how I made my system first load the net connection, and only then those 2 daemons http and ddclient ?
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.