[Server-devel] Network address for activation - Fwd: [Techteam] Activating laptops from the school server

[John Watlington]

DHCP was not recognizing msh0 interfaces brought up after
DHCP was started.   Instead of bringing DHCP down/up on every
networking device insertion, you can use a bridge to isolate the
issue.

DHCP is happy --- it finds all its network interfaces at boot time.
And whenever a msh device is inserted and attached to the right
bridge, DHCP works for it.

You cannot bridge the mesh interface together.   The explanation
would require more typing than I have time for now, but it has to
do with magic MAC addresses used to discover mesh gateways.

wad

On Aug 28, 2008, at 1:32 PM, Jerry Vonau wrote:

> Jerry Vonau wrote:
>> Jerry Vonau wrote:
>>> OR do you want msh0, msh1, and msh2 on the same bridge? That would
>>> require editing the BRIDGE= line to be the same bridge device in all
>>> three ifcfg-mshX files
>>
>> Sorry make that read TYPE=
>>
>
> Which reminds me, I might be missing something here, but what was the
> reasoning behind having one bridge per interface, and not just adding
> all the msh + eth1 devices to a single bridge, and use  
> 172.18.0.1/20 as
> the ip address of the bridge? Then it wouldn't matter if eth1 is  
> present
> or not, this main address would be bound to the bridge, and present as
> long as the bridge is active, even with no available devices for the
> bridge present. No dummies files required. ;-) If service  
> restriction is
> need, then just use iptables to block the unwanted traffic.
>
> Cleaner layout, no?
>
> Food for thought,
>
> Jerry
> _______________________________________________
> Server-devel mailing list
> Server-devel at lists.laptop.org
> http://lists.laptop.org/listinfo/server-devel