Martin Blapp wrote:
I't is my goal to make dhclient really functional, so it can not only be used with one interface, but several.
On a well known OS this works just fine. A first interface gets initialized and the GW gets set as usual. But if a second interface gets added, and the first one is still active and has a working lease, the GW will not be overwriten. If you remove now the first interface, the default GW changes to the one of the second interface.
[ ... ]
If there are other ideas, I'm open to them.
You could add kevents for interface arrival and departure, and add a kqueue to the dhcpd to catch the arrival/departure events, and then just act on them.
Instead of just adding the stuff to devd?
--
Daniel C. Sobral (8-DCS)
Gerencia de Operacoes
Divisao de Comunicacao de Dados
Coordenacao de Seguranca
VIVO Centro Oeste Norte
Fones: 55-61-313-7654/Cel: 55-61-9618-0904
E-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]Outros:
[EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]Some people have parts that are so private they themselves have no knowledge of them.
_______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
