Hallo, Simon,
Du meintest am 02.07.12:
>>> dhcp-range may have an interface name supplied as
>>> "interface:> name>> ".
>> I'd like to use this feature in many schools:
>>
>> eth0 and eth1 for the school clients in the LAN, eth2 for the
>> private clients (especially in the WLAN). And eth3 for D
> De: Helmut Hullen
> > Although you don't like udev, I think it's an important
> > part of your final solution.
>
> Sorry - I disagree. "udev" moves the problems, it doesn't
> solve them.
Okay, let's rephrase it and be accurate: udev does *not* solve your problem.
Instead udev provides more ap
Hallo, Ed,
Du meintest am 02.07.12:
[dhcp-range=ethx,...]
>>> What about [re]naming those interface names using udev, i.e.
>>> xx-persistent-net.rules file in /etc/udev/rules.d/ ?
>> That moves the problem from one place to another. I don't like
>> "udev", I don't use "udev". Especially with mo
On 02/07/12 04:42, Helmut Hullen wrote:
> Hallo, Simon,
>
> Du meintest am 01.07.12:
>
>> A quote from the man page:
>
>> dhcp-range may have an interface name supplied as
>> "interface: name>> ". The semantics if this are as follows: For DHCP, if any other
>> dhcp-range exists _without_ an int
On 02/07/2012 08:30, Helmut Hullen wrote:
Hallo, Vincent,
Du meintest am 02.07.12:
But it seems to be a bit more difficult to change
automatically something like
dhcp-range=eth0,192.168.0.10,static
dhcp-range=eth1,192.168.1,10,static
dhcp-range=eth2,192.168.17.10-192.168,28.250
Hallo, Vincent,
Du meintest am 02.07.12:
>> But it seems to be a bit more difficult to change
>> automatically something like
>>
>> dhcp-range=eth0,192.168.0.10,static
>> dhcp-range=eth1,192.168.1,10,static
>> dhcp-range=eth2,192.168.17.10-192.168,28.250
>>
>> to
>>
>> dhcp-range
Hello Helmut.
> De: Helmut Hullen
> Date: Lundi 2 juillet 2012, 5h42
> But it seems to be a bit more difficult to change
> automatically something like
>
> dhcp-range=eth0,192.168.0.10,static
> dhcp-range=eth1,192.168.1,10,static
> dhcp-range=eth2,192.168.17.10-192.168,28.250
>
>
