Configuring OPT3

johnpoz

Well if your going to want opt3 devices to do anything, ping pfsense - go to opt2 or lan or internet then you would need to put those rules there. But again that does not stop pfsense from pinging into opt3 network. If you can not ping stuff in opt3 from pfsense then you have something else going on other than just lack of rules on opt3

m3tatr0n

@johnpoz:

Well if your going to want opt3 devices to do anything, ping pfsense - go to opt2 or lan or internet then you would need to put those rules there. But again that does not stop pfsense from pinging into opt3 network. If you can not ping stuff in opt3 from pfsense then you have something else going on other than just lack of rules on opt3

There will be rules added to this interface but for now I just want servers on that network to be able to at least go out through the WAN.
This network will be totally separated from our LAN and the network on OPT1. Only remote client will access this network via OpenVPN and HTTP/S.

johnpoz

well how are you connecting these interfaces to your network? What vlan are they in, are they just dumb switches that you have isolated for each network?

m3tatr0n

@johnpoz:

well how are you connecting these interfaces to your network? What vlan are they in, are they just dumb switches that you have isolated for each network?

Yes, dumb switches. Just wanted it totally separated from the other segments.

johnpoz

that is fine and rules out issues with vlan config on your switches.

So your saying you have this

pfsense opt3 - dumbswitch - pc
psense lan - different dumbswitch - different pc

Both with network 192.168.30/24, lets forget the whole carp setup for a bit. You configure pfsense opt3 with 192.168.30.1/24 and your pc with 192.168.30.100/24

If pfsense can not see mac in his arp table when you try and ping 192.168.30.100 then you got bad cable, bad switch, interface not actually working, etc.

PC firewall might block you from getting answer, but its not going to block the arp for the mac. Doing the same thing from pc to 192.168.30.1 again if you don't have rules on opt3 to allow ping you wont get an answer but you should see the mac of pfsense opt3 interface.

your pfsense is on a physical device right, its not VM running in some vm host??

m3tatr0n

@johnpoz:

that is fine and rules out issues with vlan config on your switches.

So your saying you have this

pfsense opt3 - dumbswitch - pc
psense lan - different dumbswitch - different pc

Both with network 192.168.30/24, lets forget the whole carp setup for a bit. You configure pfsense opt3 with 192.168.30.1/24 and your pc with 192.168.30.100/24

If pfsense can not see mac in his arp table when you try and ping 192.168.30.100 then you got bad cable, bad switch, interface not actually working, etc.

PC firewall might block you from getting answer, but its not going to block the arp for the mac. Doing the same thing from pc to 192.168.30.1 again if you don't have rules on opt3 to allow ping you wont get an answer but you should see the mac of pfsense opt3 interface.

your pfsense is on a physical device right, its not VM running in some vm host??

PFSense is a physical device Netgate SG-4860
Before configuring OPT3, the WAN, LAN and OPT1 are already working, all are configured for CARP.

OPT3 ip address is 192.168.30.252
Server1 ip address is 192.168.30.10
Server2 ip address is 192.168.30.11

Only firewall rule is to allow OPT3 interface, any protocol, with source OPT3 net to allow connection to any.
server1 can ping server2 and vice versa.

Steps taken so far:

Use another dumb switch
Use OPT2 instead of OPT3
Use different network cables.

johnpoz

You sure you have the mask right, pfsense defaults to /32 when you create a new IP.. Sure you didn't put /32 vs /24??

m3tatr0n

@johnpoz:

You sure you have the mask right, pfsense defaults to /32 when you create a new IP.. Sure you didn't put /32 vs /24??

Holy crap batman! That was it, the mask was set to 32 instead of 24.

Thanks a lot

johnpoz

Dude I brought that up much earlier in the thread.. ;)

" If he can not ping, then either clients blocking it not answering. He has a mask issue on this network between clients and pfsense. Or he has some sort of connectivity issue be it at layer 1 or 2."

Glad you got it sorted..

m3tatr0n

@johnpoz:

Dude I brought that up much earlier in the thread.. ;)

" If he can not ping, then either clients blocking it not answering. He has a mask issue on this network between clients and pfsense. Or he has some sort of connectivity issue be it at layer 1 or 2."

Glad you got it sorted..

I admit I am kinda overwhelmed with other stuff here, wearing too many hats ;)

Thanks so much for helping out.