Help getting asix ax88772b to work
-
It should load at boot and replace the in-kernel module. That's done often with pci NICs (em, sk, msk etc).
Steve
Hmm really? Ok let me try that
-
Yep, done it many times for msk. Never tried for a USB device but I can't see why that would be any different. USB device list not updated perhaps?
Interesting, I hadn't realised that the module you are working on in the other thread is differently named: if_axe vs if_axge. Is it a completely new module then? With no support for earlier devices?
Steve
-
Yep, done it many times for msk. Never tried for a USB device but I can't see why that would be any different. USB device list not updated perhaps?
What process did you use. I get "module axe already present!"
Interesting, I hadn't realised that the module you are working on in the other thread is differently named: if_axe vs if_axge. Is it a completely new module then? With no support for earlier devices?
Steve
if_axge is just for the 178A and 179 which I backported from november source.
if_axe is for the other axis devices. I added a revision into the code 772b_1 that was in new source and recompiled
-
You have to load it at boot using the /boot/loader.conf.local file. Create that file if it doesn't exist. Add the line:
if_axe_load="yes"
Steve
-
You have to load it at boot using the /boot/loader.conf.local file. Create that file if it doesn't exist. Add the line:
if_axe_load="yes"
Steve
I get "module axe already present" in my dmesg.boot. I don't think it overrides.
-
Hmm, maybe usb device drivers are different then.
Steve
-
Hmm, maybe usb device drivers are different then.
Steve
The axe driver is compiled into the kernel there is no way around unless we recompile a kernel.
-
Apparently not. :( I wonder what's actually different about the USB drivers that prevents it. The PCI drivers can certainly be loaded at boot to displace the in kernel driver.
Steve
-
I want to share my experience with two different usb to lan cards both claiming to have chipset (AX88772 a/b).
I managed to install (simple plug&play) only one of the two usb to ethernet adapters (0B95 & 772B), taking name ue0 under pfsense.(the other adapter never worked)
but huge but.
I set the ue0 as lan card and give it the ip 192.168.1.1
and i set my wan card as 192.168.2.2 with gateway my router (192.168.2.1)i can ping from my client pc (192.168.1.2) the lan interface & also i can ping pfsense.org
i can ping from my pfsense box the address pfsense.orgbut again huge but.
i never get the packages of pfsense to load (stating that it cant contact pfsense.org, and i should change DNS)
i never get to load webpages in my browser.i would appreciate any help given
edit0: usb to ethernet adapter is having a weird mac 00:00:00:00:00:01
edit1: i updated to 2.2, now usb to ethernet doesnt even get recognized as ue0
edit2: i get this errorskernel: ugen1.2: <vendor 0x0b95=""> at usbus1 (disconnected)</vendor>
and ```
[ There were error(s) loading the rules: pfctl: DIOCADDRULE: Operation not supported by device - The line in question reads [0]: ] -
That is a different problem. The usb ethernet card is clearly working correctly since you're able to ping it from the client machine. One possible cause might be: https://doc.pfsense.org/index.php/Controlling_IPv6_or_IPv4_Preference
You should start another thread to discuss that.2.2 is still 'highly experimental'. Many things don't work correctly at this point. You should start a thread in the 2.2 subforum to report this failure if it hasn't already been reported.
Steve
-
That is a different problem. The usb ethernet card is clearly working correctly since you're able to ping it from the client machine.
Stevei am able to ping the interface but not access the web configuration (if usb to ethernet is used as lan interface)
-
If it is responding to pings (or any IP traffic) then the driver is loading correctly and talking to the card.
If you aren't able to access the webgui check your firewall rules on the interface. Check the firewall logs to see what traffic is being blocked. If it's not that it's probably a routing problem, check the client is receiving the correct IP info.Steve
-
If you have a look I got AX88179 working on 2.1 with some kernel modules I backported.
The other ones you will need to recompile kernel at least with the modules deselected as far as I understand.