Re: lagg0.2 style vlans on lagg(4) interface
- From: "Niki Denev" <nike_d@xxxxxxxxxxx>
- Date: Thu, 22 May 2008 01:14:37 +0300
On Thu, May 22, 2008 at 12:32 AM, Max Laier <max@xxxxxxxxxxxxxx> wrote:
On Wednesday 21 May 2008 23:22:52 Niki Denev wrote:
On Thu, May 22, 2008 at 12:05 AM, Max Laier <max@xxxxxxxxxxxxxx> wrote:^-------------------------------------------------
Looks good, though I'd probably move up the _INVOKE to before the
ARPs are sent out. Probably between twiddling the hardware and
sending ARPs (though that needs an else-case if the interface is
---------^still down). In fact the ARPs could be sent from an event hook, too.
This would get rid of INET specific code in the LL-interface code.
I thought about moving it up too, but in this case isn't it going to
be called only if the interface is up (IFF_UP)?
See above.
Oh, I've missed that.
So, generating ARPs from an event handler looks to like the best solution.
But in that case what would be the correct place for it?
if_ethersubr.c and the others (fw,fddi,arc...) that may use ARP?
Niki
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: lagg0.2 style vlans on lagg(4) interface
- From: Max Laier
- Re: lagg0.2 style vlans on lagg(4) interface
- References:
- lagg0.2 style vlans on lagg(4) interface
- From: Niki Denev
- Re: lagg0.2 style vlans on lagg(4) interface
- From: Max Laier
- Re: lagg0.2 style vlans on lagg(4) interface
- From: Niki Denev
- Re: lagg0.2 style vlans on lagg(4) interface
- From: Max Laier
- lagg0.2 style vlans on lagg(4) interface
- Prev by Date: Re: netatm removal warning
- Next by Date: Re: lagg0.2 style vlans on lagg(4) interface
- Previous by thread: Re: lagg0.2 style vlans on lagg(4) interface
- Next by thread: Re: lagg0.2 style vlans on lagg(4) interface
- Index(es):
Relevant Pages
|
|