FYI, if anyone was curious. Whatever the problem was, it was being hampered by a bad rule configured on one side of the network. The rule to negate the load-balancer for internal and IPsec networks was mis-set. I think I am having a problem with Chrome as well with some of the selection dialogs in pfSense. I can't be sure.
The problem began with a 2.0-RC3 build of pfSense, which was working yesterday. It stopped for not apparent reason. We identified the missing negation rule today, and then when we put it in, somehow we had the CiDR set wrong. Jim from support logged in and took a look. He identified the problem very quickly. So, Thanks for the assistance. Sincerely, joshua On Thu, Dec 8, 2011 at 09:49, Joshua Schmidlkofer <[email protected]> wrote: > We just purchased commercial support. So, even if we have a Stupid > Problem™, I know that it's money towards an excellent cause. > > > On Thu, Dec 8, 2011 at 09:42, Joshua Schmidlkofer <[email protected]> wrote: >> Thanks for the replies. I did setup rules this morning for just such >> a thing. I left the gateway as "default". I had only run into this >> problem with IPsec tunnels, but it seemed to be a good idea. However, >> this did not fix my problem. >> >> I have tcpdump'd on all interfaces, the packets appear not to be >> headed anywhere. >> >> Sincerely, >> Joshua >> >> On Thu, Dec 8, 2011 at 09:33, Seth Mos <[email protected]> wrote: >>> HI, >>> >>> Op 8 dec 2011, om 18:27 heeft Joshua Schmidlkofer het volgende geschreven: >>> >>>> Yesterday, for no discernible reason, new connections ceased, in one >>>> direction between two local subnets. I have two interfaces, alc0 to >>>> 10.2.0.0/16 (BuildingA), and re2 to 10.3.0.0/16 (BuildingB). >>>> >>>> My pfSense box is a single box, with multiple internet uplinks, and is >>>> the default gateway for both networks. We have no filtering between >>>> 10.3.0.0 and 10.2.0.0. They are in another building and connected to >>>> us via high speed wireless. >>>> >>>> At some point yesterday, 10.3.0.0 stopped being able to initiate >>>> connections to hosts on 10.2.0.0. BuildingA may create new >>>> connections to BuildingB without incident. BuildingB may not connect >>>> to BuildingA at all. The packets enter PFsense, I can't get them to >>>> log at all, tcpdump shows them. Once in, they never come out. There >>>> is no log of them going anywhere. They simply cease. >>> >>> Added a firewall rule with a gateway for policy routing without making a >>> exception rule for the directly connected building A? >>> >>> You need to make sure that there is a rule without a gateway to building A >>> and vice versa. >>> >>> This is one of the fixes in 2.0.1. >>> >>> Cheers, >>> >>> Seth >>> >>> _______________________________________________ >>> List mailing list >>> [email protected] >>> http://lists.pfsense.org/mailman/listinfo/list _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
