Menu

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.

Show posts Menu

Topics - Dantichrist

#1
24.1, 24.4 Legacy Series / Problem using Kea DHCP
July 16, 2024, 08:44:48 PM
Hello.

I'm having an issue with one reservation that's not working correctly. It's with a Raspberry Pi that I'm using as a DNS server for my network. The reservations for everything else works as it should.

I've copied everything over to Kea from ISC, and at first it seemed like everything was fine. After about an hour the reservation stops working, and Kea assigns an incorrect address to it after the initial lease runs out.

According to the logs it appears that there are several characters added to the front of the MAC address for the Pi's NIC in the cid causing it to assign it a different IP than the one that's reserved, and I can't figure out what's causing it. I don't have the issue at all while using ISC, and it has worked as intended for several years now.

I'm hoping that someone with more knowledge about this can point me to the direction of where the problem could be.

Thank you in advance for any help!

Sincerely,

Dan

Edit: In the first line in the attached log KEA does assign the correct address.
#2
Hello,

After updating to 24.1 google drive backups no longer work.

Looking at the plugins page it shows that os-api-backup is orphaned. I'm not sure if that's the cause of it. Looking at the backups configuration page my p12 key was missing. I re-added it but it will not save. It has worked fine for years prior to the update.

After adding the p12 key back in it says

The following input errors were detected:

    Invalid P12 key, openssl_pkcs12_read() failed
    Saved settings, but remote backup failed.

I noticed that the updates log shows "pkg: libevent has a missing dependency: openssl111" as well. I'm not sure if that's part of the issue or not but I've never seen that before.

Is there something that I can do to resolve this? Thank you in advance for your help!
#3
22.1 Legacy Series / os-ddclient with Godaddy
July 07, 2022, 09:48:19 PM
Hello,

I'm hoping that someone that has gotten os-ddclient to work with godaddy can help me out to get it working. I've been trying for the past few months, and have had no luck. Since the new client has been introduced they have added godaddy in the list of supported services.

I'm not sure what it is that I'm doing wrong. I'm able to get it working fine with a shell script with the same server/credentials. It also works fine with the depreciated dyndns client.

I've tried both available protocols, and can't get it to update.

This is what is in the log with both of the protocols:

2022-07-07T13:33:44-06:00 Notice ddclient[82034] 6272 - [meta sequenceId="21"] RECEIVE: {"code":"NOT_FOUND","message":"Not Found : The requested resource was not found"}
2022-07-07T13:33:44-06:00 Notice ddclient[82034] 4636 - [meta sequenceId="20"] RECEIVE:
2022-07-07T13:33:44-06:00 Notice ddclient[82034] 3140 - [meta sequenceId="19"] RECEIVE: Connection: close
2022-07-07T13:33:44-06:00 Notice ddclient[82034] 1262 - [meta sequenceId="18"] RECEIVE: Date: Thu, 07 Jul 2022 19:33:44 GMT
2022-07-07T13:33:44-06:00 Notice ddclient[82034] 233 - [meta sequenceId="17"] RECEIVE: Pragma: no-cache
2022-07-07T13:33:44-06:00 Notice ddclient[82034] 98779 - [meta sequenceId="16"] RECEIVE: Cache-Control: max-age=0, no-cache, no-store
2022-07-07T13:33:44-06:00 Notice ddclient[82034] 97726 - [meta sequenceId="15"] RECEIVE: Expires: Thu, 07 Jul 2022 19:33:44 GMT
2022-07-07T13:33:44-06:00 Notice ddclient[82034] 96279 - [meta sequenceId="14"] RECEIVE: Content-Length: 81
2022-07-07T13:33:44-06:00 Notice ddclient[82034] 95578 - [meta sequenceId="13"] RECEIVE: Content-Type: application/json
2022-07-07T13:33:44-06:00 Notice ddclient[82034] 94404 - [meta sequenceId="12"] RECEIVE: HTTP/1.0 404 Not Found
2022-07-07T13:33:44-06:00 Notice ddclient[82034] 93004 - [meta sequenceId="11"] SENDING:
2022-07-07T13:33:44-06:00 Notice ddclient[82034] 93004 - [meta sequenceId="10"] SENDING:
2022-07-07T13:33:44-06:00 Notice ddclient[82034] 93004 - [meta sequenceId="9"] SENDING: Connection: close
2022-07-07T13:33:44-06:00 Notice ddclient[82034] 93004 - [meta sequenceId="8"] SENDING: User-Agent: ddclient/3.9.1
2022-07-07T13:33:44-06:00 Notice ddclient[82034] 93004 - [meta sequenceId="7"] SENDING: Authorization: Basic XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
2022-07-07T13:33:44-06:00 Notice ddclient[82034] 93004 - [meta sequenceId="6"] SENDING: Host: api.godaddy.com
2022-07-07T13:33:44-06:00 Notice ddclient[82034] 93004 - [meta sequenceId="5"] SENDING: GET /nic/dyndns?action=edit&started=1&hostname=YES&host_id=cXXXX.XXXXXXXXXXXX.com&myip=XX.XXX.XX.XXX HTTP/1.0
2022-07-07T13:33:44-06:00 Notice ddclient[82034] 91134 - [meta sequenceId="4"] CONNECTED: using SSL
2022-07-07T13:33:43-06:00 Notice ddclient[82034] 87859 - [meta sequenceId="3"] CONNECT: api.godaddy.com
2022-07-07T13:33:43-06:00 Notice ddclient[82034] 85229 - [meta sequenceId="2"] UPDATE: updating XXXX.XXXXXXXXXXXX.com
2022-07-07T13:33:43-06:00 Notice ddclient[82034] 83545 - [meta sequenceId="1"] INFO: setting IP address to XX.XXX.XX.XXX for XXXX.XXXXXXXXXXXX.com


