WTware RDP client

When creating a bootable ISO using WTware Center in version 6.2.54, we selected the option "Work over Wi-Fi. Wi-Fi configuration is performed from terminal" in the wizard.

In previous versions, this option correctly configured the terminal to boot with Wi-Fi enabled. However, in version 6.2.54, the ...

This works for me (in a Windows environment):

You can change the DNS settings in your DHCP scope to
- Enable DNS dynamic updates
-- Dynamically update DNS records only if requested
- Discard A and PTR records when lease is deleted
- Dynamically update DNS records for DHCP clients that do not ...

I'd like to place a feature request to disable TLS 1.0 and TLS 1.1 on the embedded webserver, either by default or by a configuration setting.

It works good now, thanks!

Unfortunately that also doesn't work

aka wrote: Thu Apr 22, 2021 7:07 pmShow me FULL all.log

I want to, but then I have to take a lot of photos.
It goes to CLI after the error message, web interface does not work.
I used less /tmp/all.log to view the log file.

Additional information from all.log:

[initrd] bootWay.cpp (132): -- ERROR -- Failed to mount /bootmedia
[initrd] bootWay.cpp (198): -- ERROR -- INTERAL ERROR. Please, contact WTware tech support.
[initrd] bootWay.cpp (251): -- ERROR -- INTERAL ERROR. Please, contact WTware tech support.

When I try to install WTware 6.0.46 from USB with UEFI, the following error is displayed:"

ERROR: Failed to mount boot media. Please, send the photo
of this screen to WTware techsupport and describe:
where do you boot terminal from and what makes
you think, that terminal can boot from it.

It ...

Hello,

I have WTware UEFI installed.
When I try to update WTware UEFI to the latest version and reboot, I always get the following error:


photo


In the full log after reboot there is this information:
[ initrd] [ 3.510102] [FILE CACHE] Take 'packages/uefi-xnet' from cache.
[ initrd] [ 3 ...

Yes please return to wl driver.
B43 solves one issue, but creates many other issues.

Add to wpa_supplicant command line:

-f /tmp/wpa_supplicant.out

So we can compare wpa_supplicant output.


This is the output
Successfully initialized wpa_supplicant
wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
wlan0: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN ...

It there such line ?


Yes, indeed it says
[ 14.582103] b43 ssb0:0: firmware: direct-loading firmware b43/ucode16_mimo.fw
[ 14.586401] b43 ssb0:0: firmware: direct-loading firmware b43/n0initvals16.fw
[ 14.587283] b43 ssb0:0: firmware: direct-loading firmware b43/n0bsinitvals16.fw
[ 16.262377 ...

After some testing, it seems that the Wi-Fi connection disconnects every minute or so.
The following happens in the log:
[ WPA] [ 263.881133] l2_packet_send - sendto: No buffer space available
[ KERNEL] [ 263.884444] eth0: deauthenticating from bb:bb:bb:bb:bb:bb by local choice (Reason: 1 ...

Yes! It works!

Broadcom is detected and B43 is loaded:
[ initrd] [ 11.163418] [WiFi] Do not load wl for 14e4:432b.
[ initrd] [ 11.194666] Found broadcom chip.
[ initrd] [ 11.194777] modprobe b43.
[ KERNEL] [ 11.228370] ssb: Found chip with id 0x4322, rev 0x01 and package 0x0A
[ KERNEL] [ 11.341015 ...

Ah yes you are correct.
I needed to install debian again for lsmod output and it says that the b43 driver uses a non-free firmware.

Attached you can find the lsmod output.