On Tue, Sep 2, 2008 at 7:10 PM, Jerry Vonau <[EMAIL PROTECTED]> wrote: > Martin Langhoff wrote: >> - there seems to be no routing between 172.18.16.x and 172.18.0.1 >> > > GATEWAY1=172.18.1.2 > ADDRESS1=172.18.16.0 > NETMASK1=255.255.248.0 > > Is routed out eth1 though 1.2, based on the .2, that should be for a second > xs server no?
Oops. You are right. Hmmm. Two problems - The address must be served by server 1 so single server setups just work for activation. My recommendation is going to be for single server setups for quite a while I suspect... (deciding where to split the workload without seeing the workload is something I rather not do :-/ perhaps once I've seen a couple of real life sites with heavy workload I'll warm up to some pre-canned rules on how to split the services...) - The routing there is off - server number 2 does not know 172.18.16.x -- if I call network_config 2 br0 is on .18 not .16 . I copied the routing straight from olpc-mesh-config, >From what I can see, each server gets a /21, starting from the "second" /21 block, so .16.1 is the first address of server 2. Looking at it from the 'each server role gets its own /21' POV, - the first /21 is unused - each server is leaving the first /23 unused. For example, server 2 uses .18 to .23 but leaves .16.1 to .17.255 unused > You could use iptables here with a rule kind of like the squid rules, > intercepting the traffic to 172.18.16.1 Yes, there are several ways to skin this cat, at the moment I'm keen on hearing from Wad what the original plan was. I don't tihnk anyone has deployed multi-server setups, so we can move this stuff around as we see fit. One of the possibilities is to shift all servers >1 a few netblocks and grab 172.18.10.1/19 for "server 1" to manage (in the "assign dhcp leases and route" sense). This has 8190 addresses - hang a big chunk of that off eth1 and you can safely wire up a school with many APs and to serve a large population of XOs. 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 Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
