Topics

1

24.7 Production Series / 24 7.4: 4G modem (PPP) connection broken

« on: September 13, 2024, 08:16:03 am »

After upgrading to 24.7.4 my 4G modem (PPP) isn't working anymore.
In the logs I can see the following (descending):

Code: [Select]

[...]
Informational ppp [opt10] IPCP: parameter negotiation failed
Informational ppp [opt10] IFACE: IfaceChangeAddr() error, closing IPCP
Informational ppp [opt10] IFACE: Adding IPv4 address to ppp0 failed: Destination address required
Informational ppp [opt10] 77.1xx.xxx.xxx -> 0.0.0.0
Informational ppp [opt10] IPCP: LayerUp
Informational ppp [opt10] IPCP: state change Ack-Sent --> Opened
[...]Any idea how to fix this?
Thanks!

2

24.1 Legacy Series / WebDAV Config Backup Plugin & SFTP Config Backup Plugin

« on: June 16, 2024, 11:32:02 am »

I did a rewrite of the Nextcloud backup plugin to support any WebDAV server. For anyone interested, here is the code:
https://gist.github.com/cretl/c0cf801b45020df77e100a6a3e9d447c

This plugin is tested with SFTPGo WebDAV server and Hetzner Storage Box.
Works for me

I also created a SFTP Backup Plugin:
https://gist.github.com/cretl/9399900b4e623de4fcaab76592508ed0

3

20.1 Legacy Series / DHCPv4 Dynamic DNS (bind9): does it really work?

« on: June 14, 2020, 09:55:01 pm »

Hi,

I tried to set up a DHCPv4 server with Dynamic DNS support (bind9 server included as optional package).
I can't make it work since I ran into several issues:

The rndc-key generated by bind9 is a hmac-sha256; the DHCP Server only allows hmac-sha512 (see: https://github.com/opnsense/core/issues/4136).
Error message: security: error: client @0x44c22e2cf68 127.0.0.1#54103: request has invalid signature: TSIG rndc-key: tsig verify failure (BADKEY)

After the workaround it seems that updating the zone files is not allowed because of missing allow-update { key rndc-key; }; in the named.conf.
Error message: update-security: info: client @0x4613802c168 192.168.145.2#54889/key rndc-key: update '[domain]/IN' denied

After manually adding (which is removed by any config change) it seems that there are permission errors since bind9 can't create a journal file in /usr/local/etc/namedb/master since it is owned by root:wheel.
Error message: general: error: /usr/local/etc/namedb/master/[DOMAIN].db.jnl: create: permission denied

After manually changing the owner to bind:wheel it still doesn't seem to work despite no errors in the logs.
When trying to query the added dynamic host the server doesn't respond the IP address.

4

17.1 Legacy Series / Can't get Huawei ME909s-120 working

« on: April 10, 2017, 10:33:27 pm »

Hi,

I have a APU apu3a4 with OPNsense 17.1.4 installed. I now bought a Huawei ME909s-120 and try to get it working. I installed it in correct mPCIe slot according to the APU manual. The devices gets detected as: "ugen2.3: <HUAWEI Mobile V7R11 Huawei Technologies Co., Ltd.> at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (2mA)".
I can change config by comitting "usbconfig -d 2.3 set_config 1" (setting to HiLink mode). But the modem doesn't appear in /dev. The HiLink mode doesnt work either (doesnt get DHCP IP, when I set static IP I cant ping 192.168.8.1, which is the standard HiLink gateway address).
In dmesg log the modem produces only one line: "ugen2.3: <Huawei Technologies Co., Ltd.> at usbus2"

ls /dev output:

Code: [Select]

acpi            apmctl          ctty            cuau1.lock      full            kbd0            mem             pass0           sndstat         ttyu0           ufssuspend      ugen2.3
ada0            audit           cuau0           devctl          geom.ctl        kbdmux0         midistat        pci             speaker         ttyu0.init      ugen0.1         urandom
ada0p1          auditpipe       cuau0.init      devctl2         gpt             klog            msdosfs         pf              stderr          ttyu0.lock      ugen1.1         usb
ada0p2          bpf             cuau0.lock      devstat         gptid           kmem            netmap          pts             stdin           ttyu1           ugen1.2         usbctl
ada0p3          bpf0            cuau1           fd              hpet0           led             nfslock         random          stdout          ttyu1.init      ugen2.1         xpt0
apm             console         cuau1.init      fido            io              mdctl           null            reroot          sysmouse        ttyu1.lock      ugen2.2         zero
Any clue? I know only the modem is not marked as supported in Opnsense wiki, but it works flawlessly with PFsense so I thought it should work with OPNsense.

Does anyone have a clue how to make it work?