[Server-devel] DNS/dhcp question

[Jerry Vonau]

On Sat, 2009-09-26 at 13:21 -0400, Gerald Ardito wrote:
> Jerry,
> 
> Yes, we are adding the XS server to an existing network.
> Our tech people created a VLAN for the XOs, points to 10.125.140.31 as
> the DHCP server. So, computers coming into the network from these APs
> have no other DHCP servers. 
That sounds like the APs are acting as dhcp relays (as a router not a
bridge)... These APs are also used with the existing network? This is
really outside of what Martin had in mind...  

> I have been assuming that I therefore have to set eth1, which is
> connected to that VLAN, to that IP address. Is that correct?

If the AP are acting as dhcp-relays, yes. The AP are directing the dhcp
requests to 10.125.140.31, a bridge would just forward the traffic, and
not "direct" it. 

The default layout doesn't provide for VLANs, but adding an ip alias to
eth1 should be no problem. create an 
/etc/sysconfig/network-scripts/ifcfg-lanbond0:3 containing: 

DEVICE=lanbond0:3
ONBOOT=yes
IPADDR=10.125.140.31
NETMASK=255.255.248.0
BOOTPROTO=static
IPV6INIT=no

restart the network, you should see the alias with ifconfig..

That should get the XS on the same lan as the AP's... then dhcp might
work for you.

> We also have another LAN which has its own DHCP server. I can have the
> XOs connect to our "regular" wireless network, and they get IP
> addresses and connect to the internet. I have trouble having more than
> about 20 at a time connect to our regular network, plus I want the
> benefits of the XS server.
> 

That can be a problem, how is eth0 set? by dhcp from the "regular
network"? Is the ip address in the 10.125.140.0 netblock? What gateway
is the XS using? What is the output of "ip route ls"? Do both eth0 and
eth1 plug into the same switch? 

> Does this help?
> 
> Thanks.
> Gerald
> 
some,

Jerry