Messages

1

22.7 Legacy Series / Re: DNS not working - can't resolve domain names behind opnsense

« on: September 11, 2022, 03:45:26 pm »

it seems like your opnsense blocks outgoing traffic for DNS. you try to ping 8.8.8.8 but DNS ist not ICMP related. I would suggest to test it like this:
Disable the packet filter for short time and try to resolve a domain name via dig. If this works the problem is that opnsense is blocking your dns queries. Please turn on the filter again after testing!!! You can also do a live view in the logs while trying do resolve domain names. DNS queries are working via UDP port 53, try creating a rule for adguard to be alloewd for this traffic.  BR

2

22.7 Legacy Series / Re: Multiple services don't work after update to 22.7

« on: August 03, 2022, 09:29:51 am »

what settings do you use? Enable syncookies : always ?

I have it set to "adaptive"  start 60, end 30, and whatsapp, facebook etc all is working fine.

I used always, which caused problems.
Now i use 50/25 which works fine

3

22.7 Legacy Series / Re: Multiple services don't work after update to 22.7

« on: August 02, 2022, 04:27:39 pm »

i turned off the "DDOS protection" - syncookies.
Now whats app web is working again
When i turn it on again the page will not load.

4

22.7 Legacy Series / Re: Multiple services don't work after update to 22.7

« on: August 02, 2022, 09:54:32 am »

I am facing the same Issue with WhatsApp after updating opnsense  to latest Version.

5

22.7 Legacy Series / Re: Display an explanatory page when DNS block / firewall rules kick in

« on: July 31, 2022, 10:41:10 am »

This would be a very useful feature also for me!!

6

22.1 Legacy Series / Re: 22.1.9 Upgrade - Unbound logfile GUI hang

« on: June 26, 2022, 06:02:14 pm »

i get results immediately with every kind of filter selected!

7

22.1 Legacy Series / Re: 22.1.9 Upgrade - Unbound logfile GUI hang

« on: June 26, 2022, 03:26:14 pm »

HI,

i updated today and just tested it and i do not have this issue.

BR

8

22.1 Legacy Series / Re: Syslog, Graylog, not human readable logs?

« on: June 11, 2022, 02:10:52 pm »

OK, I have searched, and I have not seen this issue, I am sure that I am overlooking something (hopefully simple).

I have installed Graylog 4.3 + Mongo 4.2 + Elasticsearch 7.17. I have setup inputs (and extractors), indices, and streams in GrayLog, I have this on port 1514 and then created a logging target in OpnSense UDP(4) everything left as default except the hostname and port. I see ingress and I can see the logs and messages, communication seems to be working.

My problem is that the logs are not human readable. It seems like there is encoding that is happening and I am not sure how to work it out. This is what a log looks like in GrayLog:

Code: [Select]

2022-05-25 16:52:25.651 172.17.0.1
�>�b�^�
J�
\���l��PJS0


G�0�0��5�@"P���JS0


M�0�05�)

k
Any ideas?

Thanks!

*** UPDATE ***

I configured a Unifi Controller to send syslogs and in GrayLog they ARE human readable. So, it appears that it is something with OpnSense.

i had the same problem.
it was solved after disabling "SYSTEM: SETTINGS: LOGGING / TARGETS" and restarting the telegraf service and enabling my object in "SYSTEM: SETTINGS: LOGGING / TARGETS" again.