PfSense 2.4.4-RELEASE-p3 attempting to USB tether
-
@ginjaninja said in PfSense 2.4.4-RELEASE-p3 attempting to USB tether:
I have edited the /boot/loader.conf file to include if_urndis
You should put that in /boot/loader.conf.local to avoid it being overwritten. That isn't going to help it recognise the phone though.
Anything logged when you connect the phone? It is trying and failing to use the driver?Steve
-
@stephenw10 Thanks for the reply. All dmesg shows is disconnect and connection of the phone. Nothing else error wise unless I should look elsewhere?
-
Hmm, nope. It seems like urndis just doesn't see it as an interesting device to attach to. Which is surprising since it clear has an RNDIS Ethernet interface.
Not sure there's much we can do there though. Does it have more than one config index you could try?Steve
-
@stephenw10 thanks again. That sticks it would have been great to use this as a failover. No other config indexes available, but there are Bulk labeled Ethernet interface 1. But no index tied to it.
Is there a supported list of working Android devices or perhaps the version of if_rndis.ko is wrong. I pulled it from the 11.2 64bit freebsd release. I see it running...
-
That's the correct version for 2.4.4p3. You could try a 2.5 snapshot and use the module from FreeBSD 12.
Steve
-
Thanks i'll give it a shot.
-
On the hardware i'm installing this on, I consistently get a fatal tray 12 page fault during USB boot. I've tried all IMG and ISO options apart from serial.. I may have to pull back the attempts for now. Unless you have other options.
-
You could install 2.4.4p3 and upgrade if it won't boot the 2.5 installer.
You could try forcing it to boot uefi or not uefi depending what it's booting as now.
Steve
-
@stephenw10 thanks for the suggestion. The hardware I'm using (sophos UTM 110/120) firewall doesn't like PFS 2.5 period. After update I still get the same issue. Thanks, I'll attempt this on my Proxmox virtual environment as well. That's where the production PFS VM sits currently.
-
Hmm, curious. I'm not aware of any hardware that won't run 2.5.... yet.
Do you have the backtrace or console output leading up to the panic?
