Hi again, On Tue, Nov 06, 2012 at 05:45:52AM +1100, jerome alet wrote: > > ---------------------------------------- > > From: Mikey van der Worp <[email protected]> > > Sent: Mon Nov 05 15:29:04 NCT 2012 > > To: pfSense support and discussion <[email protected]> > > Subject: Re: [pfSense] Strange problem after auto update > > > > According to the details it looks like Ichmp echo is blocked. Does it do > > the same pinging to google etc? > > Sorry, forgot to add that I don't see any rejected packet in our > central syslog server, for any of these two pfSense boxes.
I've done additional tests this morning with the "8.3-RELEASE-p4 #1: Sun Nov 4 19:45:08 EST 2012" snapshot. BTW ICMP is not blocked because pinging the slave from any other host works fine, and now I've found that pinging from the slave to some machines on some interfaces (only the ones with public IPs it seems, although I don't understand why). work. And pinging the IP address of www.google.com works fine too. But pinging from slave to LAN doesn't work, despite the "Default allow LAN to any rule" and an additional explicit ICMP allow all rule. And now I've just noticed this : if I disable CARP on the slave, all works fine again from the slave as far as ping and DNS are concerned (the only tests I've done so far). As soon as I re-enable CARP on the slave, the slave encounters the same problem as already reported : no ping to LAN and other "internal" networks, and no DNS either. Again, if I restore my full backup from September 27th, all is perfectly fine for the slave. And of course all this without modifying anything to the configuration... Any other idea ? TIA -- Jérôme Alet - <[email protected]> - Direction du Système d'Information Université de la Nouvelle-Calédonie - BPR4 - 98851 NOUMEA CEDEX Tél : +687 290081 Fax : +687 254829 _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
