Yes your right. I have read all the posts and i have the same problem with pfsese 1.0.1 and MonoWall 1.3b1 & 1.3B2 (based on FreeBSD 6.2RC1). The Monowall 1.2 based on FreeBSD 4.11 doesn't have this "feature".
Thanx Cesar A. Vergara Buenaventura MMP BU Sistemas Tel : (51) 326-4957 Fax : (51) 326-4957 Cel : 95404463 RPM : #221593 http://www.mitsuimaquinarias.com -----Original Message----- From: Chris Daniel [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 02, 2007 3:52 PM To: [email protected] Subject: Re: [pfSense Support] Static Routes not functioning Cesar Vergara wrote: > I have this setup : > > Main Office : 172.16.0.0/22 > Default Gateway : 172.16.0.1 (pfsense) > > Branches : 192.168.2.0, 3.0, 4.0, etc. > Default gateway : 192.168.2.1, 3.1, 4.1, etc. > > I have setup this static routes on pfsense ( as done previously with > monowall) > > Network : 192.168.2.0/24, 3.0/24, etc > Gateway : 172.16.0.2 > > But when i run the command : tracert 192.168.2.25 it jumps from > 172.16.0.1 to my external ip and doen't jumpos to 172.16.0.2 > Assuming you are running the traceroute from the "main office subnet", I think these static routes would be accomplishing their functions through ICMP redirects. I recall reading something about ICMP redirects mussed up in pfsense due to some pf/FreeBSD bugs ... http://marc2.theaimsgroup.com/?l=pfsense-support&m=116336150824274&w=2 maybe. Anyone else? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
