ASIX AX88772B chipset / USB LAN not work
-
Hello I have a problem with the ASIX USB Ethernet 10/100 LAN Card AX88772B chipset
DHCP Client and ping works .
but no traffic is Operational .
I did research on google :
I think AX88772B a driver problem
For the full functionality checksum rx / tx hardwareideas for a bypassed this problem ?
tnx. :)
-
Which version of pfSense you are using?
pfSense 2.2.5 is based on FreeBSD 10.1 and on their (FreeBSD 10.1) hardware compatibility list
this adapter is shown as fully supported by the driver (axe4)!FreeBSD 10.1-RELEASE Hardware Notes
[i386,pc98,amd64,powerpc] The axe(4) driver supports ASIX Electronics AX88172/AX88178/AX88772/AX88772A/AX88772B/AX88760
based USB Ethernet adapters including:
AX88772B: ASIX AX88772B- Install the device
- create an Interface under interfaces (ue..)
- assign this interface
- create rules for this interface
-
Hello ,
Thank you for your return
Yes , for test I use version 2.2.5 of pfsense 32bit in VMware ESXi
VM:
RAM: 512 MB
CPU: CPU 1
Drive: 8GB
LAN: 2 x USB LAN ASIX AX88772Btopology:
ADSL Internet–--------- (WAN) Pfesense (LAN) ---------- MyPC
Both USB LAN interfaces its recognized ( ue0 LAN / WAN ue0 ) and assinged.
The pfsense DHCP Server gives me 192.168.1.101/24 an IP address on my PC interface .
I can ping the address 192.168.1.1 and anyone ip internet for example 8.8.8.8 .
but no other Traffic is passed by pfsense even the web admin does not work http://192.168.1.1/
I think this is a bug in the driver :( !!!!!!?????
-
Yes , for test I use version 2.2.5 of pfsense 32bit in VMware ESXi
I personally think it is more tended to the ESXi host that the both USB LAN adapters are not really supported.
I can ping the address 192.168.1.1 and anyone ip internet for example 8.8.8.8 .
Ok then the traffic should be also running over this LAN adapter.
I think this is a bug in the driver :( !!!!!!?????
Are this adapters supported by ESXi?
-
thank you BlueKobold
It is not the cause of almost ESXi :
The USB card is mapped directly from the ESXi on pfsense not bridge .
it is detected as ue0 / eu1 native driver pfsense.
I even repeated the same physical machine LAB with the same problem.
See screenshots.
tnx
-
Are you able to insert two real NICs or a real dual port NIC to see if this behavior exist also there?