2008/8/20 David Leeming <[EMAIL PROTECTED]>: > I am setting up a server using a outdoor access point from Rural Link > (www.rurallink.co.nz) at our Patukae OLPC trial school site in Solomon > Islands. It's a type that can't get an IP address from a DHCP server and on > the LAN side needs to be fixed.
Jerry's answer is correct. Edit ifcfg-eth0 > Normally I have found, when setting up the XS, that if I attach a simple AP > to a second NIC using eth1, with DHCP, there is no additional configuration > required. It works by default. That sounds wrong. Maybe I'm misunderstanding what you've done but - eth0 is the WAN address. Attaching something to eth1 does not solve anything unless you've got eth0 and eth1 mixed up... - On the LAN side (eth1) don't let the AP act as a router or give DHCP leases. Set it to be a vanilla AP, no DHCP, routing or NAT'ting. It is up to the XS to do routing, NAT'ting, handing out DHCP leases and providing DNS services. > In the case of my Rural Link access point, I need to fix an IP address > within the range given by the server – which presumably it also uses to > allocate addresses to the XOs. So you are talking about 2 XSs and want one of the servers to be 'downstream' of the other? That'll need a bit of routing glue methinks. Tell us more about the network topology you're setting up... cheers, m -- [EMAIL PROTECTED] [EMAIL PROTECTED] -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff _______________________________________________ Server-devel mailing list [email protected] http://lists.laptop.org/listinfo/server-devel
