ah, I see. I will try this in the morning and report back.
-- Jason T. Slack-Moehrle On Wednesday, February 15, 2012 at 6:12 PM, Yehuda Katz wrote: > On Wed, Feb 15, 2012 at 8:57 PM, Jason T. Slack-Moehrle > <[email protected] (mailto:[email protected])> wrote: > > > > Can anyone shed some light on what is going on? I just cannot simply > > > > get to the server after doing this. > > > > > > We had a similar issue on Verizon. We allowed all ICMP PINGas through the > > > firewall and tried to ping each address. The primary (assigned to the > > > pfsense) responded and the others did not. It seems that the pfSense was > > > not properly picking up the ARP requests unless is was the primary IP. > > > (We did some other testing by connecting a computer to act as a packet > > > sniffer in between the NOC and the pfSense. We never got around to > > > figuring out why it did not work, since we found a workaround.) > > > We "solved" the problem by setting the primary interface IP to each of > > > our IPs in turn and pinged it and then fixing the Virtual IP > > > configuration. > > > We only had to do that once and it has run fine ever since. > > > > > > I dont follow what this means exactly and how to test this on my setup to > > see if it solves my problem. > > Change the WAN IP to one of you other assigned addresses, save, apply, repeat > until you have returned to your original address. > I would give you screenshots, but I am using my development pfSense VM for > trying to fix a different bug, so it is unusable right now. > > - Y > _______________________________________________ > List mailing list > [email protected] (mailto:[email protected]) > http://lists.pfsense.org/mailman/listinfo/list _______________________________________________ List mailing list [email protected] http://lists.pfsense.org/mailman/listinfo/list
