On Wed, Dec 14, 2005 at 09:20:06PM -0500, Chris Zakelj wrote:
> Here's the problem I've run into... after staring at the dhcpd.conf man
> page for a while, it didn't seem like you could feed it two interfaces
> at once. So off to Google, where the top articles (for Linux,
> admittedly) seem to confirm that you can't serve both the wired and the
> wireless internal interfaces at the same time.
Of course dhcpd can handle multiple interfaces. I don't know how you
could have gotten the idea that it couldn't. If you read even the
on-line synopsis of the manual page or looked at dhcpd's usage you
would see this is clearly supported.
Note the [...ifN]:
dhcpd [-dfn] [-c config-file] [-l lease-file] [if0 [...ifN]]
> I consider the possibility of putting ral0 into a bridge with fxp1, and
> thought this might work...
>
> /etc/hostname.fxp1:
> inet 192.168.0.1 255.255.255.0 NONE
>
> /etc/hostname.ral0:
> inet 192.168.0.6 255.255.255.0 media autoselect mediaopt hostap nwid
> this_is_only_a_test nwkey totally_sucks chan 11
> #I've also tried 172.16.0.0 255.255.0.0 with the same results
>
> /etc/bridgename.bridge0:
> add fxp1
> add ral0
> up
>
> /etc/dhcpd.interfaces
> fxp1 ral0 bridge0 #not sure whether ral0 or bridge0 is what dhcpd listens to
>
> and finally at the end of /etc/pf.conf
> pass quick on { fxp1, ral0, bridge0 }
>
> Needless to say, I'm getting no love there, either. Is what I'm trying
> to do simply not possible, or is there something (obvious, perhaps) that
> I'm missing. Yeah, I could go down the street and just buy a WAP, but
> that defeats the purpose of learning.
