Hi, Ed:
OK, between Greg, Shawn, and Jim on the Speakup list, and a gentleman on
the MidAtlantic Linux list, I have both dhcp and iptables working, I
think. I say, "think," because I haven't yet been able to get to the
server physically to test it. But, judging from the messages on screen,
the logs, and the pids, everything is working more or less as it should.
Here's what happened:
RE: iptables -- It turned out that I needed to get rid of ipchains first,
as per Jim Wantz' email on Saturday. lsmod now shows several iptables
modules loaded, and iptables -L (that's a cap L) displays a host of rules
which seem correct, to my only partially savvy sense.
The dhcpd thing turns out to be relatively straight forward, as well. The
required configuration file is /etc/dhcpd.conf, and there are several man
pages about it. Also, the Red Hat Customization Guide has a good section
on setting up dhcpd. My problem appears to have been a late night typo.
The fix I got was something I thought I had already tried. My best guess
is that I got a brace and a bracket confused, as in [ vs {. Essentially,
then answer is to declare a subnet and netmask but declare no range for
addresses to be assigned, so none will be.
On Mon, 5 Aug 2002, Edward L. Barnes wrote:
> Hi there Janina.
> First, do let the list or at least me (write to me direct if you'd like)
> know how you do with the ip masquerading stuff you wrote in about last
> week, I've been following that thread with alot of interest.
> In regard to your other question about having dhcpd start only on the
> single interface you want it to send and receive on, for example, I
> believe that the following bit of info is what you're looking for.
> Of course, if it doesn't work, let me know.
> You need to edit a file which influences dhcpd's behaviour.
> That file is:
> /etc/rc.d/init.d/dhcpd
> Down under where it says starting daemons there'll be a line which will
> read something like:
> daemon /usr/sbin/dhcpd $args
> Replace that line with something like the following, of course, replace
> the interface eth1 with something else if needed.
> daemon /usr/sbin/dhcpd eth1
> Then, of course, do service dhcpd restart to restart the daemon though
> you're a more experienced Linux user than I am so you undoubtedly
> already know that part.
> Hth and good luck!
>
> Ed Barnes
> Harbour Grace, Newfoundland, Canada
> home phone +1-709-596-3165
> e-mail and msn messenger id ebarnes at enigma2.cjb.net
> ********
> "There is a fantasy in Redmond that Microsoft products are innovative, but
> this is based entirely on a peculiar confusion of the words 'innovative'
> and 'successful.' Microsoft products are successful -- they make a lot of
> money -- but that doesn't make them innovative, or even particularly
> good." -ROBERT X. CRINGELY
> ********
>
>
> On Sun, 4 Aug 2002, Janina Sajka wrote:
>
> > I have an /etc/dhcpd.conf that appears to be working correctly with
> > respect to the nic where I want dhcp services. According to the man pages,
> > every nic requires a subnet statement, however, even if dhcpd is doing
> > nothing on a particular segment.
> >
> > But, how do I specify that it should ignore eth0?
> >
> > PS: Thanks to Jim, Greg, and Shawn for helping get the iptables working. I
> > think it's now correctly configured. Will test sometime early this week.
> >
> >
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
--
Janina Sajka, Director
Technology Research and Development
Governmental Relations Group
American Foundation for the Blind (AFB)
Email: janina at afb.net Phone: (202) 408-8175
Chair, Accessibility SIG
Open Electronic Book Forum (OEBF)
http://www.openebook.org
