Id like to work a bit on this issue in my free time, I have 2 weeks
after Xmass. 

First an update on lagg for the case you boot with wired coupled:

1. I previously said lagg0 switches correctly when I unplug the wired 
interface, but it is not so. It appeared so because I used "ifconfig"
and listed all interfaces. If I do a ifconfig lagg0 specifically
the network activity DOES NOT resume, and  the output shows that the 
interface was not switched.
2. network activity resumes when you specifically do ifconfig bge0 (
master wired). 


1. Please tell me if one of the developers made on their personal pages
a intro how to set up a solid kernel development intro. It would save me 
a lot  of time considering I never set up such an environment for 
any Unix like OS. I only worked in kernel development for NT and later 
derived kernels. I can allocate two core 2 machines for this task , with 
fire-wire, USN and Ethernet connectivity

2. Any other resources which you can come up from your head which I can
print and read are also appreciated. 


On Tue, 17 Dec 2013 12:11:49 -0800, Adrian Chadd <>
> Ive no idea sorry. Its likely an ifnet change and not anything WiFi
> specific. :( On Dec 17, 2013 12:04 PM, "dan_partelly"  wrote:
>  Yes, this is correct. A simple list of the interfaces with ifconfig
>  makes the system recover and restart activity on the secondary port.
>  Its a good starting point to hunt down the problem. One of the ioctls
> sent
>  has this "side effect".
>  Dan
>  > If I am am understanding correctly, Dan and Nikolai say that just
>  > running ifconfig brings the lagg back to life. Why would that make a
>  > difference at all? Running ifconfig with no parameters shouldnt be
>  > changing anything.
>  _______________________________________________
> [2] mailing list
> [3]
>  To unsubscribe, send any mail to
> " [4]"
> Links:
> ------
> [1]
> [2]
> [3]
> [4]
_______________________________________________ mailing list
To unsubscribe, send any mail to ""

Reply via email to