Recommendations for my pfsense setup with 5 nics

stephenw10

Which interface is 192.168.20.X?

Is pfSense 192.168.20.1 there?

What is the Cisco device at 192.168.20.2 that also seems to be replying to DHCP?

johnpoz

@teke why is the IP range now 192.168.20 vs what you posted 192.168.10.

Clearly in the offer there is a router listed (gateway)

But then it looks like you got some relay setup on your switch, that also sent an ack?

this 20.2 is cisco something

But it also includes the router.. But why are you setting up a dhcp relay on your switches? You do not need a helper setup..

stephenw10

It is passing 192.168.20.1 as to the client though:

Frame 52: 342 bytes on wire (2736 bits), 342 bytes captured (2736 bits) on interface \Device\NPF_{BF7A7DCF-B2B5-493A-823E-808EAEDB7BE9}, id 0
Ethernet II, Src: Broadcom_71:92:ba (00:10:18:71:92:ba), Dst: Dell_f0:4d:49 (8c:ec:4b:f0:4d:49)
Internet Protocol Version 4, Src: 192.168.20.1, Dst: 192.168.20.100
User Datagram Protocol, Src Port: 67, Dst Port: 68
Dynamic Host Configuration Protocol (Offer)
    Message type: Boot Reply (2)
    Hardware type: Ethernet (0x01)
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0xde3b3dfc
    Seconds elapsed: 0
    Bootp flags: 0x0000 (Unicast)
    Client IP address: 0.0.0.0
    Your (client) IP address: 192.168.20.100
    Next server IP address: 0.0.0.0
    Relay agent IP address: 0.0.0.0
    Client MAC address: Dell_f0:4d:49 (8c:ec:4b:f0:4d:49)
    Client hardware address padding: 00000000000000000000
    Server host name not given
    Boot file name not given
    Magic cookie: DHCP
    Option: (53) DHCP Message Type (Offer)
        Length: 1
        DHCP: Offer (2)
    Option: (54) DHCP Server Identifier (192.168.20.1)
        Length: 4
        DHCP Server Identifier: 192.168.20.1
    Option: (51) IP Address Lease Time
        Length: 4
        IP Address Lease Time: (7200s) 2 hours
    Option: (1) Subnet Mask (255.255.255.0)
        Length: 4
        Subnet Mask: 255.255.255.0
    Option: (3) Router
        Length: 4
        Router: 192.168.20.1
    Option: (6) Domain Name Server
        Length: 4
        Domain Name Server: 192.168.20.1
    Option: (15) Domain Name
        Length: 12
        Domain Name: maclean.home
    Option: (255) End
        Option End: 255
    Padding: 000000000000000000000000

Teke

@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 address

What 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.

johnpoz

@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?

stephenw10

It appears to be running as a DHCP relay. Is the client ending up with an IP in the wrong subnet?

Teke

@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?

stephenw10

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.

Teke

@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

stephenw10

Ok, so we need a pcap showing a client that fails to pull a gateway.

Teke

@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.

stephenw10

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

Teke

@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...

stephenw10

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.

Teke

@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?

stephenw10

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

Teke

@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?

stephenw10

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.