Re: [arch-general] systemd-networkd and netctl with multiple interfaces
On Thu, Nov 12, 2015 at 07:52:20PM +0100, Bennett Piater wrote: > > I mostly just use LAN when I need to download a lot of stuff at home, > because WIFI is much slower even at 54 Mb/s, especially since my home > network is 1 Gbps. So I could just turn WIFI off in those cases, that > would be an acceptable situation. You probably don't want to turn off the wifi physically because you will also need to tell daemons like wpa_supplicant to quit gracefully (and then restart when the card is turned back on). > However, I want to understand all of this as fully as possible. > So, yes, I would appreciate your profiles - but please take your time > digging them out :) I'd say, the cleanest option is to keep wlan0 interface up and have wpa_supplicant running on it all the time, but configure it a slave to ethernet in the bonding. So, whenever you plug a cable, the kernel will automatically send all traffic through eth. Unplug it, and the traffic will flow over wifi. And your applications shouldn't even notice that. The setup is simple: create a netctl profile, like $ cat bonding0 Description="Bond interface for external NICs" Interface=bond0 Connection=bond BindsToInterfaces=(eth0 wlan0) IP=no Then, enable wpa_supplicant-nl80211@wlan0.service after netctl@bonding0.service, and finally configure IP, firewall, etc using the new bond0 interface. This IP (and routing) will stay stable in between switches between wired and wireless networks. The above ordering of netctl and wpa_supplicant is the only trick here... HTH, -- Leonid Isaev GPG fingerprints: DA92 034D B4A8 EC51 7EA6 20DF 9291 EE8A 043C B8C4 C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
Re: [arch-general] systemd-networkd and netctl with multiple interfaces
> Well, it depends on whether wlan0 and eth0 are on different networks. If > they are, then the answer is yes, and you are screwed. > > If both interfaces get the same ip, then you can maintain persistent > connection. For example, let's assume that you constantly switch between > different interfaces (wlan0 <--> eth0), when you move between buildings on > campus. > > In the latter case, you can bond wlan0 and eth0 (bond0 := wlan0 + eth0) and > use > bond0 in all your networking scripts (but still, wpa_supplicant runs on > physical wlan0). In this case, nothing but the kernel cares what physical > interface carries the traffic. Last time I checked about a year ago, > systemd-networkd had some obscure bug in this situation, so I'm using netctl > that works perfectly. If you need, I can dig out the relevant profiles. I mostly just use LAN when I need to download a lot of stuff at home, because WIFI is much slower even at 54 Mb/s, especially since my home network is 1 Gbps. So I could just turn WIFI off in those cases, that would be an acceptable situation. However, I want to understand all of this as fully as possible. So, yes, I would appreciate your profiles - but please take your time digging them out :) Cheers, Bennett -- GPG fingerprint: 871F 1047 7DB3 DDED 5FC4 47B2 26C7 E577 EF96 7808 signature.asc Description: OpenPGP digital signature
Re: [arch-general] systemd-networkd and netctl with multiple interfaces
On Thu, Nov 12, 2015 at 12:30:36PM +0100, Bennett Piater wrote: > > Say you start out on wifi, and open an ssh connection. Then you plug in > > ethernet. The ssh session will remain on the wifi route until it is > > closed. There's no way* to make an existing connection "jump ship" from > > one route to another. If you were to disable the wifi connection as soon > > as the ethernet connection, your ssh session would die. > > Thanks a lot, that is both new and helpful indeed. > > So does this mean that new connections will use the new network, while > old connections retain theirs? Well, it depends on whether wlan0 and eth0 are on different networks. If they are, then the answer is yes, and you are screwed. If both interfaces get the same ip, then you can maintain persistent connection. For example, let's assume that you constantly switch between different interfaces (wlan0 <--> eth0), when you move between buildings on campus. In the latter case, you can bond wlan0 and eth0 (bond0 := wlan0 + eth0) and use bond0 in all your networking scripts (but still, wpa_supplicant runs on physical wlan0). In this case, nothing but the kernel cares what physical interface carries the traffic. Last time I checked about a year ago, systemd-networkd had some obscure bug in this situation, so I'm using netctl that works perfectly. If you need, I can dig out the relevant profiles. HTH, -- Leonid Isaev GPG fingerprints: DA92 034D B4A8 EC51 7EA6 20DF 9291 EE8A 043C B8C4 C0DF 20D0 C075 C3F1 E1BE 775A A7AE F6CB 164B 5A6D
Re: [arch-general] QT applicacion dies on plain fluxbox, but not on fluxbox on top of LXDE
> On Wed, Nov 11, 2015 at 11:45 AM, Javier Vasquez > wrote: >> On Wed, Nov 11, 2015 at 10:21 AM, Javier Vasquez >> wrote: >> ... OK, thanks to the fluxbox users folks, the problem has been identified. There's a bug on "hpmyroom" which makes it crash when DESKTOP_SESSION is undefined, which is the case when one doesn't use a DE. By setting it to any string, "hpmyroom" doesn't crash anymore. The bug has been reported already, and I have the work around in place. Thanks, -- Javier
Re: [arch-general] systemd-networkd and netctl with multiple interfaces
> Say you start out on wifi, and open an ssh connection. Then you plug in > ethernet. The ssh session will remain on the wifi route until it is > closed. There's no way* to make an existing connection "jump ship" from > one route to another. If you were to disable the wifi connection as soon > as the ethernet connection, your ssh session would die. Thanks a lot, that is both new and helpful indeed. So does this mean that new connections will use the new network, while old connections retain theirs? Cheers, Bennett -- GPG fingerprint: 871F 1047 7DB3 DDED 5FC4 47B2 26C7 E577 EF96 7808 signature.asc Description: OpenPGP digital signature
