Re: [pfSense Support] ok throw a bucket of ice water on me and wake me up

2006-12-11 Thread Bill Marquette
This was most likely due to the gratuitous arps when the machines booted. It's possible that the router(s) cached them and issued ICMP redirects. I can see how it could happen and yep, you're correct, it'd work like ass ;) --Bill On 12/11/06, mOjO <[EMAIL PROTECTED]> wrote: either that or its

Re: [pfSense Support] ok throw a bucket of ice water on me and wake me up

2006-12-10 Thread mOjO
either that or its the switch? ever run two completely different subnets (and networks) on the same unmanaged switch? (of course this begs the question WHY?) but well... it has some interesting effects. of course it works fine for each subnet within themselves but when trying to contact one ne

Re: [pfSense Support] ok throw a bucket of ice water on me and wake me up

2006-12-09 Thread Bill Marquette
Probably those machines had 192.168.125.65's mac address still cached. Knowing what the MAC was, they didn't need to do an arp lookup for their default gateway to send the traffic on. Expect those machines to stop working before too long ;-P --Bill On 12/9/06, Jonathan Horne <[EMAIL PROTECTED]>

[pfSense Support] ok throw a bucket of ice water on me and wake me up

2006-12-09 Thread Jonathan Horne
i previously had 2 sites, both with pfsense firewalls. site a - 192.168.125.0/26 site b - 192.168.125.64/26 i recently did away with site a, and since those ips were no longer in use, i decided to change my site b from a /26 to a /25. so i started with the pfsense box. it ip was previously 19