[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: hostap mode on existing firewall
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: hostap mode on existing firewall
- From: Remco <remco_(_at_)_d-compu_(_dot_)_dyndns_(_dot_)_org>
- Date: Thu, 15 Dec 2005 13:10:15 +0100
- Organization: D-Compu
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.
Hoping I understand you correctly, won't something like this work ?
Put the interfaces you want to run dhcpd on in /etc/dhcpd.interfaces.
/etc/dhcpd.conf:
shared-network LOCAL-NET {
option domain-name "my.domain";
option domain-name-servers 192.168.10.1;
subnet 192.168.10.0 netmask 255.255.255.0 {
option routers 192.168.10.1;
range 192.168.10.32 192.168.10.127;
}
}
shared-network WLAN {
option domain-name "wlan.my.domain";
option domain-name-servers 192.168.20.1;
subnet 192.168.20.0 netmask 255.255.255.0 {
option routers 192.168.20.1;
range 192.168.20.32 192.168.20.127;
}
}
// end of /etc/dhcpd.conf
LOCAL-NET serves the wired interface configured as 192.168.10.1
WLAN serves the wireless interface configured as 192.168.20.1
Your /var/log/daemon may show dhcpd messages telling you for which interface
you're missing subnet definitions.
I think the trick is to have subnet definitions that correspond to the ip
addresses of the interfaces you want to run dhcpd on.
Visit your host, monkey.org