1
23.7 Legacy Series / Re: Firewall Diagnostics - Search Not Working?
« on: September 18, 2023, 07:10:47 am »
Woohoo, I'm not crazy. 
Thanks for the link. Patches fixed the glitch.
Thanks for the link. Patches fixed the glitch.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
23.7 Legacy Series / SOLVED: Firewall Diagnostics - Search Not Working?
« on: September 17, 2023, 07:59:30 pm »
General question cause I "think" this used to work on an older version...I'm currently on v23.7.4
If I 1) Nav to Firewall, Diagnostics, Sessions, 2) Wait for the data to load, then 3) Search for something, e.g. a specific port like "5060", it returns "no results found" when I know they are there in the list. The only thing I can get to match is a complete and specific IP address, e.g. "192.168.10.2", partials don't work either.
Am I missing something? Can anyone else confirm?
If I 1) Nav to Firewall, Diagnostics, Sessions, 2) Wait for the data to load, then 3) Search for something, e.g. a specific port like "5060", it returns "no results found" when I know they are there in the list. The only thing I can get to match is a complete and specific IP address, e.g. "192.168.10.2", partials don't work either.
Am I missing something? Can anyone else confirm?
3
22.1 Legacy Series / Re: os-ddclient 1.7 - PHP Error
« on: June 28, 2022, 07:37:56 pm »Quote.... I have to issue the command each time I add a service.
No you don't, executing it again will revert the change...
Hmm...Well I don't know then. I guess I added a second service, had the PHP errors, then I must have issued the command twice or something to that effect. Anyhoo, I managed to get three working DDNS services added, so I'm good.
Thanks
4
22.1 Legacy Series / Re: os-ddclient 1.7 - PHP Error
« on: June 26, 2022, 12:58:49 pm »
This fixed my issue, too. Looks like I have to issue the command each time I add a service.
can you try https://github.com/opnsense/plugins/commit/339993680de4453962d21546a181550bd1cc0f0f ?
To install via a console, use the following command:Code: [Select]opnsense-patch -c plugins 33999368
the /var/tmp/ddclient.cache file likely contains incomplete data.
Best regards,
Ad
5
20.1 Legacy Series / (Workaround) Deutsche Telekom DSL | PPPoE Renewal & IPV6
« on: April 10, 2020, 03:17:03 pm »
Hi folks…I have a problem and workaround. Thought I would share for others.
System Info
Qotom Mini-PC
OPNsense 20.1.3-amd64
FreeBSD 11.2-RELEASE-p17-HBSD
OpenSSL 1.1.1d 10 Sep 2019
Problem: System does not receive correct IPv6 addresses from DSL provider after a forced or initiated PPPoE reset
Solution: Create a Cron Job to run /var/etc/rtsold_pppoe0_script.sh at 0303; System normalizes IPv6 addresses.
I have no idea if what I did is healthy, recommended, or plain crazy…but it works. If I run that script at any time after the PPPoE resync, the IPv6 issue is resolved. I wonder if it fails during the 0300 cron reset because it is set to request an IPv6 address via IPv4 and that may not be up yet? I’m not smart enough to figure that part out.
If you can read German, there were some folks having a similar issue on pfSense a few years ago https://forum.netgate.com/topic/115578/nach-periodic-reset-keine-neu-ipv6-adresse. I had their solution working on pf, but this new workaround is easier for me on OPNSense.
Hope that’s helpful for someone in the future…Maybe even me, if I forget what I did to fix it in a few years.
Edit: Fix script location
System Info
Qotom Mini-PC
OPNsense 20.1.3-amd64
FreeBSD 11.2-RELEASE-p17-HBSD
OpenSSL 1.1.1d 10 Sep 2019
Problem: System does not receive correct IPv6 addresses from DSL provider after a forced or initiated PPPoE reset
- My provider Deutsche Telekom requires a PPPoE reset every 24 hours. I’ve set that up to happen via cron at 0300.
- WAN is configured for DHCPv6
- LAN is configured for Track Interface (WAN)
Solution: Create a Cron Job to run /var/etc/rtsold_pppoe0_script.sh at 0303; System normalizes IPv6 addresses.
I have no idea if what I did is healthy, recommended, or plain crazy…but it works. If I run that script at any time after the PPPoE resync, the IPv6 issue is resolved. I wonder if it fails during the 0300 cron reset because it is set to request an IPv6 address via IPv4 and that may not be up yet? I’m not smart enough to figure that part out.
If you can read German, there were some folks having a similar issue on pfSense a few years ago https://forum.netgate.com/topic/115578/nach-periodic-reset-keine-neu-ipv6-adresse. I had their solution working on pf, but this new workaround is easier for me on OPNSense.
Hope that’s helpful for someone in the future…Maybe even me, if I forget what I did to fix it in a few years.
Edit: Fix script location
Pages: [1]