[Bug 217391] [ipfw] [panic] erroneous ipfw rule triggers KASSERT

2017-02-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217391 Mark Linimon changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org

Re: dummynet loses ports mask bits

2017-02-28 Thread Julian Elischer
On 1/3/17 1:54 am, Julian Elischer wrote: On 1/3/17 1:46 am, Luigi Rizzo wrote: On Tue, Feb 28, 2017 at 9:27 AM, Julian Elischer wrote: In the following example it appears that the mask bits for the port number are lost. before I raise a bug.. is there anyone who can see

Re: dummynet loses ports mask bits

2017-02-28 Thread Julian Elischer
On 1/3/17 1:46 am, Luigi Rizzo wrote: On Tue, Feb 28, 2017 at 9:27 AM, Julian Elischer wrote: In the following example it appears that the mask bits for the port number are lost. before I raise a bug.. is there anyone who can see that I am doing anything wrong? I'm not

Re: dummynet loses ports mask bits

2017-02-28 Thread Julian Elischer
On 1/3/17 1:27 am, Julian Elischer wrote: In the following example it appears that the mask bits for the port number are lost. before I raise a bug.. is there anyone who can see that I am doing anything wrong? just realised I'm using wrong syntax need "mask dst-port" fooled by the fact

Re: dummynet loses ports mask bits

2017-02-28 Thread Luigi Rizzo
On Tue, Feb 28, 2017 at 9:27 AM, Julian Elischer wrote: > In the following example it appears that the mask bits for the port number > are lost. > before I raise a bug.. is there anyone who can see that I am doing anything > wrong? > > I'm not sure what the q131053 stuff is

dummynet loses ports mask bits

2017-02-28 Thread Julian Elischer
In the following example it appears that the mask bits for the port number are lost. before I raise a bug.. is there anyone who can see that I am doing anything wrong? I'm not sure what the q131053 stuff is about either, but.. -- FreeBSD

[Bug 216719] panic: ipfw_check_frame: unknown retval - while trying to ipfw nat incoming packet without translation state (can be L2 firewall related)

2017-02-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216719 smi...@nimnet.asn.au changed: What|Removed |Added CC||smi...@nimnet.asn.au ---

[Bug 216719] panic: ipfw_check_frame: unknown retval - while trying to ipfw nat incoming packet without translation state (can be L2 firewall related)

2017-02-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216719 --- Comment #1 from b...@kobyla.org --- Adding the "not layer2" to ipfw nat rule helps to avoid this problem -- You are receiving this mail because: You are the assignee for the bug. ___