10-RC2 current wireless link aggregation not working correctly
dan_partelly
dan_partelly at rdsor.ro
Fri Dec 20 09:52:09 UTC 2013
Guys,
Id like to work a bit on this issue in my free time, I have 2 weeks
holiday
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).
Second:
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.
Dan
On Tue, 17 Dec 2013 12:11:49 -0800, Adrian Chadd <adrian.chadd at gmail.com>
wrote:
> 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.
> _______________________________________________
> freebsd-current at freebsd.org [2] mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current [3]
> To unsubscribe, send any mail to
> "freebsd-current-unsubscribe at freebsd.org [4]"
>
>
> Links:
> ------
> [1] mailto:dan_partelly at rdsor.ro
> [2] mailto:freebsd-current at freebsd.org
> [3] http://lists.freebsd.org/mailman/listinfo/freebsd-current
> [4] mailto:freebsd-current-unsubscribe at freebsd.org
More information about the freebsd-current
mailing list