On Wed, Mar 30, 2011 at 1:11 PM, - Dickie Bradford - <[email protected]> wrote: > On 3/26/2011 9:53 PM, - Dickie Bradford - wrote: >> >> Today I installed a New 2.0 RC1 pfsense build and then installed my >> backup config from 1.2.3. It went pretty well with minor issues that were >> easily fixed. One issue that is not easily fixed is this.... I have 3 >> interfaces, WAN (DHCP), LAN (192.168.20.1) and WirelessLan (192.168.21.1). >> WAN and LAN work perfect, the WirelessLan is acting strange to the fact >> that from the lan i can only ping a fewl of the active 192.168.21.0/24 >> address's ...BUT... I can ping all the active address's from the firewall >> with no problem. >> >> example: >> >> firewall can ping: 192.168.21.2, 192.168.21.3, 192.168.21.48, >> 192.168.21.49, 192.168.21.223 >> >> Lan & IPSEC can only ping: 192.168.21.48, 192.168.21.49 >> >> I have the rule to pass everything on all interfaces just for the sake of >> trying to track this issue down. BOGON's and Private IP blocking are >> unchecked on all interfaces. >> >> I am at a loss of what is wrong >> >> Thnx >> > Here is some additional information on this > > only IP's directly connected to the switch that is connected to the pfsense > box cannot be pinged from lan or ipsec, but remote IP's that run accross > wireless brigdes thru the switch can be pinged. I have changed the switch > to make sure it is not an issue, but the problem still persists. >
Get a packet capture on the interface the traffic is entering, make sure it's showing there, then on the interface it's leaving, see that it's leaving there. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
