-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update _index.md #8
base: main
Are you sure you want to change the base?
Conversation
comitup issue with double wlan
``` | ||
enable_appliance_mode: false | ||
primary_wifi_device: wlan1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you sure wlan1 is correct here? It means "use wlan1 for hotspot"
In my setup (external usb card for extra coverage) I'm setting primary_wifi_device: wlan0
, so we get hotspot on builtin card (that is less prone to issues) and main connectivity on external
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, it is correct , when you use wlan1 then comitup will use wlan0, broadcast openmower-xx and you can just use it., after that you get some nginx error.
with enable_appliance_mode you disable wlan0 for wifi broadcast.
so this is only an issue when you have 2 wifi devices.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this now verified correct? can I merge?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I, frankly, don't know. In my setup I have predictive interface names enabled, udev mapping internal interface to wlan1 and comitup.conf just contains primary_wifi_device: wlan0
. Meanwhile interfaces work correctly:
wlx00c0caae7845 IEEE 802.11bgn ESSID:"*******" Nickname:"<WIFI@REALTEK>"
Mode:Managed Frequency:2.452 GHz Access Point: 0A:55:31:********
Bit Rate:150 Mb/s Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=55/100 Signal level=-62 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
wlan1 IEEE 802.11 Mode:Master Tx-Power=31 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
Without additional settings power management is off on external and internal is switched off.
I would create some badge, like "People tried that with success" that would mean that it's not official verified solution but something people can experiment with.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it is by design when you have an external wifi device davesteele/comitup#21
wlan0 stays up with comitup ip and broadcast wifi. if you connect you will get some nginx error.
on the openmower OS comitup.conf it also have now a reference to these 2 params
I'd say we move that to contrib section. because there would be additional issue with cards fighting for |
comitup issue with double wlan