1 |
On Tuesday, 5 April 2022 08:46:52 BST Neil Bothwick wrote: |
2 |
> On Tue, 5 Apr 2022 11:16:10 +0800, William Kenworthy wrote: |
3 |
> > On 5/4/22 07:09, Michael wrote: |
4 |
> > > On Monday, 4 April 2022 16:12:53 BST Jack wrote: |
5 |
> > >> On 4/4/22 01:31, William Kenworthy wrote: |
6 |
> > >>> Is there a way force openrc and wpa_supplicant to map a particular |
7 |
> > >>> access point to an interface or fail? |
8 |
> > >>> |
9 |
> > >>> I have two AP's (each on a different ssid) to connect to so have two |
10 |
> > >>> wifi interfaces - unfortunately they are not equal so I want wlan0 |
11 |
> > >>> to connect to only one particular AP, and wlan1 to the other ... |
12 |
> > >>> reliably! I can manually force it to connect but invariably at the |
13 |
> > >>> first glitch they both end up connected to the same AP (usually the |
14 |
> > >>> strongest which is often not what I want :( |
15 |
> > >>> |
16 |
> > >>> BillK |
17 |
> > >> |
18 |
> > >> I don't know about wpa-supplicant, but I'm using open-rc and KDE, and |
19 |
> > >> KDE's systemsettings Network / Connections screen lets you restrict a |
20 |
> > >> network connection so a specific device. Not sure if this helps you |
21 |
> > >> any, but it would indicate that what you want is possible. |
22 |
> > >> |
23 |
> > >> Jack |
24 |
> > > |
25 |
> > > Look at the example provided in: |
26 |
> > > |
27 |
> > > /usr/share/doc/netifrc-0.7.3/net.example.bz2 |
28 |
> > > |
29 |
> > > You can set a different ssid for each wireless NIC. The |
30 |
> > > wpa_supplicant can be set with credentials for the two APs only. |
31 |
> > |
32 |
> > Unfortunately, this does not work as I want ...wpa_supplicant's |
33 |
> > behaviour makes sense in that it provides a fallback if the allocated |
34 |
> > access point cant connect ... it will pick the next available one |
35 |
> > (seemingly based on signal strength) if it is in its conf file (and |
36 |
> > does not care that its another ssid) - so it does not fail. As only |
37 |
> > one of the two networks has internet access the device often ends up |
38 |
> > not being able to be connected to (its headless so that's a problem!). |
39 |
> > |
40 |
> > I have fallen back to openrc for the main connection and will do the |
41 |
> > other manually - it would be nice to have everything properly |
42 |
> > controlled but its not working for me. |
43 |
> |
44 |
> Could you run two instances of wpa_suplicant, each listening on a |
45 |
> different interface and using a config with only the AP for that |
46 |
> interface? |
47 |
|
48 |
As I recall wpa_cli can be launched by specifying a particular interface. |
49 |
Therefore two instances of wpa_cli launched by a script should be possible. |
50 |
|
51 |
However, isn't the purpose of /etc/conf.d/net to specify how individual |
52 |
interfaces are configured? I still think - but have not tried it - each |
53 |
wireless NIC can be configured via this file to use a particular access point/ |
54 |
channel and not go scanning for others, while the wpa_supplicant can be left |
55 |
to deal with the authentication mechanism after each NIC has found its |
56 |
specified ESSID. |
57 |
|
58 |
The section in the netifrc example file which starts as follows, merits |
59 |
reading: |
60 |
|
61 |
############################################### |
62 |
# SETTINGS |
63 |
# Hard code an SSID to an interface - leave this unset if you wish the driver |
64 |
# to scan for available Access Points . . . |
65 |
|
66 |
Something like this ought to work: |
67 |
|
68 |
essid_wlan0="foo" |
69 |
|
70 |
essid_wlan1="bar" |