pfSense custom build hardware with Realtek port dilemma

techtester-m

@Gertjan said in pfSense custom build hardware with Realtek port dilemma:

It's a security device, not some basic Arduinio-based-Coffee-machine

Hahaha I actually laughed out loud...Yeah, you're right...I was still just experimenting it.

@Gertjan said in pfSense custom build hardware with Realtek port dilemma:

send to a syslog collector for later analyses

I've seen that option under the Logs section (send to syslog server or something). Would a simple old PC with enough storage connected to the local network do the job?

@Gertjan said in pfSense custom build hardware with Realtek port dilemma:

For typical 'home' usage the onboard syslog facilities will do fine

The mini PC where I'm experimenting all of this, has a cheap 240GB Kingston SSD. Syslog server/collector isn't needed, right?

@Gertjan said in pfSense custom build hardware with Realtek port dilemma:

edit : lol, I'll back off

LOL don't give up on me...

Gertjan

@techtester-m said in pfSense custom build hardware with Realtek port dilemma:

I've seen that option under the Logs section (send to syslog server or something). Would a simple old PC with enough storage connected to the local network do the job?

Yes - some device with any OS (call it Windows) and you'll find the tool. My Syn Diskstation can handle that job also.
As does any 'linux' based PC, since they all use 'syslog'.

@techtester-m said in pfSense custom build hardware with Realtek port dilemma:

The mini PC where I'm experimenting all of this, has a cheap 240GB Kingston SSD.

Consider make the log files bigger.
Goto Status > System Logs > Settings and check the second option, Log file size (Bytes)

Note that these days, pfSense uses fixed size files with circular logging. These files will never grow. Perfect for devices where disk space is an issue.
Future pfSense (2.50) will use classic "clear" logging - like syslog does. A log file rotating facility will be present. Up to you to choose the number of days / weeks / month to keep. Disk space is less an issue these days.

@techtester-m said in pfSense custom build hardware with Realtek port dilemma:

LOL don't give up on me...

Noop. Said that because @stephenw10 (a frequent poster) was also replying the same thing, but differently at the same moment.

edit : wtf : @stephenw10 : more then 18 K posts ...

stephenw10

Go to Diag > Command Prompt and execute mount -p. You should see something like:

/dev/diskid/DISK-9E18E959s2a /			ufs	rw,noatime 	1 1
devfs			/dev			devfs	rw		0 0
/dev/diskid/DISK-9E18E959s1 /boot/u-boot		msdosfs	rw,noatime 	0 0
/dev/md0		/tmp			ufs	rw		2 2
/dev/md1		/var			ufs	rw		2 2
devfs			/var/dhcpd/dev		devfs	rw		0 0

You can see on that SG-3100 the root filesystem / is mounted 'noatime'.
If yours is not go to Diag > Edit File an open /etc/fstab. Edit the / line to include noatime. So it would probably just be rw. Change it to rw,noatime.
Note that breaking the fstab with a typo will probably make the system unbootable until it's corrected so....
Reboot to apply that change. Run mount -p again to be sure.

@Gertjan said in pfSense custom build hardware with Realtek port dilemma:

edit : wtf : @stephenw10 : more then 18 K posts ...

Yeah it's a problem. I'm trying to cut down!

Steve