[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 6.0BETA3 panic in ip_output (vlan/RIP related?)
- To: rwatson_(_at_)_freebsd_(_dot_)_org, yar_(_at_)_comp_(_dot_)_chem_(_dot_)_msu_(_dot_)_su
- Subject: Re: 6.0BETA3 panic in ip_output (vlan/RIP related?)
- From: Mark Tinguely <tinguely_(_at_)_casselton_(_dot_)_net>
- Date: Tue, 6 Sep 2005 10:35:47 -0500 (CDT)
- Cc: freebsd-current_(_at_)_freebsd_(_dot_)_org
> So it sounds like we need to figure out how the multicast code should
> behave on interface removal -- I wonder what other operating systems do
> here? Do they simply invalidate current membership related with the
> interface, or do they leave the multicast sockets in a state such that if
> the interface comes back, the memberships are re-bound?
In the case of a non-local multicast sessions, the saved multicast socket
state would need to keep a timestamp of the last a multicast router IGMP
session probe to detect the possibility of session pruning.
--Mark Tinguely.
_______________________________________________
freebsd-current_(_at_)_freebsd_(_dot_)_org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe_(_at_)_freebsd_(_dot_)_org"
Visit your host, monkey.org