WTware Technical Support

hi
I also have this problem like you

ap_scan=0
network={
              key_mgmt=IEEE8021X
              eap=MD5
              identity="login"
              password="password"
              }

Hello, we used dhcp with guest vlan.
We can work with default suplicant.
[code]ap_scan=0
network={
key_mgmt=IEEE8021X
eap=MD5
identity="login"
password="password"
}[/code]

Now is the question, why i can run /sbin/wpa_supplicant -B -c /etc/wpa_supplicant.conf -i eth0, because a only have accces to shell before Wtware booting ???

ctrl_interface=/var/run/wpa_supplicant
network={
    ssid="MYSSID"
    psk="passphrase"
}

/sbin/wpa_supplicant -B -c /etc/wpa_supplicant.conf -i eth0

Sorry for a delay.

As far as I understand, we should prepare wpa_supplicant.conf and run wpa_supplicant as we do for Wi-Fi, but on Ethernet interface. Before asking DHCP or apply static IP to interface. Right?

Should we generate default wpa_supplicant.conf or always require user-provided wpa_supplicant.conf ? If we should generate default, please write it to me.

For Wi-Fi we use such minimal default wpa_supplicant.conf if user doesn't provide another :

[code]ctrl_interface=/var/run/wpa_supplicant
network={
ssid="MYSSID"
psk="passphrase"
}[/code]

With wpa_supplicant.conf prepared, we should run:

[code]/sbin/wpa_supplicant -B -c /etc/wpa_supplicant.conf -i eth0[/code]

Right?

Sorry, too busy now. I'll answer here after we upload next version.

Hi, can you provider the way to do?

Yep, i´m familiar with linux, let´s go!

We can make it if someone familiar with wired 802.1x in regular linux tells us what should we do.

Don´t have a plan to support in future???

WTware does not support 802.1x now.

Please provide one way use Wtware in environments with 802.1x in wired network