Sorry, This particular issue turned out to be a typo in the virtual IP address. It was trying to do right but of course would not work. As for why the WAN connection did not work correctly when I tested using the interface address, I am not sure. I deleted and recreated all rules and forwards for that interface many times. After I made all the others work (which only took a couple of minutes), I redid the rules for WAN one more time. It started working better. Then I noticed the typo for 2 of the 5 IP addresses set for the device. The only remaining issues I have are DNS and a possible bug. The caching DNS server/service of pfsense is not working. It is refusing the clients that try to get DNS info from it. The pfsense router is unable to resolve any DNS names for the ping command either. The DNS servers are set for the interface. The same DNS servers are what the of clients on the network had to be set to and are working. The bug issue is a feature that is now missing. For the firewall/gateway rules for the LAN interface, you used to be able to add a rule based on the destination port. That is not longer on the page. You can use source port but that is useless in most cases. I need to direct outgoing traffic out different WANs based on the destination port. This worked in the 11-29-06 version I upgraded from. Thank you ffor your time. Again I apologize for my email behavior. It was late and I was running pretty low on fuel at that point.
Robert On Friday 30 March 2007 02:04, Holger Bauer wrote: > Please don't switch the topics of your mails concerning the same issue > constantly. It's hard to follow/track a vonversation this way. Thank > you. > > Holger > > > -----Original Message----- > > From: Robert Goley [mailto:[EMAIL PROTECTED] > > Sent: Friday, March 30, 2007 2:42 AM > > To: support@pfsense.com > > Subject: [pfSense Support] NAT Mapping failure > > > > I did find that 1-1 mapping is breaking the outgoing connect > > of the machine that is being mapped. I verified this by > > switching a 1-1 NAT mapping between to machines. I was able > > to access before the map and could not after. on the other > > machine that had the map to start with, I could not access out. > > After switch the map to another machine I was able to access > > it from this machine. I have deleted all NAT port forward > > for the WAN interface and recreated 2 for testing SSH and > > HTTP. Neither work. The same portforwards for OPT1 and OPT2 > > work. The firewall rules were autocreated by pfSense. I an > > using any for the from IP addresses and ports. > > > > --------------------------------------------------------------------- > > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
