Re: 10-RC2 current wireless link aggregation not working correctly
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.ch...@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@freebsd.org [2] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current [3] To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org [4] Links: -- [1] mailto:dan_parte...@rdsor.ro [2] mailto:freebsd-current@freebsd.org [3] http://lists.freebsd.org/mailman/listinfo/freebsd-current [4] mailto:freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10-RC2 current wireless link aggregation not working correctly
Hi! On 20 December 2013 01:52, dan_partelly dan_parte...@rdsor.ro wrote: 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). Hm. Well, doing an ifconfig bge0 will likely do a bunch of queries to the NIC to figure out what the current link status is. I bet what's happening is that the link status isn't being updated correctly, so lagg doesn't flip over. 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. Have a read of the FreeBSD handbook: https://www.freebsd.org/doc/handbook/ And if you have questions about the networking side of things, please don't hesitate to email the list(s). We can turn whatever question/answers you have into a chapter or two in the handbook. -a Dan On Tue, 17 Dec 2013 12:11:49 -0800, Adrian Chadd adrian.ch...@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@freebsd.org [2] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current [3] To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org [4] Links: -- [1] mailto:dan_parte...@rdsor.ro [2] mailto:freebsd-current@freebsd.org [3] http://lists.freebsd.org/mailman/listinfo/freebsd-current [4] mailto:freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
10-RC2 current wireless link aggregation not working correctly
Hi all, I've set up wireless link aggregation on FreeBSD 10 RC1 and RC2 as described in the FreeBSD handbook, on an oldish Compaq nc6320 laptop. What happens is: If I boot the system with the Ethernet cable attached, I correctly get lagg0 active port on master- bg0- and the network is working correctly. (I mainly test pinging my gateway). When I pull the cable out, lagg0 device correctly switches to wlan0 as shown by ifconfig (wlan0 is created from wpi0), but at the same time I get no more ping replies from my gateway. I can leave the system in this state for several minutes as an example and no replies are coming through. A simple list of interfaces with ifconfig with no parameters brigs the network back to life, and I start to get back the due ping replyes, this time thrugh wireless link. Please, if possible en-light me on tis problem. I sat at your disposition with any info you may deem necessary to get this fixed (if it needs a fix). Dan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10-RC2 current wireless link aggregation not working correctly
On 12/17/13 08:06, dan_partelly wrote: Hi all, I've set up wireless link aggregation on FreeBSD 10 RC1 and RC2 as described in the FreeBSD handbook, on an oldish Compaq nc6320 laptop. What happens is: If I boot the system with the Ethernet cable attached, I correctly get lagg0 active port on master- bg0- and the network is working correctly. (I mainly test pinging my gateway). When I pull the cable out, lagg0 device correctly switches to wlan0 as shown by ifconfig (wlan0 is created from wpi0), but at the same time I get no more ping replies from my gateway. I can leave the system in this state for several minutes as an example and no replies are coming through. A simple list of interfaces with ifconfig with no parameters brigs the network back to life, and I start to get back the due ping replyes, this time thrugh wireless link. Please, if possible en-light me on tis problem. I sat at your disposition with any info you may deem necessary to get this fixed (if it needs a fix). Dan I can confirm this behavior. It also happens to me. - Nikolai Lifanov. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10-RC2 current wireless link aggregation not working correctly
Hi, The MAC of the lagg needs to be the same as the wireless interface. I'm going to just state right now that using lagg as the failover method for doing wireless/wired integration isn't supported by me. If someone wants to make it supported then they need to claim it. :) -a On 17 December 2013 05:06, dan_partelly dan_parte...@rdsor.ro wrote: Hi all, I've set up wireless link aggregation on FreeBSD 10 RC1 and RC2 as described in the FreeBSD handbook, on an oldish Compaq nc6320 laptop. What happens is: If I boot the system with the Ethernet cable attached, I correctly get lagg0 active port on master- bg0- and the network is working correctly. (I mainly test pinging my gateway). When I pull the cable out, lagg0 device correctly switches to wlan0 as shown by ifconfig (wlan0 is created from wpi0), but at the same time I get no more ping replies from my gateway. I can leave the system in this state for several minutes as an example and no replies are coming through. A simple list of interfaces with ifconfig with no parameters brigs the network back to life, and I start to get back the due ping replyes, this time thrugh wireless link. Please, if possible en-light me on tis problem. I sat at your disposition with any info you may deem necessary to get this fixed (if it needs a fix). Dan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10-RC2 current wireless link aggregation not working correctly
On 12/17/13 10:54, Adrian Chadd wrote: Hi, The MAC of the lagg needs to be the same as the wireless interface. I'm going to just state right now that using lagg as the failover method for doing wireless/wired integration isn't supported by me. If someone wants to make it supported then they need to claim it. :) -a On 17 December 2013 05:06, dan_partelly dan_parte...@rdsor.ro wrote: Hi all, I've set up wireless link aggregation on FreeBSD 10 RC1 and RC2 as described in the FreeBSD handbook, on an oldish Compaq nc6320 laptop. What happens is: If I boot the system with the Ethernet cable attached, I correctly get lagg0 active port on master- bg0- and the network is working correctly. (I mainly test pinging my gateway). When I pull the cable out, lagg0 device correctly switches to wlan0 as shown by ifconfig (wlan0 is created from wpi0), but at the same time I get no more ping replies from my gateway. I can leave the system in this state for several minutes as an example and no replies are coming through. A simple list of interfaces with ifconfig with no parameters brigs the network back to life, and I start to get back the due ping replyes, this time thrugh wireless link. Please, if possible en-light me on tis problem. I sat at your disposition with any info you may deem necessary to get this fixed (if it needs a fix). Dan It actually is, in my case. The macs for em0, wlan0, and lagg0 all match. I can always do the failover differently, but this used to work with 9.0-RELEASE-9.2-RELEASE. - Nikolai Lifanov ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10-RC2 current wireless link aggregation not working correctly
On Tue, 17 Dec 2013 07:54:52 -0800, Adrian Chadd adr...@freebsd.org wrote: Hi, All 3 MACs are the same. wpi0 is set to the MAC of bg0. Wlan0 inherits the MAC of wpi0. Lagg0 is set up to the MAC of master. So everything checks out. All are the same. I have to check if the systems sends packets to the gateway after the switch on wlan0, but fails to get any packets back. I didnt had time yet for this. If someone wants to make it supported then they need to claim it. :) Who from the FreeBSD team supports it ? Dan The MAC of the lagg needs to be the same as the wireless interface. I'm going to just state right now that using lagg as the failover method for doing wireless/wired integration isn't supported by me. If someone wants to make it supported then they need to claim it. :) -a On 17 December 2013 05:06, dan_partelly dan_parte...@rdsor.ro wrote: Hi all, I've set up wireless link aggregation on FreeBSD 10 RC1 and RC2 as described in the FreeBSD handbook, on an oldish Compaq nc6320 laptop. What happens is: If I boot the system with the Ethernet cable attached, I correctly get lagg0 active port on master- bg0- and the network is working correctly. (I mainly test pinging my gateway). When I pull the cable out, lagg0 device correctly switches to wlan0 as shown by ifconfig (wlan0 is created from wpi0), but at the same time I get no more ping replies from my gateway. I can leave the system in this state for several minutes as an example and no replies are coming through. A simple list of interfaces with ifconfig with no parameters brigs the network back to life, and I start to get back the due ping replyes, this time thrugh wireless link. Please, if possible en-light me on tis problem. I sat at your disposition with any info you may deem necessary to get this fixed (if it needs a fix). Dan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10-RC2 current wireless link aggregation not working correctly
On 12/17/13 10:54, Adrian Chadd wrote: Hi, The MAC of the lagg needs to be the same as the wireless interface. I'm going to just state right now that using lagg as the failover method for doing wireless/wired integration isn't supported by me. If someone wants to make it supported then they need to claim it. :) -a On 17 December 2013 05:06, dan_partelly dan_parte...@rdsor.ro wrote: Hi all, I've set up wireless link aggregation on FreeBSD 10 RC1 and RC2 as described in the FreeBSD handbook, on an oldish Compaq nc6320 laptop. What happens is: If I boot the system with the Ethernet cable attached, I correctly get lagg0 active port on master- bg0- and the network is working correctly. (I mainly test pinging my gateway). When I pull the cable out, lagg0 device correctly switches to wlan0 as shown by ifconfig (wlan0 is created from wpi0), but at the same time I get no more ping replies from my gateway. I can leave the system in this state for several minutes as an example and no replies are coming through. A simple list of interfaces with ifconfig with no parameters brigs the network back to life, and I start to get back the due ping replyes, this time thrugh wireless link. Please, if possible en-light me on tis problem. I sat at your disposition with any info you may deem necessary to get this fixed (if it needs a fix). Dan Also, this method is still described in the handbook: https://www.freebsd.org/doc/handbook/network-aggregation.html#networking-lagg-wired-and-wireless If this isn't supposed to work, then the handbook needs to be updated. - Nikolai Lifanov ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10-RC2 current wireless link aggregation not working correctly
I'm the wireless stack maintainer and I currently don't support that. Sorry. -a On 17 December 2013 08:10, dan_partelly dan_parte...@rdsor.ro wrote: On Tue, 17 Dec 2013 07:54:52 -0800, Adrian Chadd adr...@freebsd.org wrote: Hi, All 3 MACs are the same. wpi0 is set to the MAC of bg0. Wlan0 inherits the MAC of wpi0. Lagg0 is set up to the MAC of master. So everything checks out. All are the same. I have to check if the systems sends packets to the gateway after the switch on wlan0, but fails to get any packets back. I didnt had time yet for this. If someone wants to make it supported then they need to claim it. :) Who from the FreeBSD team supports it ? Dan The MAC of the lagg needs to be the same as the wireless interface. I'm going to just state right now that using lagg as the failover method for doing wireless/wired integration isn't supported by me. If someone wants to make it supported then they need to claim it. :) -a On 17 December 2013 05:06, dan_partelly dan_parte...@rdsor.ro wrote: Hi all, I've set up wireless link aggregation on FreeBSD 10 RC1 and RC2 as described in the FreeBSD handbook, on an oldish Compaq nc6320 laptop. What happens is: If I boot the system with the Ethernet cable attached, I correctly get lagg0 active port on master- bg0- and the network is working correctly. (I mainly test pinging my gateway). When I pull the cable out, lagg0 device correctly switches to wlan0 as shown by ifconfig (wlan0 is created from wpi0), but at the same time I get no more ping replies from my gateway. I can leave the system in this state for several minutes as an example and no replies are coming through. A simple list of interfaces with ifconfig with no parameters brigs the network back to life, and I start to get back the due ping replyes, this time thrugh wireless link. Please, if possible en-light me on tis problem. I sat at your disposition with any info you may deem necessary to get this fixed (if it needs a fix). Dan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10-RC2 current wireless link aggregation not working correctly
On 17 December 2013 08:12, Nikolai Lifanov lifa...@mail.lifanov.com wrote: Also, this method is still described in the handbook: https://www.freebsd.org/doc/handbook/network-aggregation.html#networking-lagg-wired-and-wireless If this isn't supposed to work, then the handbook needs to be updated. I'd be really happy if someone removed it until it was actually debugged correctly and documented in the code. -adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10-RC2 current wireless link aggregation not working correctly
No problem. Can you point me to the relevant source files in the kernel tree, please ? Dan On Tue, 17 Dec 2013 08:43:09 -0800, Adrian Chadd adr...@freebsd.org wrote: I'm the wireless stack maintainer and I currently don't support that. Sorry. -a On 17 December 2013 08:10, dan_partelly dan_parte...@rdsor.ro wrote: On Tue, 17 Dec 2013 07:54:52 -0800, Adrian Chadd adr...@freebsd.org wrote: Hi, All 3 MACs are the same. wpi0 is set to the MAC of bg0. Wlan0 inherits the MAC of wpi0. Lagg0 is set up to the MAC of master. So everything checks out. All are the same. I have to check if the systems sends packets to the gateway after the switch on wlan0, but fails to get any packets back. I didnt had time yet for this. If someone wants to make it supported then they need to claim it. :) Who from the FreeBSD team supports it ? Dan The MAC of the lagg needs to be the same as the wireless interface. I'm going to just state right now that using lagg as the failover method for doing wireless/wired integration isn't supported by me. If someone wants to make it supported then they need to claim it. :) -a On 17 December 2013 05:06, dan_partelly dan_parte...@rdsor.ro wrote: Hi all, I've set up wireless link aggregation on FreeBSD 10 RC1 and RC2 as described in the FreeBSD handbook, on an oldish Compaq nc6320 laptop. What happens is: If I boot the system with the Ethernet cable attached, I correctly get lagg0 active port on master- bg0- and the network is working correctly. (I mainly test pinging my gateway). When I pull the cable out, lagg0 device correctly switches to wlan0 as shown by ifconfig (wlan0 is created from wpi0), but at the same time I get no more ping replies from my gateway. I can leave the system in this state for several minutes as an example and no replies are coming through. A simple list of interfaces with ifconfig with no parameters brigs the network back to life, and I start to get back the due ping replyes, this time thrugh wireless link. Please, if possible en-light me on tis problem. I sat at your disposition with any info you may deem necessary to get this fixed (if it needs a fix). Dan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10-RC2 current wireless link aggregation not working correctly
On 2013-12-17 10:54, Adrian Chadd wrote: Hi, The MAC of the lagg needs to be the same as the wireless interface. I'm going to just state right now that using lagg as the failover method for doing wireless/wired integration isn't supported by me. If someone wants to make it supported then they need to claim it. :) -a On 17 December 2013 05:06, dan_partelly dan_parte...@rdsor.ro wrote: Hi all, I've set up wireless link aggregation on FreeBSD 10 RC1 and RC2 as described in the FreeBSD handbook, on an oldish Compaq nc6320 laptop. What happens is: If I boot the system with the Ethernet cable attached, I correctly get lagg0 active port on master- bg0- and the network is working correctly. (I mainly test pinging my gateway). When I pull the cable out, lagg0 device correctly switches to wlan0 as shown by ifconfig (wlan0 is created from wpi0), but at the same time I get no more ping replies from my gateway. I can leave the system in this state for several minutes as an example and no replies are coming through. A simple list of interfaces with ifconfig with no parameters brigs the network back to life, and I start to get back the due ping replyes, this time thrugh wireless link. Please, if possible en-light me on tis problem. I sat at your disposition with any info you may deem necessary to get this fixed (if it needs a fix). Dan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org 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 shouldn't be changing anything. -- Allan Jude signature.asc Description: OpenPGP digital signature
Re: 10-RC2 current wireless link aggregation not working correctly
On 12/17/13 12:34, Allan Jude wrote: On 2013-12-17 10:54, Adrian Chadd wrote: Hi, The MAC of the lagg needs to be the same as the wireless interface. I'm going to just state right now that using lagg as the failover method for doing wireless/wired integration isn't supported by me. If someone wants to make it supported then they need to claim it. :) -a On 17 December 2013 05:06, dan_partelly dan_parte...@rdsor.ro wrote: Hi all, I've set up wireless link aggregation on FreeBSD 10 RC1 and RC2 as described in the FreeBSD handbook, on an oldish Compaq nc6320 laptop. What happens is: If I boot the system with the Ethernet cable attached, I correctly get lagg0 active port on master- bg0- and the network is working correctly. (I mainly test pinging my gateway). When I pull the cable out, lagg0 device correctly switches to wlan0 as shown by ifconfig (wlan0 is created from wpi0), but at the same time I get no more ping replies from my gateway. I can leave the system in this state for several minutes as an example and no replies are coming through. A simple list of interfaces with ifconfig with no parameters brigs the network back to life, and I start to get back the due ping replyes, this time thrugh wireless link. Please, if possible en-light me on tis problem. I sat at your disposition with any info you may deem necessary to get this fixed (if it needs a fix). Dan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org 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 shouldn't be changing anything. I see the same lagg behavior change going from 9.2-10.0, but for me the test is slightly different. My wired and wireless networks use different IP address ranges, so I need to re-run dhclient on lagg0, but I can't get an address on it. In fact, dhclient doesn't work at all with a lagg interface when it is only backed by my wireless card. Without a lagg interface, I can get addresses on both wired and wireless cards individually and act dual-homed just fine. - Nikolai Lifanov ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10-RC2 current wireless link aggregation not working correctly
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 shouldn't be changing anything. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10-RC2 current wireless link aggregation not working correctly
Ive no idea sorry. Its likely an ifnet change and not anything WiFi specific. :( On Dec 17, 2013 12:04 PM, dan_partelly dan_parte...@rdsor.ro 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 shouldn't be changing anything. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10-RC2 current wireless link aggregation not working correctly
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 12/17/13 09:34, Allan Jude wrote: 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 shouldn't be changing anything. I don't really believe these claim. I had similar issue in the past and found an 'arp -a -d' would fix it so I didn't pursued further but I think this would be an interesting problem to get addressed. If I would take an guess, I would start from making lagg(4) interface to initiate one or a few gratuitous ARP broadcast when the active port changes. Some switches could use this to kick out their (outdated) memory of where the port is. Cheers, - -- Xin LI delp...@delphij.nethttps://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJSsPQLAAoJEJW2GBstM+nsyXoP/RCeHdu1PVCooIUxzjhqWMJG 3RyN9i85O1WYpgZwHCSC9mkFKM6GjEIiyaNKCvdYzN/k+d9aCQSXIShgIGutM6ie hFD4GCGrevjquHCddpULlUE+iwj0qIJWSyRMusUgo+ya+Bc/4H+szoxTndXaaamz CPkZMuzga8kEApXgMvImGfsqB8FqqFNtEELlRmISEHb04iAGqUv6HwoL1DhqEZ3I tQQi73JvuCU3Lfbp4CDI0IeTzlAoARBX/mWFjlDm7CA8clu4PzIVhdsRxRUhXIId ijI8432al9XXt0m4+4LIKmJa6DlyvQ3pIZDFodryQ1za3PAaF7IheILFKPi9BAwi Tn47X2+2XYXx7ZS2S22R7KRgeORZqj2uYZifs/xsNwkBCsyntYZgH+c5qYU7TWb/ tWRi9c5uVFskoPx4JL4W3ctgPvN7TpvKeCBLZTBdLQjy9WT6sqhxChxS57SFT5AH kTOWNEA0PqWjrrqRlNO47TL/aTg3Js9S4KxIZ2+hHSkDAlMxGi9rHzyHYPQKxJ1V lLmLGN0ZRYGGKa4Yn2OBAy16q/I2jkLE0Nkb0u1V3EEMkKQWp6pcro/Kb9Hrirfe n6zrFVyzLTIgNpr9C1+By1CxAmJfg73cIoobJSjNDZ2+EpY+FRDdhKYip3xtpNfA QFmabonocmaEohNcC8me =mSYS -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10-RC2 current wireless link aggregation not working correctly
Hi, On Tue, 17 Dec 2013 17:02:03 -0800 Xin Li delp...@delphij.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 12/17/13 09:34, Allan Jude wrote: 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 shouldn't be changing anything. I don't really believe these claim. it does not work with iwn and em. I had similar issue in the past and found an 'arp -a -d' would fix It also does not work. The machine is running FreeBSD 10.0 RC2. Erich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10-RC2 current wireless link aggregation not working correctly
What claims you do not believe ? Not important anyway. This is engineering, so you need not believe, you need to know. Go and replicate the bug. You will know then. I don't really believe these claim. I had similar issue in the past and found an 'arp -a -d' would fix it so I didn't pursued further but I think this would be an interesting problem to get addressed. If I would take an guess, I would start from making lagg(4) interface to initiate one or a few gratuitous ARP broadcast when the active port changes. Some switches could use this to kick out their (outdated) memory of where the port is. Cheers, - -- Xin LI delp...@delphij.nethttps://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJSsPQLAAoJEJW2GBstM+nsyXoP/RCeHdu1PVCooIUxzjhqWMJG 3RyN9i85O1WYpgZwHCSC9mkFKM6GjEIiyaNKCvdYzN/k+d9aCQSXIShgIGutM6ie hFD4GCGrevjquHCddpULlUE+iwj0qIJWSyRMusUgo+ya+Bc/4H+szoxTndXaaamz CPkZMuzga8kEApXgMvImGfsqB8FqqFNtEELlRmISEHb04iAGqUv6HwoL1DhqEZ3I tQQi73JvuCU3Lfbp4CDI0IeTzlAoARBX/mWFjlDm7CA8clu4PzIVhdsRxRUhXIId ijI8432al9XXt0m4+4LIKmJa6DlyvQ3pIZDFodryQ1za3PAaF7IheILFKPi9BAwi Tn47X2+2XYXx7ZS2S22R7KRgeORZqj2uYZifs/xsNwkBCsyntYZgH+c5qYU7TWb/ tWRi9c5uVFskoPx4JL4W3ctgPvN7TpvKeCBLZTBdLQjy9WT6sqhxChxS57SFT5AH kTOWNEA0PqWjrrqRlNO47TL/aTg3Js9S4KxIZ2+hHSkDAlMxGi9rHzyHYPQKxJ1V lLmLGN0ZRYGGKa4Yn2OBAy16q/I2jkLE0Nkb0u1V3EEMkKQWp6pcro/Kb9Hrirfe n6zrFVyzLTIgNpr9C1+By1CxAmJfg73cIoobJSjNDZ2+EpY+FRDdhKYip3xtpNfA QFmabonocmaEohNcC8me =mSYS -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10-RC2 current wireless link aggregation not working correctly
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 12/17/13, 11:28 PM, dan_partelly wrote: What claims you do not believe ? Not important anyway. This is engineering, so you need not believe, you need to know. Go and replicate the bug. You will know then. I don't believe in merely doing 'ifconfig' would workaround the issue, it does not make sense, plus I have tested and it didn't work for my case (iwn+em on my laptop). I'm aware of the issue but thought it was compatibility issue with my own weirdly setup wireless AP at the time, and looks like it's not just me, but I'm not interested nor have time to fix the problem so I replied the thread and offered what I have tested as a workaround in the hope that it's useful for someone who is interested and have the ability to fix the problem. Cheers, -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJSsVEkAAoJEJW2GBstM+nswTsP/Rs0hdyXNejf2Z98GbSGns0n lsI+UmjwWUSg0h+8QzCce7/80mwEw0tZH1btoRr6I0tPKXwdUYDO2C3LPM2a/jSV hvN6aay0ppnldtsqMZcuDv1OznSGfEIt0A04/m/RUTDBYaPKY+F1iqZYNE960zes u6mbR2elpAUCHjpV3lEchnP5V1v/yLpVziGYabR4WLwohtlOMGVbL92ejLAeKVnr Ar7SiWA7GVar6lSGBWyyGwoErveb8TaZxRiSKgjHuvciMLgy+KrlyxqZq6gNd7nP isBDMEe2NsnUawR/gfcxvvzpyHTPYPtSlEJjejdbnGlP4YGy5BT2vm3HqyAgK/iX N1iRBhx8zuH9UDNN8XiSuvuYuxAw9OfeBoh/2aGifj5dcrEP+IeyYUoAWBoXgny+ IcoitmUwYE4xLduLnIpf2b5KG8Yw1r2bKoZJVOw8+ixJAqCWR0xXONcywB56MXoE 8r9A11D6ASdRmozKjcEQH9+j6/4VuVeydCBfXQSZHIlVL3pTFZAlH0Q0JSZq4NXA Pb5YGcdYDONi3gPxNIvUn1WeqTfpgJhGveKV5PhI3NY2d+GEB3fBBuBhvlAlrwxg CPCqH4YC0sntvqMqcOooz44OfiLpB1ARGGTwtKATLNIzpS/iMsS1swW1NZEeaN19 uFZw/dY3w5uhDQ7u2Buc =4ByJ -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: 10-RC2 current wireless link aggregation not working correctly
I guarantee you that a simple interface list with ifconfig un-stucks the net on my setup, at lest in the case (master is wired, unplug ethernet, fail to wireless) I agree that it doesn't makes much sense, but no matter how unlikely it seems, it is a **fact**. I don't believe in merely doing 'ifconfig' would workaround the issue, it does not make sense, plus I have tested and it didn't work for my case (iwn+em on my laptop). I'm aware of the issue but thought it was compatibility issue with my own weirdly setup wireless AP at the time, and looks like it's not just me, but I'm not interested nor have time to fix the problem so I replied the thread and offered what I have tested as a workaround in the hope that it's useful for someone who is interested and have the ability to fix the problem. Cheers, -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJSsVEkAAoJEJW2GBstM+nswTsP/Rs0hdyXNejf2Z98GbSGns0n lsI+UmjwWUSg0h+8QzCce7/80mwEw0tZH1btoRr6I0tPKXwdUYDO2C3LPM2a/jSV hvN6aay0ppnldtsqMZcuDv1OznSGfEIt0A04/m/RUTDBYaPKY+F1iqZYNE960zes u6mbR2elpAUCHjpV3lEchnP5V1v/yLpVziGYabR4WLwohtlOMGVbL92ejLAeKVnr Ar7SiWA7GVar6lSGBWyyGwoErveb8TaZxRiSKgjHuvciMLgy+KrlyxqZq6gNd7nP isBDMEe2NsnUawR/gfcxvvzpyHTPYPtSlEJjejdbnGlP4YGy5BT2vm3HqyAgK/iX N1iRBhx8zuH9UDNN8XiSuvuYuxAw9OfeBoh/2aGifj5dcrEP+IeyYUoAWBoXgny+ IcoitmUwYE4xLduLnIpf2b5KG8Yw1r2bKoZJVOw8+ixJAqCWR0xXONcywB56MXoE 8r9A11D6ASdRmozKjcEQH9+j6/4VuVeydCBfXQSZHIlVL3pTFZAlH0Q0JSZq4NXA Pb5YGcdYDONi3gPxNIvUn1WeqTfpgJhGveKV5PhI3NY2d+GEB3fBBuBhvlAlrwxg CPCqH4YC0sntvqMqcOooz44OfiLpB1ARGGTwtKATLNIzpS/iMsS1swW1NZEeaN19 uFZw/dY3w5uhDQ7u2Buc =4ByJ -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
