On Wed, 23 Dec 2015 10:08:05 +0800, bycn82 wrote:
> Cc: "freebsd-ipfw@freebsd.org" ,
> Ganbold Tsagaankhuu
> Subject: Re: layer2 ipfw fwd
>
> Interesting, that means in order to filter the layer2 traffic with layer3
> filters. it will unpack the ether frame and get the packets. at least
Interesting, that means in order to filter the layer2 traffic with layer3
filters. it will unpack the ether frame and get the packets. at least the
packet header.
so why ipfw doesnt support this? Ipfw3 will support this!
On Wednesday, 23 December 2015, Julian Elischer wrote:
> On 22/12/2015 10
On 22/12/2015 10:57 PM, bycn82 wrote:
Hi Julian,
Thanks for the explanation.
Since it is on layer2, that means we can differentiate traffic by MAC or
other layer2 filters only.
e.g , forward the traffic when the type is 0x800 and destination MAC is
xx:yy:zz
I meant the accuracy is a big co
Hi Julian,
Thanks for the explanation.
Since it is on layer2, that means we can differentiate traffic by MAC or
other layer2 filters only.
e.g , forward the traffic when the type is 0x800 and destination MAC is
xx:yy:zz
I meant the accuracy is a big concern.
Regards,
Bill Yuan
On 21 Decem
