Recommendations for my pfsense setup with 5 nics
-
@stephenw10 said in Recommendations for my pfsense setup with 5 nics:
Which interface is 192.168.20.X?
I want it to be my Camera network.Is pfSense 192.168.20.1 there?
20.1 is the OPT1 ip addressWhat is the Cisco device at 192.168.20.2 that also seems to be replying to DHCP?
20.2 is the ip addres of VLAN20 on my cisco switch. I probably don't need that but I would like to be able to manage it via IP from any of my subnets. -
@teke you sure do not svi on every vlan to manage your switch that is for sure.
And you sure do not need a dhcp helper setup either.
What is the point of showing the lan interface 192.168.10.1 if where your problem is your opt interface?
-
It appears to be running as a DHCP relay. Is the client ending up with an IP in the wrong subnet?
-
@stephenw10
I will remove the cisco ip-helper addresses. My test machines are definately on the correct subnet depending on the cisco port I am in.@johnpoz
I'm just trying to show everything and I do apologize for my networking skills. I know enough to be dangerous. After watching videos it looked easy enough. I was wrong.
What would you like for me to do next? -
Does that client from the pcap at 192.168.20.100 show a gateway? It is being passed 192.168.20.1 to use. If it's not using that I can only imagine it's something on the client preventing it.
-
@stephenw10 said in Recommendations for my pfsense setup with 5 nics:
Does that client from the pcap at 192.168.20.100 show a gateway? It is being passed 192.168.20.1 to use. If it's not using that I can only imagine it's something on the client preventing it.
It is picking up the gateway as 192.168.20.1
-
Ok, so we need a pcap showing a client that fails to pull a gateway.
-
@stephenw10
Ok.
I just ran ipconfig on all of my machines and they are pulling a gateway from dhcp.
Here is where I'm a little stumped.
LAN - 192.168.10.0/24
OPT1 - 192.168.20.0/24
OPT2 - 192.168.30.0/24
OPT3 - 192.168.40.0/24 (no laptop hooked up yet)I can sucessfully ping LAN PC (192.168.10.10) from OPT1 and OPT2.
I can't get LAN to successfully ping OPT1 or OPT2
I can't get a successful ping between OPT1 and OPT2.
I'm a little lost where to go from here.Any guidance or suggestions I would truly appreciate.
-
Hmm, the rules you posted would allow all those pings.
Are you sure the things you are trying to ping in OPT1 and OPT2 actually respond to ping?
Try to ping them from pfSense. It will use an IP in their subnet which should get a response.Many devices will drop pings from outside their own subnet by default.
Steve
-
@stephenw10
I can ping all active IP's from the web console.Am I over thinking this? Should I just take it home and try it?
Could it be my cisco config? It's not elaborate by any means. Just vlans...
-
I clients in each subnet are receiving a gateway and can ping out to another subnet it's almost certainly a client side firewall preventing them respond to ping requests from outside their own subnet. The Windows firewall does that by default for example.
-
@stephenw10
I just found it weird that I can ping from OPT1 and 2 to LAN and it works but not the other way around.Should there be any gateways listed other than the WAN?
-
That's exactly what you would see if the devices in OPT1 and OPT2 are blocking ping requests from outside their subnet.
pfSense should only have one gateway unless you have other downstream routers with subnets behind them that pfSense needs to access. And you don't as far as I can see.
Steve
-
@stephenw10
Thank you for the help Stephen.
How can I test access between networks? Setup a share and try to access them?My current rules I should be able to access them correct?
-
Yes, the firewall rules in pfSense should allow you ping between all the subnets. Or send any IPv4 traffic.
The clients in those subnets have to accept traffic from other subnets though.
