@mattlach said in Maximum Log Size: @bmeeks said in Maximum Log Size: @mattlach said in Maximum Log Size: @bmeeks said in Maximum Log Size: pfSense currently uses a special logging utility called clog for its system logging. This utility produces a binary circular log file that is first-in first-out. It is not like a normal syslog file on say Linux. Circular logging was implemented when pfSense was first created because many of the installs were on small memory footprint systems with flash memory (remember NanoBSD). The size limit you are hitting is imposed, I believe, by the clog utility. Most folks who want to maintain tons of log data use the syslog export feature to send the logs to an external syslog or rsyslog host. Thank you for that. I will google to see if I can find any guides regarding syslog export. There are some configuration parameters on the Settings tab of the SYSTEM LOG screen for setting up log export to a remote syslog host. You will find it easiest to create a Linux machine (a VM is perfect on a hypervisor) to be the syslog receiver. There are also packages such as ELK that a lot of folks use. Google the term "ELK" for more info. It is an acronymn for Elastisearch Logstash Kibana if I am remembering correctly. This is a suite of software tools you install on a Linux host. Thanks again. I just created an Ubuntu server 18.04 container on my mmain server, and configured rsyslog per this guide. Next I went into the GUI configuration on pfSense and enabled remote logging and added in the IP of the ubuntu machine, as described here. It doesn't appear to have received any logs yet. Maybe it needs UDP? I only enabled TCP. Or maybe I have a permissions problem on the folder I asked it to store the logs in. I'm troubleshooting. netstat shows no connections on port 514 though, so the issue seems to not be permissions, but rather be that the connection isn't established. Do I need to do anything to pfsense to make it start sending logs, or is checking the box, configuring and hitting apply enough? Turns out it was indeed a filesystem permissions error. I had pointed the logs in a nonstandard location (/mnt/rsyslogd, a mounted drive) Once I changed the owners to the same as in /var/log (root:syslog for the folder, and syslog:adm for the log files) and then matched the read and write permissions to /var/log as well, things seemed to work as expected. Thanks for all the help! --Matt

@JLundberg Moving this to OpenVPN section

In general using Realtek network interfaces for anything server/infrastructure oriented is just a bad idea. They simply aren't particularly reliable, and usually perform poorly.

@Timbro said in Help, I'm a noob: UBC1301 https://mediacomcc.custhelp.com/euf/assets/documents/modem%20user%20guides/Ubee_UBC1301-AA00_%20User_Guide.pdf Yes it is a router by default. This doc shows its LAN subnet as 192.168.100.0/24 so things should work out of the box. But if your ISP has them configured different it may be 192.168.1.0/24 which would not work. You can not have the same subnet on the WAN as you do the LAN. See if your ISP or yourself can put your cablemodem in bridge mode. Then restart both modem and pfsense.

...and this syntax works fine with Gmail too! Thanks for the tip.

@renjithb said in Issue in Virtual box installation: Yes the same way I configured Which is how? What can not talk to what? Your host from what IP can not talk to pfsense IP on what interface in VB.. Your really going to have to give us more if you want any help.. sofar you have told the mechanic its broke..

Still better to have the public IP on the pfSense WAN directly if you can. Steve

@microkid yes that's okay, I also wrote this too, but fix the file system before you scan further the box everything must be ruled out when searching for such an error.. poor disk fragmentation, a typical cause of random crashes I know you think of the NIC because the LEDs don't flash but like I said it could be part of a process

@nafeasonto said in Can someone help me please? I can't udpate my packages on PFsense.: 2.5 of Pfsense. Ah, the bleeding edge technology. Probably not everything, but most of this page could be helpfull. edit : also : consider posting in the 2.5 Development forum.

This is a recent, clean install ? You use packages ? If so, what happens if you disable them all ?

@valentinius Yes, as i posted above the issue is resolved.

Had a moment to look in the logs more closely. I see this: miniupnpd 34231 setsockopt(udp, IPV6_RECVPKTINFO): Invalid argument It works, but... This happens on restart of miniupnpd after any config change.

Update - @Gertjan @johnpoz I think one of the problems (or the main one) was not a DNS blocking/limiting etc. but a static route to it set by pfsense because it was used as a monitoring IP etc. (read about it online). Since I'm never gonna use 4.2.2[1-6] for production DNS resolving, I decided to utilize them as monitor IPs for every gateway that is not the WAN itself or has no proper 'upstream' gateway to check against. Currently I'm happy with the solution below. I think the assumption mentioned in the screenshot is correct but we'll see what happens. [image: 1593508324504-screen-shot-2020-06-30-at-11.55.49.png] [image: 1593508333326-screen-shot-2020-06-30-at-11.56.06.png]

@rafamello If their SIP packets have the private IP encapsulated then they won't be able to stream back to you. I'm not sure which it would be but it's either ALG or the double NAT. SIP doesn't really work with either. When dealing with Cable operators in the USA (Spectrum and Comcast) there are 3 modes for the cable modems: RIP with NAT = Use when you are not providing a separate router. You would never use this with pfSense or any other customer provided firewall/router. RIP without NAT = Use when you have a static IP programmed in the router and the modem needs to be your Gateway. Bridge = Use when you don't have a static and are providing your own router. This puts the Public IP directly on your firewall.

@bmeeks I'll have to look at the packet capture to see what is going on at this point. I set everything up this morning again fresh with just the very basic default settings on the netgate box and this is what I have found. no netgate installed on my home network I can connect to my site with chrome and edge. put in the netgate and only edge will see my site. I tried to do a reinstall from the flash image and it gave me ad error not being able to read the drive. I followed the support link and used the program they suggested to image my flash drive and it did fine even it's test said it was fine. So I'm now looking for a new flash drive to retry to redo the image. I know you guys think I'm missing something simple because what I'm telling you just can't happen... Well if it can it will happen to me. I really can't tell you any more then what I have and I almost went through writing my last couple messages as I was doing it here at the house. I don't know how much more of a basic setup I can get. I'll shutup :-) once I'm able to get a new inage on my box to see if that has anything to do with something residule not being reset. But like you said, the browsers are supposed to be 100% agnostic. so something is going on here. if I can do a lookup and it comes back fine then why shouldn't both browsers act the same. Thank you for all your comments. I will do a packet capture and see what's going on. too weird.