Recommendations for my pfsense setup with 5 nics

Jarhead

@teke That's not possible.
The WAN has nothing to do with the DHCP server.
I've done that plenty of times, had a disconnected WAN, and the network attached to the LAN still worked fine.

Glad it's working but you aren't telling us everything.

Plus, now you're saying 192.168.10 IS the LAN and it gave out an address without the WAN connected.

Teke

@jarhead
I'm not holding anything back.
The 192.168.1 address I posted above was the LAN address after I reinstalled pfSense. Since I wanted my LAN address to be 192.168.10 I changed it to that and posted the ipconfig of that as well.

I'm just reporting back what I am seeing. Once I plugged the WAN it to my works network and did a release and renew the gateway was then appearing of the local network I was on.
ex. 192.168.40.100 pc was getting a 192.168.40.1 gateway. When I disconnect the WAN the gateway disappears on a release and renew.

I'm going to bring a router from home in just to take that out of the equation and mimic the whole setup.

I do understand that the WAN has nothing to it, this has just been frustrating for me setup. All of the videos I've watch looks so easy and I've followed them to letter but nothing has worked to this point.

johnpoz

@teke that dump you posted has no dhcp in it..

Teke

@johnpoz
I did do a release and a renew. I will do it again.

stephenw10

Hmm curious.

Yes, the DHCP server should hand out the interface IP as a gateway for connected clients by default and whether or not the WAN is connected.

The only way I'm aware of to prevent it is to enter none for the gateway IP specifically.
Is it possible you entered that at some point and your browser is auto-filling it?

Screenshot from 2022-12-17 00-32-36.png

I assume you're running pfSense 2.6?

Steve

Teke

@johnpoz
Here is another dump.
Also Pictures of my firewall settings, dhcp settings. capture30.pcapng

stephenw10

With that config any client on LAN should be passed 192.168.10.1 as it's gateway/default route. And that should happen with or without a WAN connection.

johnpoz

@teke not sure what any of that has to do with anything? the only picture that helps is that you don't have none set in the dhcp.

where is the pcap showing your dhcp - so can see if the gateway was offered or even asked for by the client, etc.

Teke

@johnpoz
I did post the capture30.pcapng. It's at the right of the last picture. Is that not what you are looking for?

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.