• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

connectivity problem with monowall as firewall

K

kensaundm31

n00b
Joined
Nov 13, 2010
Messages
1
Hi,

I have a 3 subnet network in server 2003:

PUBLIC 192.168.1.x (vmware Bridged with host)
DMZ 192.168.2.x (vmware LAN seg 1)
PRIVATE 192.168.3.x (vmware LAN seg 2)

initialy the monowall vm has 2 vm nics both bridged with host I made the first one of these LAN 2 so I can make the LAN interface 192.168.3.x.

I left the other (WAN) as bridgedtohost. I set the address to static and 192.168.1.5 with g/w 192.168.1.1 which is my physical router.

I have 2 static routes on the physical router that send all traffic for .2 and .3 subnets to 192.168.1.5 as gateway.

here is a pic to show:




I set all pass rules (any,any,any) on wan/lan/dmz. to make monowall purely a router.

almost everything now has connectivety.

My host pc (196.168.1.2) can ping monowall wan (192.168.1.5) BUT my host pc cannot ping anything after 192.168.1.5, ie nothing on the dmz or private lan.

So how come monowall cannot forward this even with no firewall restrictions?

Anyone have an idea?

Cheers.
 
You must log in or register to reply here.
Back
Top