If I use the no protocol setting I get:

2022-07-07T13:25:52-06:00 Notice ddclient[24847] 45739 - [meta sequenceId="22"] RECEIVE: {"code":"NOT_FOUND","message":"Not Found : The requested resource was not found"}
2022-07-07T13:25:52-06:00 Notice ddclient[24847] 43836 - [meta sequenceId="21"] RECEIVE:
2022-07-07T13:25:52-06:00 Notice ddclient[24847] 42964 - [meta sequenceId="20"] RECEIVE: Connection: close
2022-07-07T13:25:52-06:00 Notice ddclient[24847] 41413 - [meta sequenceId="19"] RECEIVE: Date: Thu, 07 Jul 2022 19:25:52 GMT
2022-07-07T13:25:52-06:00 Notice ddclient[24847] 41122 - [meta sequenceId="18"] RECEIVE: Pragma: no-cache
2022-07-07T13:25:52-06:00 Notice ddclient[24847] 40200 - [meta sequenceId="17"] RECEIVE: Cache-Control: max-age=0, no-cache, no-store
2022-07-07T13:25:52-06:00 Notice ddclient[24847] 39090 - [meta sequenceId="16"] RECEIVE: Expires: Thu, 07 Jul 2022 19:25:52 GMT
2022-07-07T13:25:52-06:00 Notice ddclient[24847] 38372 - [meta sequenceId="15"] RECEIVE: Content-Length: 81
2022-07-07T13:25:52-06:00 Notice ddclient[24847] 37251 - [meta sequenceId="14"] RECEIVE: Content-Type: application/json
2022-07-07T13:25:52-06:00 Notice ddclient[24847] 35815 - [meta sequenceId="13"] RECEIVE: HTTP/1.0 404 Not Found
2022-07-07T13:25:52-06:00 Notice ddclient[24847] 35029 - [meta sequenceId="12"] SENDING:
2022-07-07T13:25:52-06:00 Notice ddclient[24847] 35029 - [meta sequenceId="11"] SENDING:
2022-07-07T13:25:52-06:00 Notice ddclient[24847] 35029 - [meta sequenceId="10"] SENDING: Connection: close
2022-07-07T13:25:52-06:00 Notice ddclient[24847] 35029 - [meta sequenceId="9"] SENDING: User-Agent: ddclient/3.9.1
2022-07-07T13:25:52-06:00 Notice ddclient[24847] 35029 - [meta sequenceId="8"] SENDING: Authorization: Basic XXXXXXXXXXX
2022-07-07T13:25:52-06:00 Notice ddclient[24847] 35029 - [meta sequenceId="7"] SENDING: Host: api.godaddy.com
2022-07-07T13:25:52-06:00 Notice ddclient[24847] 35029 - [meta sequenceId="6"] SENDING: GET /nic/update?system=dyndns&hostname=XXXX.XXXXXX.com&myip=XX.XXX.XX.XXX HTTP/1.0
2022-07-07T13:25:52-06:00 Notice ddclient[24847] 33425 - [meta sequenceId="5"] CONNECTED: using SSL
2022-07-07T13:25:51-06:00 Notice ddclient[24847] 29979 - [meta sequenceId="4"] CONNECT: api.godaddy.com
2022-07-07T13:25:51-06:00 Notice ddclient[24847] 29104 - [meta sequenceId="3"] UPDATE: updating XXXX.XXXXXX.com
2022-07-07T13:25:51-06:00 Notice ddclient[24847] 27913 - [meta sequenceId="2"] INFO: setting IP address to XX.XXX.XX.XXX for XXXX.XXXXXX.com
2022-07-07T13:25:51-06:00 Notice ddclient[24847] 25940 - [meta sequenceId="1"] WARNING: file /usr/local/etc/ddclient.conf, line 12: Invalid Value for keyword 'protocol' = ''


