@steveits Packages installed ? NONE.

CPU usage: about 50% when not doing the test (and otherwise no activity) No change when the test begins and ends.

After the test has ended however, CPU Usage climbs from about 50% to 98% for 5 seconds, then it returns to its normal 50%.

At the end of the day, it seems to me the SG-1000 may well be the bandwidth limiting factor. Should this be the case, then I will not change anything as I do no need such a high bandwidth anyway.

Thank you for your kind assistance.

I just tried adding a Monitor IP to an existing gateway and had no error. Perhaps related to the VPN?

@boumacor Oh yes, Thanks for your concern.

@johnpoz said in Routing to client with wrong default gateway:

@boumacor your welcome - glad you got it sorted. Yeah enough coffee does help ;)

Coffee and pizza :)

@burninbogey6 said in Setting up routing:
"when the WRT1200 is in bridge mode, it disables most of the router functions " dont use bridgemode, dus try with regular mode, don't use WAN port and connect the lan port to one of the ports of the switch.

You might need to setup a gateway (ip adress of the pFsense device) in the LAN interface of the WRT1200 to get everyting working.

@viktor_g

Might this will be helpful

[2.5.2-RELEASE][admin@canlfw03.networklab.prod]/root: frr-reload /usr/local/lib/frr/frr-reload.py:805: SyntaxWarning: "is not" with a literal. Did you mean "!="? if line is not "exit-vrf": vtysh failed to process new configuration: vtysh (mark file) exited with status 2: b'line 46: % Unknown command: network 10.18.130.0/24 area 0.0.0.0!\n\n' Exiting: failed to connect to any daemons. Traceback (most recent call last): File "/usr/local/lib/frr/frr-reload.py", line 1424, in <module> if not vtysh.is_config_available(): File "/usr/local/lib/frr/frr-reload.py", line 116, in is_config_available output = self('configure') File "/usr/local/lib/frr/frr-reload.py", line 105, in __call__ raise VtyshException('vtysh returned status %d for command "%s"' __main__.VtyshException: vtysh returned status 1 for command "configure"

@viragomann maybe the php-script does something else than the shell command does

@viragomann The odd thing is that both gateways are available. If you ping the gateway - it is available, if there is something behind the gateway - the packets just seem to be dropped.
I agree about the route 0.0.0.0/24, yesterday I did not realize it a little. Now I turned it off, it seems, it continues to work.
I continue to monitor)

@periko or state table.

When you said Meraki mesh, I assume you have multiple sites using Meraki? If so, you need to make sure your local pfsense has ipsec to the site where the 10.1.0.0/24 subnet is.

@vertigo8 nothing pfsense can do about devices on the same lan talking to or discovering each other.

For that you need to do that on your switch/wireless devices. Switch would be a private vlan. On wifi its called AP or Client isolation.

Pfsense is involved with traffic leaving a network, to be routed somewhere else - it is not able to control what devices do on the local network amongst themselves.

@wayne47 It would be interessting to see your pfsense interface config and frr status. It sounds to me that you have an upstream gateway configured on at least one interface (the one you call wan)

My expirence is that If you want routing to be handled by OSPF you should not have an upstream gateway configured on any of the interfaces receiving ospf routes and naturally also not override routing from firewall rules. If you want you default route to be one of the upstream edgerouters think you will need them to announce a default route.

@mer Thanks for the reply! Your comments got me to thinking which can be dangerous ;-)

I figured out the problem. It has to do with little Windows 10 app that the commercial VPN provides. This app resides in the system tray on the right side of the task bar in Windows 10. The app is used to connect and disconnect from the VPN. With your comments, I had the thought to try to figure out what DNS server windows was using when connected to the VPN and when not connected to the VPN. With a quick google search I found the Windows 10 command prompt nslookup command. Simply entering "nslookup" in a windows command prompt will return the DNS server being used. In my case, when I wasn't connected to the VPN, it returned the ip of my pfSense router. When I was connected to the VPN it returned an ip of a DNS server that belongs to my VPN provider. It seems that everytime you connect to the VPN service using their Windows 10 app, they change your DNS server address to their DNS server. I tried manually changing it back to the ip of my pfSense router but that didn't work when connected to the VPN - in that case I broke internet access altogether and couldn't connect to anything. When connected to the VPN, Windows wasn't able to resolve the local ip of my pfSense router. The solution will have to be to stop using the app provided by the VPN provider so that the DNS server that Windows uses stays pointing to my pfSense router. I had previously setup a gateway associated wiht the commercial VPN provider in my pfSense router. My solution will be to configure pfSense to route traffic from my Windows 10 through the VPN gateway when I want to use the VPN from my Windows 10 pc. Sort of a pain b/c I will have to log in to pfSense every time I want to use (or not use) the VPN. But in this scenario I can use the https://server1name.domain_name.tld paradigm to access my local services from my Windows 10 pc whether or not its WAN traffic is being routed through the VPN. This is because my Windows 10 pc will always be configured to use pfSense for domain name resolution.

@johnpoz I'm not trying to block plex it's just installed on the same computer that blue iris is running on.

I have never really messed with Docker or VMs

I have tried messing with allowing a device on one VLAN to talk to a device on another VLAN but it wasn't working. I'm sure I was doing something wrong.

Do you think the best/easiest route would be to have the plex/blue iris computer on the "Home" VLAN and set up all the cameras on the "ipcamera" VLAN and only let the "ipcamera" VLAN talk to the Plex/blue iris machine IP?

That's what I was going to try but I just wanted to make sure I wasn't going about it the wrong way and end up having to redo everything a different way later.

@nick-loenders ah!!! thanks for the info that keeps my curiosity cat purring nicely ;)

Hello @viragomann

thanks for your reply: I tried it, so I created this entry in my Cisco:

ip route 192.168.106.0 255.255.255.0 192.168.0.30

but can't ping or ssh anything. Any other suggestion? Maybe some configuration on the pfsense side.

--
Regards,

Marco