iptables & a dhcpd question
two genuine newbie questions :)
FYI: I'm running Slackware 8.1, (kernel = 2.4.18, iptables = 1.2.6a, dhcpd ISC v3.0pl1)
Q1. I've been tweaking my rc.firewall script a bit lately and am wondering if there is a way to have my new one take effect without rebooting?
Q2. Second, I'm still trying to get my dhcp server running, and am wondering what is the best way to stop the service and restart it. I've been killing the process, but there has to be a better way. In looking for the answer to this, I've seen postings saying to run, "dhcpd stop" but that doesn't seem to work with this one.
Thanks in advance for any help!
-Paul
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
I don't know if this is what you are asking but.
I've never worked with Slackware, but try this:
/etc/(PATH TO rc.firewall)/rc.firewall
and when they say dhcpd stop, you have to add the path to it in the front:
/etc/init.d/dhcpd stop (if /etc/init.d is the path)
I hope this works,
Rodolpho
Signature · 10 lines
Rodolpho H. O. Eckhardt [email protected] Cel: 11 9126-9107 - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 7 lines · Paul
two genuine newbie questions :)
FYI: I'm running Slackware 8.1, (kernel = 2.4.18, iptables = 1.2.6a, dhcpd ISC v3.0pl1)
Q1. I've been tweaking my rc.firewall script a bit lately and am wondering if there is a way to have my new one take effect without rebooting?
It's been some time since I last looked at an rc.firewall script ... but usually they are written so you can just run them from the command line (as root, of course). They pretty much have to be able to reinstall themselves this way, as a change in DHCP lease address usually requires running them to regenerate the rulesets for use with the new IP address, and you don't want to reboot every time your DHCP lease changes (even Windows isn't *that* stupid).
Quoted 5 lines
Q2. Second, I'm still trying to get my dhcp server running, and am wondering what is the best way to stop the service and restart it. I've been killing the process, but there has to be a better way. In looking for the answer to this, I've seen postings saying to run, "dhcpd stop" but that doesn't seem to work with this one.
I'd be surprised to see any postings that say simply "dhcpd stop". More likely, they say something like "/etc/init.d/dhcpd stop", explaining how to do it on distros (the example I just typed is for Debian; RH and others are slightly different) that use init scripts with the start/stop/restart structure. The script just sends a SIGTERM to the daemon (the same signal kill sends by default).
Slackware doesn't do it this way (or didn't used to, back when I used it), so you pretty much are limited to kill'ing it, then starting it directly.
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Thanks for all the info! Quick follow up question on the rc.firewall script. I've tried running it, just by typing it's name when I'm in that folder at root. It says, "bash: rc.firewall-2.4: command not found" It's actually named, "rc.firewall-2.4" and I've made it executable already, it has a * next to its name when I do a listing. Any ideas?? TIA!
-Paul
----- Original Message -----
From: "Ray Olszewski" <[email protected]>
To: <[email protected]>
Sent: Thursday, February 27, 2003 2:16 PM
Subject: Re: iptables & a dhcpd question
Quoted 4 lines
Quoted 3 lines · Paul
two genuine newbie questions :)
FYI: I'm running Slackware 8.1, (kernel = 2.4.18, iptables = 1.2.6a,
dhcpd
Quoted 3 lines
Quoted 3 lines
ISC v3.0pl1)
Q1. I've been tweaking my rc.firewall script a bit lately and am
wondering
Quoted 4 lines
Quoted 1 line
if there is a way to have my new one take effect without rebooting?
It's been some time since I last looked at an rc.firewall script ... but usually they are written so you can just run them from the command line
(as
Quoted 8 lines
root, of course). They pretty much have to be able to reinstall themselves this way, as a change in DHCP lease address usually requires running them to regenerate the rulesets for use with the new IP address, and you don't want to reboot every time your DHCP lease changes (even Windows isn't *that* stupid).
Quoted 1 line
Q2. Second, I'm still trying to get my dhcp server running, and am
wondering
Quoted 1 line
Quoted 1 line
what is the best way to stop the service and restart it. I've been
killing
Quoted 1 line
Quoted 1 line
the process, but there has to be a better way. In looking for the answer
to
Quoted 1 line
Quoted 1 line
this, I've seen postings saying to run, "dhcpd stop" but that doesn't
seem
Quoted 5 lines
Quoted 1 line
to work with this one.
I'd be surprised to see any postings that say simply "dhcpd stop". More likely, they say something like "
/etc/init.d/dhcpdstop", explaining how
to
Quoted 1 line
do it on distros (the example I just typed is for Debian; RH and others
are
Quoted 9 lines
slightly different) that use init scripts with the start/stop/restart structure. The script just sends a SIGTERM to the daemon (the same signal kill sends by default).
Slackware doesn't do it this way (or didn't used to, back when I used it), so you pretty much are limited to kill'ing it, then starting it directly.
Quoted 6 lines
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 11 lines · Rodolpho H. O.
I don't know if this is what you are asking but.
I've never worked with Slackware, but try this:
/etc/(PATH TO rc.firewall)/rc.firewall
and when they say dhcpd stop, you have to add the path to it in the front:
/etc/init.d/dhcpdstop (if/etc/init.dis the path)I hope this works,
Huum, its plain to see you have never seen slackware, slackware does not even have a directory called /etc/init.d.
Slackware is not of the sysv catagory sorry.
Quoted 2 lines
Rodolpho
Signature · 9 lines
Regards Richard [email protected] http://people.zeelandnet.nl/pa3gcu/ - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 5 lines · Paul
Thanks for all the info! Quick follow up question on the rc.firewall script. I've tried running it, just by typing it's name when I'm in that folder at root. It says, "bash: rc.firewall-2.4: command not found" It's actually named, "rc.firewall-2.4" and I've made it executable already, it has a * next to its name when I do a listing. Any ideas?? TIA!
Yah. You can't run an executable unless it's in your path, or if you specify the path to the executable. So if you are in /etc/init.d, and you have a script there called rc.firewall-2.4, then type
./rc.firewall-2.4
The leading ./ is a path specification that satisfies the requirement.
HTH,
.brian
Signature · 8 lines
Brian P. Bilbrey <[email protected]> Orb Designs - To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 5 lines · Paul
Thanks for all the info! Quick follow up question on the rc.firewall script. I've tried running it, just by typing it's name when I'm in that folder at root. It says, "bash: rc.firewall-2.4: command not found" It's actually named, "rc.firewall-2.4" and I've made it executable already, it has a * next to its name when I do a listing. Any ideas?? TIA!
You'll have to tell bash where the script is; you could type the full path (/path/to/rc.firewall-2.4) or, if you're already in the directory where the script is type "./rc.firewall-2.4". That should work.
The script is now probarly not in one of the directorys where bash finds it's executables.
You could see these directorys if you type "echo $PATH".
Maybe you already have it, but it's good to flush your firewall-settings at the start of the script.
And please... Try to quote like it should be; below the answers. It's much easier to read that way!
But it seems to me, this list doesn't care about that... :(
HTH
--
Jos Lemmerling on Debian GNU/Linux jos(@)lemmerling(.nl)
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
animated gif creation
In reply to Eckhardt, Rodolpho H. O.I've just been full of problems this week. Now here is another one. I've captured a series of short avis which I'd like to import into an openoffice presentation. Unfortunately, openoffice will only accept animated gifs. My choices are now
1) Find a conversion package to let me create the animated gifs, or
2) Import the movies one $&%*# frame at a time and use the openoffice
animation tool.
Needless to say, I thought I'd check with you folks before I spent to much time on option 2. Does anyone know of software which can either
1) convert jpeg to gif. Then I could assemble the gifs with gifsicle, or
2) covert avi files (raw data or riff) directly to animated gifs.
Thanks for all the help,
Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
Quoted 2 lines
Quoted 2 lines
/etc/(PATH TO rc.firewall)/rc.firewall
^^^^^^^^^^^^^^^^^^^^^
/etc/rc.d/rc.firewall
Hmmm, it is plain to see that Richard gave you good advice.
:-|
locate rc.
Yes, IIRC, Slackware is BSD'ish, rather than SYSV'ish.
HTH, Chuck
Quoted 12 lines
Quoted 6 lines
and when they say dhcpd stop, you have to add the path to it in the front:
/etc/init.d/dhcpdstop (if/etc/init.dis the path)I hope this works,
Huum, its plain to see you have never seen slackware, slackware does not even have a directory called
/etc/init.d.
Slackware is not of the sysv catagory sorry.Quoted 1 line
Quoted 4 lines
Quoted 1 line
Rodolpho
--
Regards Richard
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs