<br>Jerry,<br><br>I will try out what you suggested when I get back to school on Monday.<br>I'll let you know what happens.<br><br>Thanks.<br>Gerald<br><br><div class="gmail_quote">On Sat, Sep 26, 2009 at 2:08 PM, Jerry Vonau <span dir="ltr"><<a href="mailto:jvonau@shaw.ca">jvonau@shaw.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On Sat, 2009-09-26 at 13:21 -0400, Gerald Ardito wrote:<br>
> Jerry,<br>
><br>
> Yes, we are adding the XS server to an existing network.<br>
> Our tech people created a VLAN for the XOs, points to 10.125.140.31 as<br>
> the DHCP server. So, computers coming into the network from these APs<br>
> have no other DHCP servers.<br>
</div>That sounds like the APs are acting as dhcp relays (as a router not a<br>
bridge)... These APs are also used with the existing network? This is<br>
really outside of what Martin had in mind...<br>
<div class="im"><br>
> I have been assuming that I therefore have to set eth1, which is<br>
> connected to that VLAN, to that IP address. Is that correct?<br>
<br>
</div>If the AP are acting as dhcp-relays, yes. The AP are directing the dhcp<br>
requests to 10.125.140.31, a bridge would just forward the traffic, and<br>
not "direct" it.<br>
<br>
The default layout doesn't provide for VLANs, but adding an ip alias to<br>
eth1 should be no problem. create an<br>
/etc/sysconfig/network-scripts/ifcfg-lanbond0:3 containing:<br>
<br>
DEVICE=lanbond0:3<br>
ONBOOT=yes<br>
IPADDR=10.125.140.31<br>
NETMASK=255.255.248.0<br>
BOOTPROTO=static<br>
IPV6INIT=no<br>
<br>
restart the network, you should see the alias with ifconfig..<br>
<br>
That should get the XS on the same lan as the AP's... then dhcp might<br>
work for you.<br>
<div class="im"><br>
> We also have another LAN which has its own DHCP server. I can have the<br>
> XOs connect to our "regular" wireless network, and they get IP<br>
> addresses and connect to the internet. I have trouble having more than<br>
> about 20 at a time connect to our regular network, plus I want the<br>
> benefits of the XS server.<br>
><br>
<br>
</div>That can be a problem, how is eth0 set? by dhcp from the "regular<br>
network"? Is the ip address in the 10.125.140.0 netblock? What gateway<br>
is the XS using? What is the output of "ip route ls"? Do both eth0 and<br>
eth1 plug into the same switch?<br>
<div class="im"><br>
> Does this help?<br>
><br>
> Thanks.<br>
> Gerald<br>
><br>
</div>some,<br>
<font color="#888888"><br>
Jerry<br>
<br>
<br>
</font></blockquote></div><br>