>On Mon, Nov 15, 2010 at 9:57 PM, Evgeny Yurchenko
wrote:
>>
>> I do not know a lot about Hyper-v but in VMWare for instance you can
>> block frames with 'faked' mac-addresses. Probably you hit the same
>> problem as CARP-packets have MAC-addresses 'not real' but specifically
crafted.
>
>I'm sur
On Mon, Nov 15, 2010 at 9:57 PM, Evgeny Yurchenko wrote:
>
> I do not know a lot about Hyper-v but in VMWare for instance you can block
> frames with 'faked' mac-addresses. Probably you hit the same problem as
> CARP-packets have MAC-addresses 'not real' but specifically crafted.
I'm sure that's
On 10-11-16 12:19 PM, Dimitri Rodis wrote:
On 10-11-15 09:22 PM, Dimitri Rodis wrote:
I recently migrated a pfSense virtual machine (version 1.2.2) that was
running flawlessly on Hyper-V (first release) with 2 additional CARP
IP addresses on the WAN interface for about 16 months. Over the
we
On 10-11-15 09:22 PM, Dimitri Rodis wrote:
I recently migrated a pfSense virtual machine (version 1.2.2) that was
running flawlessly on Hyper-V (first release) with 2 additional CARP IP
addresses on the WAN interface for about 16 months. Over the weekend, I
migrated that virtual machine over t
On 10-11-15 09:22 PM, Dimitri Rodis wrote:
I recently migrated a pfSense virtual machine (version 1.2.2) that was
running flawlessly on Hyper-V (first release) with 2 additional CARP
IP addresses on the WAN interface for about 16 months. Over the
weekend, I migrated that virtual machine over
