Yar Tikhiy wrote:
Quagga still uses it, too, if its configure script detects FreeBSD
or NetBSD. I'm afraid it was me who submitted the patch to the
Quagga folks when I'd found that Quagga's ospfd couldn't handle
unnumbered P2P interfaces in FreeBSD because their local IPs weren't
unique. Unfort
On 4/6/07, Tai-hwa Liang <[EMAIL PROTECTED]> wrote:
On Thu, 5 Apr 2007, Jack Vogel wrote:
> Our test group uses a script that does 100 iterations of
> a module load, then bring up all interfaces, and then
> unload driver.
>
> Depending on the system in anything from just a few
> iterations to 20
Hi,
For a while now I have had a patch available to teach olsrd to use
IP_ONESBCAST instead of using libnet/bpf just to send broadcast
datagrams in FreeBSD, which has had IP_ONESBCAST for a few years now.
If anyone is using olsrd on FreeBSD I would greatly appreciate testing
and feedback for
nterface
>> it always deassociates a few seconds after associating.
>> If i remove it from the trunk group it associates perfectly, and
>> keeps the link up.
>
> The updated patch here partially fixes the problem, the EAP packets will
> be passed now.
>
> http://people.fr
Current FreeBSD problem reports
Critical problems
Serious problems
S Tracker Resp. Description
a kern/38554 netchanging interface ipaddress doesn't seem to work
s kern/39937 netipstealth
nterface
>> it always deassociates a few seconds after associating.
>> If i remove it from the trunk group it associates perfectly, and
>> keeps the link up.
>
> The updated patch here partially fixes the problem, the EAP packets will
> be passed now.
>
> http://people.fr
associates perfectly, and
> keeps the link up.
The updated patch here partially fixes the problem, the EAP packets will
be passed now.
http://people.freebsd.org/~thompsa/if_trunk-20070409.diff
The remaining issue is that when the wireless interface is added to the
trunk it will get a down/up
