Prev: latest kernel?
Next: How to "post-mortem" fileserver overload incidents?
From: Greg Russell on 12 Mar 2010 15:20
We're going to use a CentOS 5.4 box to act as a wireless bridge between
the ISP's tower and a neighbor's LAN. I would appreciate some help in
getting started understanding the issues involved in using dhcp on both
wireless interfaces simultaneously.

The wireless to the ISP's tower will need to be assigned by the ISP, yet
the neighbor's wireless interface and LAN should be a private dhcp
network e.g. 192.168/16 served by the bridge.

I'm unclear on how to accept the ISP's dhcp for the one interface and
simultaneously serve the neighbor's LAN with a local configuration on the
other interface.
From: Robert Nichols on 12 Mar 2010 20:07
On 03/12/2010 02:20 PM, Greg Russell wrote:
> We're going to use a CentOS 5.4 box to act as a wireless bridge between
> the ISP's tower and a neighbor's LAN. I would appreciate some help in
> getting started understanding the issues involved in using dhcp on both
> wireless interfaces simultaneously.
>
> The wireless to the ISP's tower will need to be assigned by the ISP, yet
> the neighbor's wireless interface and LAN should be a private dhcp
> network e.g. 192.168/16 served by the bridge.
>
> I'm unclear on how to accept the ISP's dhcp for the one interface and
> simultaneously serve the neighbor's LAN with a local configuration on the
> other interface.

Pretty close to being automatic, really.

You tell the dhcp server what subnet it is serving. It won't listen
on any interface that doesn't have an IP address in that range. Here's
what my subnet declaration looks like:

subnet 192.168.43.0 netmask 255.255.255.0 {
authoritative;
option routers 192.168.43.48;
option subnet-mask 255.255.255.0;
option domain-name "local";
option domain-name-servers 192.168.43.48;
option time-offset -21600; # Central Standard Time
option ntp-servers 192.168.43.48;

default-lease-time 86400; # 1 day
max-lease-time 345600; # 4 days
pool {
range 192.168.43.160 192.168.43.191;
allow unknown-clients;
}
pool {
range 192.168.43.96 192.168.43.127;
deny unknown-clients;
ping-check false;
}

}

I have one interface statically configured with an address in the
192.168.43.0/24 network. My ISP assigns the address (24.14.x.y) to the
other interface. The dhcp server ignores that second interface.

--
Bob Nichols AT comcast.net I am "RNichols42"
 | 
Pages: 1
Prev: latest kernel?
Next: How to "post-mortem" fileserver overload incidents?