Hi Beniamino,
thx for your quick response, I'll try to pass these NM parameters, as you
suggested and see if it works. Btw. they do differ than these from
wpa_supplicant, so maybe there is the problem. I will keep you inform.
Best regards
Piotr
Od: Beniamino
I'll try to explain.
I have three interfaces. I'll call them eth0, eth1 and wlan0.
Normally, we create a bridge, br0, and enslave eth0 and eth1. We assign an
IP to br0 (DHCP) and it can access devices connected to eth0 and eth1.
Those devices also can access each other, too. A DHCP server is
On Tue, Jan 26, 2021 at 01:58:53PM +, Vallevand, Mark K wrote:
> Actually, I am using a bridge. It is currently between two NICs.
> We removed the 'upstream' NIC from the bridge and then enabled
> NetworkManager interface sharing on the bridge.
> NetworkManager selects the Wi-Fi connection
On Tue, 2021-01-26 at 15:07 +0100, IB Development Team via
networkmanager-list wrote:
> W dniu 26.01.2021 o 13:49, Beniamino Galvani pisze:
>
> > Please verify if you have more than one connection for the SSID.
>
> Only one connection is defined for this SSID and every file
>
W dniu 26.01.2021 o 13:49, Beniamino Galvani pisze:
Please verify if you have more than one connection for the SSID.
Only one connection is defined for this SSID and every file
/etc/NetworkManager/system-connections has ist unique UUID.
After manually changing connection files, NM must
Actually, I am using a bridge. It is currently between two NICs.
We removed the 'upstream' NIC from the bridge and then enabled
NetworkManager interface sharing on the bridge.
NetworkManager selects the Wi-Fi connection and creates all the plumbing and
it works.
There are some issues.
The first
On Sun, Jan 17, 2021 at 07:55:53PM +, Vallevand, Mark K via
networkmanager-list wrote:
> I'd like to use the upstream DHCP server when using network sharing.
>
> Is this possible?
No, connection sharing starts its own DHCP server on the "downstream"
interface (the one with
On Sun, Jan 24, 2021 at 02:32:01PM +, Piotr Lobacz wrote:
> i am struggling for a week to connect via NM together with
> wpa_supplicant using systemd on buildroot. I have compiled
> wpa_supplicant with dbus support. Before that i tried to use only
> NM, but the nmcli was saying that the wlan0
On Tue, Jan 26, 2021 at 01:23:46PM +0100, IB Development Team wrote:
>
> output I can see one conn try with subject matching failure and then next
> attempt that succeeded (no conn config file changed between):
> Jan 26 12:28:34 mycomp wpa_supplicant[937]: wlan0: Trying to associate with
>
W dniu 26.01.2021 o 11:23, Beniamino Galvani pisze:
with NM 1.14, just I tried to connect to a EAP-TLS Wi-Fi network with
a wrong '802-1x.subject-match' and it failed complaining about the
mismatch. I don't have the setup for 'altsubject-matches' and
'domain-suffix-match', I'll try to prepare
On Mon, Jan 25, 2021 at 09:27:55PM +0100, IB Development Team via
networkmanager-list wrote:
> network-manager does not verify server certificate name on EAP-TLS WIFI
> connections:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981057
>
> Please verify and consider fixing.
Hi,
with NM
network-manager does not verify server certificate name on EAP-TLS WIFI
connections:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981057
Please verify and consider fixing.
--
Regards,
Paweł Bogusławski
IB Development Team
E: d...@ib.pl
___
12 matches
Mail list logo
