Messages

Hello All.. I am trying to setup a remote logging connection to LogDNA and there instructions state that the following has to be put into the syslog-ng. File attached.

I have setup the connection but I am getting a TLS error in the logs even though the GUI took the cert I imported.

Same issue as before. All interfaces (VLANS) on the LAGG do not fail over when the active router is rebooted.

Found the issue.. For some reason syslog-d was not running.

Hello guys, I just updated to 20.7 and now my live view does not seem to be working. Even with auto-refresh going it does not scroll.. And I do not have any filters set.

This is still an issue. I have updated to 20.7 on both routers. I recabled the routers as suggested earlier.

Yes, it will be on the LAN side.

Hello RGN01.

Its called PBR. Pabst Blue..... wait thats not it.. Policy Based Routing.. :)

When you create your rule make sure the source address is the IP of your device with a destination of ANY and then towards the bottom of the rule you will see a spot to change the gateway. I have attached a screenshot to show it.

If this is a default install of OPNsense this should be all you need to do.

I also just tried on another router I have that is on 20.1 still no dice.

I am on release 19.7.9 on this router.

Hello guys. I am trying to back up to Google Drive but I am running into issues. I followed the WIKI to the letter. Service account, shared drive settings, key, etc. But when I go to save it I get this error attached.

I pasted the folder ID after the #/folder/ in the URL.

Am i doing something wrong?

Anything in logs? How is cabling done?

Its actually a simple design. A simple mesh using host based LAGG.. Each router has one member of the LAGG on each switch.

Also nothing of note in logs.

In a Lab with 10g and moderate Xeons I achived 1,9gbit

Is that "1.9Gbit" so almost 2Gb on a 10Gbit link?

So I have some firewalls that are using OPNsense based (non-LACP) load balancing based LAGG on OPNsense 20.1. I am also running two routers. The LAGG is hooked to two different switches. When I enter persistent CARP on the the "main" router or reboot it, the LAGG interfaces do not move to master on the "backup" router. I have put in the net.inet.carp.senderr_demotion_factor=0 and net.inet.carp.preempt=1 tunables but still no dice.

Am I missing something?

I guess I can. This is going to be a firewall used for VDI. I will be web filtering and dont want to but the Sunny Valley plugin on my "core" routers. I like to keep those as close to routers/firewalls only as possible.

You are just wanting to allow SMTP/S out from a single device on your LAN?

If this is the case you do not need a port forward which is what this looks like.

All you need is a LAN rule that specifies the source IP as your Synology device, a destination as smtp.gmail.com or any if you want it to connect to any external IP and destination port as SMTP/S.

You then, below this rule need to put in a rule with a block/reject and specify the source as your LAN net destination as any and destination port would be SMTP/S.

Also be sure and set another block rule with the same settings as the first but with SMTP so all SMTP and SMTP/S ports are blocked.