using both wifi and wired
Forum rules
Porteus Kiosk section of the forum is unmaintained now. Its kept in a 'read only' mode for archival purposes.
Please use the kiosk contact page for directing your queries: https://porteus-kiosk.org/contact.html
Porteus Kiosk section of the forum is unmaintained now. Its kept in a 'read only' mode for archival purposes.
Please use the kiosk contact page for directing your queries: https://porteus-kiosk.org/contact.html
using both wifi and wired
Is it possible to configure the kiosk to use wired connection if available, and fallback to wifi if wired is not connected?
- francois
- Contributor
- Posts: 6435
- Joined: 28 Dec 2010, 14:25
- Distribution: xfce plank porteus nemesis
- Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.
Re: using both wifi and wired
I moved your post in the porteus kiosk edition section.
Prendre son temps, profiter de celui qui passe.
- fanthom
- Moderator Team
- Posts: 5667
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
Re: using both wifi and wired
@radu,
If you enable dhcp + wifi in the wizard then each connection will work as a fallback to the other. I'm not sure which one will be primary but i assume wired as it gets established faster.
If you enable dhcp + wifi in the wizard then each connection will work as a fallback to the other. I'm not sure which one will be primary but i assume wired as it gets established faster.
Please add [Solved] to your thread title if the solution was found.
using both wifi and wired
I have a further question about this issue.
Does "fallback" mean the wireless connection can take over only if the wired can't be *established* (eg. connect to the network and get an IP) and vice versa; or does fallback mean both connections are constantly monitored for properly working internet access and porteus automatically uses the interface with a working internet connection?
Does "fallback" mean the wireless connection can take over only if the wired can't be *established* (eg. connect to the network and get an IP) and vice versa; or does fallback mean both connections are constantly monitored for properly working internet access and porteus automatically uses the interface with a working internet connection?
- fanthom
- Moderator Team
- Posts: 5667
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
using both wifi and wired
Both connections are constantly monitored by dhcpcd and wpa_supplicant. They work on all available network interfaces so when first connection is lost then second one takes its role.
Thanks
Thanks
Please add [Solved] to your thread title if the solution was found.
using both wifi and wired
Sorry for asking again, but I just want to be sure:
Are the connections monitored for (local) connectivity only or for actual availability of internet access.
With connectivity only I mean:
Wired: Checking for having an ethernet cable plugged in and an IP address of the local network.
Wireless: Being connected to the access point and having an IP address.
With internet access I mean more than just (local) connectivity, but in particular checking if "the internet works".
Are the connections monitored for (local) connectivity only or for actual availability of internet access.
With connectivity only I mean:
Wired: Checking for having an ethernet cable plugged in and an IP address of the local network.
Wireless: Being connected to the access point and having an IP address.
With internet access I mean more than just (local) connectivity, but in particular checking if "the internet works".
- fanthom
- Moderator Team
- Posts: 5667
- Joined: 28 Dec 2010, 02:42
- Distribution: Porteus Kiosk
- Location: Poland
- Contact:
using both wifi and wired
This is local connectivity test.
Internet test would have to be handled by additional system customization. If pinging kernel.org does not work then switch wireless to wired (kill dhcpcd/wpa_supplicant on wifi interface).
Thanks
Internet test would have to be handled by additional system customization. If pinging kernel.org does not work then switch wireless to wired (kill dhcpcd/wpa_supplicant on wifi interface).
Thanks
Please add [Solved] to your thread title if the solution was found.