OPNsense Forum

After installation it runs auto-configure for LAN and WAN. This is messing with my settings because WAN is now a 4G connection via USB.

How do you disable this after installation?

/ Johan

Hi Johan,

My idea, just finish the setup with wan on one of the 3 nic. After you finished the wizard, you can reassign whatever you want.

Uwe

Hi Johan,

There is no installation on Nano. Skip the wizard if you don't agree with its configuration by navigating away from the page. :)


Cheers,
Franco

PS: And/or make sure you have a console attached on first boot to make sure it doesn't configure LAN/WAN by default.

Sorry,

I was talking about the "wizard" / configuration on the console screen (with serial cable and e.g. PuTTY).

Uwe

Exactly what I'm doing. I reassign the interface bit as soon as the unit restart it runs a new auto-configuration and sets WAN to the first free nic.

The the USB NIC driver is not available during early boot, hence it mismatches your configuration and forces the defaults.

How do you load the driver during boot?


Cheers,
Franco

I have no idea at all. :P. The USB modem works out of the box.

Okay, well, we just need the driver name, then we can make a /boot/loader.conf entry. What's the WiFi driver name in the GUI?

Alternatively a dump of this will help to spot it from the console when it's up and running:

# ifconfig -l

Hmmmm I think it's because it also have some storage function.
It's a 4G modem, MF831 from ZTE.

It takes some time for the storage function to be done with so opnsense can't find the interface in time (I think).

The ifconfig -l doesn't give much:

vr0 vr1 vr2 pflog0 pfsync0 enc0 lo0 ue0

ifconfig -L on the other hand gives some more:

vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8280b<RXCSUM,TXCSUM,VLAN_MTU,WOL_UCAST,WOL_MAGIC,LINKSTATE>
        ether 00:0d:b9:38:ea:28
        inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
        inet6 fe80::1:1%vr0 prefixlen 64 scopeid 0x1
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (none)
        status: no carrier
vr1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8280b<RXCSUM,TXCSUM,VLAN_MTU,WOL_UCAST,WOL_MAGIC,LINKSTATE>
        ether 00:0d:b9:38:ea:29
        inet6 fe80::20d:b9ff:fe38:ea29%vr1 prefixlen 64 scopeid 0x2
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (none)
        status: no carrier
vr2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8280b<RXCSUM,TXCSUM,VLAN_MTU,WOL_UCAST,WOL_MAGIC,LINKSTATE>
        ether 00:0d:b9:38:ea:2a
        inet6 fe80::20d:b9ff:fe38:ea2a%vr2 prefixlen 64 scopeid 0x3
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet autoselect (none)
        status: no carrier
pflog0: flags=100<PROMISC> metric 0 mtu 33184
pfsync0: flags=0<> metric 0 mtu 1500
        syncpeer: 0.0.0.0 maxupd: 128 defer: off
enc0: flags=0<> metric 0 mtu 1536
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet 127.0.0.1 netmask 0xff000000
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x7
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
ue0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 36:4b:50:b7:ef:da
        inet6 fe80::344b:50ff:feb7:efda%ue0 prefixlen 64 scopeid 0x8
        inet 192.168.0.153 netmask 0xffffff00 broadcast 192.168.0.255
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

Would really appreciate if this could be fixed :D

/ Johan

How long does it take for the modem to become ready?

You could try a simple boot delay:

# mkdir /usr/local/etc/rc.syshook.d
# echo "#!/bin/sh" > /usr/local/etc/rc.syshook.d/4g-delay.early
# echo "sleep 20" >> /usr/local/etc/rc.syshook.d/4g-delay.early
# chmod 755 /usr/local/etc/rc.syshook.d/4g-delay.early

And reboot. "20" is only a guess, it's hard to "correctly" "wait" for the modem to become ready.

Quote from: franco on September 18, 2016, 11:28:10 PM

# echo "sleep 20" > /usr/local/etc/rc.syshook.d/4g-delay.early

# echo "sleep 20" >> /usr ...

Fixed, thanks!