genmac reports lan3 when fxwrap is installed

[Yuri Dario]

When fxwrap driver from Injoy Firewall is installed on genmac wifi driver, genmac reports wrong interface number, e.g. lan3 instead of lan1. genmac link.exe already shows the error, so I think it is a genmac issue.

Until genmac gets fixed, a manual checkbox could be added to override interface number.

[andib]

I tried to reproduce here but till now without success. I've wired interface lan0 controlled by Intel Pro/1000 driver and wireless lan1 controlled by Genmac. After installing Injoy Firewall 4.1 and binding fxwrap.sys to lan0 Genmacs link.exe still reports correct 'Lan-Number : lan1' for the wireless interface.

AFAIR you do have only one interface driven by genmac, correct? Then it should be lan0.

Did you configure it with tcpcfg2 or let you configure it completely by xwlan?

Will you post your \mptn\bin\setup.cmd please. Think there should be no ifconfig statement there expect for lo.

[andib]

Okay can reproduce now. In my case genmac reports lan3 instead lan2.

What puzzles me is wpa_supplicant needs lan3 to work but dhclient lan2. If I implement a global override interface number setting wpa_supplicant does not work anymore. Although wpa_supplicant and dhclient are both ported apps I do not understand why the supplicant needs a different number than dhclient.

Of course I can hack in a override for dhclient only. But if wpa_supplicant works with the number genmac reports why the hell does dhclient needs a different one?

Btw. xwlan still has some code for handling fxwrap (and vswitch).

[andib]

On my Thinkpad

• lan0 is Intel wired lan
• lan1 is wireless handled by Genmac

When I install Injoy fxwrap on both interfaces it still works.

• lan0 still is Intel wired lan of course
• but wireless is now lan2, Genmac\bin\link.exe says Lan-Number: lan2

Now wpa_supplicant uses lan2 and can connect AND dhclient also uses lan2 and get's an IP. Wonder why?

But I can not start Injoy gateway.exe as every network action would take ages then. But without gateway it simply works.

It does not matter if I add a alias IP address to lan0. The conflicting one is deleted by xwlan as expected and the alias still runs fine. So I've lan0 and lan2 running without any lan1.

[andib]

Yuri, which WLAN device do you use?

My notebook has Intel 2200.

My main computer has Atheros 168C:0013 on lan3 and this one does not work.

One difference I noticed is the Intel device is RUNNING after ifconfig lan2 0.0.0.0 while the Atheros does not set the RUNNING flag.

Maybe that's the reason why dhclient aborts with my Atheros but not with the Intel.

[andib]

Another observation - adding vswitch (VirtualPC) driver to wireless Intel 2200 beside fxwrap now Thinkpad do not work with current XWLAN too. Now wireless lan does not have lan2 anymore but lan3 (same as with my main system).

But when I attach vswitch to the wired interface instead the wireless it works again (wireless uses lan2)

From this observation I think problem only occurs when both fxwrap and vswitch are attached to the wireless interface. At least this is what I can see here.

Have to wait what Yuri has to say about this. Maybe he posts his setup.cmd and protocol.ini.

[andib]

New option to manually override lan interface for dhclient was added. Works as expected regarding email feedback.