Custom Query (39 matches)

The current code base sometimes does not correctly configure interfaces when switching profiles. It was observed that xwlan creates numerous interfaces (lan9, lan8, lan7....) instead of configuring the correct ones (lan0, lan1 in my case).

As switching profiles usually works here, I think this could be a timing issue. Usually one interface is switched off and afterwards the other interface is configured. But once I saw that both interfaces lan0 and lan1 were configured at the same time for a short period.

There are at least 2 problems with xwlan and DHCP. As OS/2 - eCS dhcp client has problems we can not solve the goal is switching to ISC open source dhcpclient.

For traceability the current DHCP problems are documented in this ticket. 1) eCS client does not work with 2 DHCP servers. IIRC client sends DHCPREQUEST with wrong server data. 2) eCS client seems to configure routes before 'old' interface is deleted which leads to wrong routing in stack. This may be related to #3.

There is no info to the user if wpa supplicant is available/working. When trying to connect to wpa protected network it simply does not work. No info that wpa_supplicant.exe is missing.

Would be fine if a popup or fly over message warns about.