The content of os-ddclient.conf is this:

syslog=yes                  # log update msgs to syslog
pid=/var/run/ddclient.pid   # record PID in file.
verbose=yes
ssl=yes


use=if, if=igb1, \
protocol=, \
server=api.godaddy.com, \
login=XXXXXXXXXXXXXX, \
password=XXXXXXXXXXXXX \


If I use dyndns 1/2 as the protocol they show in the config as expected.

Thank you in advance for your help!
#4
22.1 Legacy Series / Log time/date format.
January 30, 2022, 05:34:19 AM
Since the update any logs on the system seem to include the time offset for the region that I live in (MST). I'm not sure if this was intended or not so I figured that I'd post as an FYI in case it's unintended.
#5
Hello,

I have tried everything that I can think of over the past few months to get this working properly. If I enable IPS my (lagg0)WAN interface will drop after around five to ten minutes. I can bounce the interface, and it will come back up but will go back down after five to ten minutes.

Hardware CRC, Hardware TSO, and Hardware LRO are all disabled. VLAN Hardware Filtering is set to disabled as well.

I've tried running all combinations of VLAN Hardware Filtering on/off, and Promiscuous mode on/off, and the WAN interface will go down every time. I have also tried using a "pass" policy for my CM1200 cable modem (192.168.100.1) in case it was something with that.

The LAGG interface works superbly, and is rock solid. It consistently tests out with ~1300Mbps down/~42Mbps up as long as IPS is off. It will also alert just fine with just IDS on.

When the interface goes down there is nothing that I can see in the suricata/system logs that give me any indication of what is causing it. Also the hardware can handle it easily with an i7 4590 with 16GB of RAM. I don't see any CPU, memory, or mbuff spikes. They all stay the same as it would with IPS off. All of my NICs are Intel 82576 (igb).

I have also tried it with RSS on and off and it makes no difference.

I'm just wondering if anyone else with a similar set up gotten this to work. It's not a huge issue for me but it's one of those things that keep coming back to that I'd like to solve, or at least understand what is causing it.

Thank you in advance for any ideas or info that you can share!
#6
21.1 Legacy Series / Monit alerts with Suricata
March 29, 2021, 11:16:53 PM
I hope that this is the right place to ask this.

I have been trying to get alerts working for suricata, and haven't been able to get them to work. I do get alerts for anything else that I have set up so I know that I have the alert settings set up properly.

I have set it up as it is shown in the manual https://docs.opnsense.org/manual/monit.html verbatim but I'm not getting alerts when I have blocked entries in the suricata log.

One thing that is really strange thing that I noticed is that if I vi /usr/local/etc/monitrc I have this in the config:

check file SURICATA_ALERT with path "/var/log/suricata/eve.json"
   if content = \xe2\x80\x9cblocked\xe2\x80\x9d then alert

If I cat the same file I get this:

check file SURICATA_ALERT with path "/var/log/suricata/eve.json"
   if content = "blocked" then alert

If I look at it with less or more I get this:
check file SURICATA_ALERT with path "/var/log/suricata/eve.json"
   if content = <E2><80><9C>blocked<E2><80><9D> then alert

If I manually change "if content =" to blocked with vi I still don't get alerts even thought the status page in the UI shows that the service test is being triggered. If I reboot or make any changes to monit via the web interface it will change back to \xe2\x80\x9cblocked\xe2\x80\x9d.

I've spent a few days trying different things, and reading anything that I can get my hands on to to try to get this working and I'm out of ideas.

Can anyone give me any direction on what to try next? Thank you in advance for your time.