Re: need help with ipfw nat to pf nat migration

2019-04-03 Thread Artem Viklenko via freebsd-net
04.04.19 07:30, Victor Sudakov пише: 1. pass in quick on $int_if inet proto tcp from $server to any flags S/SA keep state allow-opts tag SERVER 2. block return-rst out log quick on $mob_if inet proto tcp to any port 25 tagged SERVER You have already passed the packet with "quick" in

Re: need help with ipfw nat to pf nat migration

2019-04-03 Thread Victor Sudakov
Artem Viklenko via freebsd-net wrote: > >>> > >>> I'm trying to migrate some firewall rules from ipfw to pf. As pf does > >>> NAT first and filtering after NAT, I have a problem doing the following: > >>> > >>> 1. All 192.168.0.0/16 addresses should be translated to the real IP of > >>> the

[Bug 236983] bnxt(4) VLAN not operational unless explicit "ifconfig promisc" is used on the physical IF

2019-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983 --- Comment #13 from Stephen Hurd --- (In reply to punkt.de Hosting Team from comment #12) What are your values of dev.bnxt.0.ver.hwrm_fw and dev.bnxt.0.ver.hwrm_if? I don't think vlans were tested with hwrm interfaces greater than

determine interface txq/rxq for iflib queue kernel threads

2019-04-03 Thread Nick Rogers
Hello, I am wondering if there is a simple way to determine which iflib queue kernel threads belong to which network interface's rxq or txq. For example if in ps/top there is a busy thread such as "if_io_tqg_0" is it possible to get a mapping between thread name and interface rx / tx queue names

[Bug 236983] bnxt(4) VLAN not operational unless explicit "ifconfig promisc" is used on the physical IF

2019-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983 --- Comment #12 from punkt.de Hosting Team --- Nope :-) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list

[Bug 230465] ixl: not working in netmap mode

2019-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230465 Gong Teng <43381...@qq.com> changed: What|Removed |Added CC||43381...@qq.com ---

[Bug 236983] bnxt(4) VLAN not operational unless explicit "ifconfig promisc" is used on the physical IF

2019-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983 --- Comment #11 from Rodney W. Grimes --- The tcpdump looks good, thanks sysctl dev.bnxt.X.vlan_only=1 Try that instead of promisc and see if that makes a difference. -- You are receiving this mail because: You are the assignee for the

[Bug 236983] bnxt(4) VLAN not operational unless explicit "ifconfig promisc" is used on the physical IF

2019-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983 --- Comment #10 from punkt.de Hosting Team --- ifconfig bnxt0 -promisc packets stop ifconfig bnxt0 promisc packets resume Some SSH traffic: 5:18:48.715538 00:19:e7:94:5b:6a > 00:25:90:5f:9a:82, ethertype 802.1Q (0x8100), length 98: vlan

[Bug 236983] bnxt(4) VLAN not operational unless explicit "ifconfig promisc" is used on the physical IF

2019-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983 --- Comment #9 from Rodney W. Grimes --- (In reply to punkt.de Hosting Team from comment #6) Can you show me tagged vlan traffic via tcpdump with the command: tcpdump -n -l -i bnxt0 -e vlan Thanks, Rod -- You are receiving this mail

[Bug 236983] bnxt(4) VLAN not operational unless explicit "ifconfig promisc" is used on the physical IF

2019-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983 --- Comment #8 from Eugene Grosbein --- It is obviously driver bug. Does it continue to work if you disable promisc. mode after it's enabled once? -- You are receiving this mail because: You are the assignee for the bug.

[Bug 236983] bnxt(4) VLAN not operational unless explicit "ifconfig promisc" is used on the physical IF

2019-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983 --- Comment #7 from punkt.de Hosting Team --- This is my current config line: -vlanhwtag -vlanhwfilter -vlanmtu -vlanhwcsum -vlanhwtso -rxcsum -rxcsum6 -txcsum -txcsum6 up This is the resulting IF config after a complete reboot: bnxt0:

[Bug 236983] bnxt(4) VLAN not operational unless explicit "ifconfig promisc" is used on the physical IF

2019-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983 --- Comment #6 from punkt.de Hosting Team --- Yes, the switch is configured with switchport trunk native vlan 1001 VLAN 1001 is my "throwaway" VLAN for untagged traffic ... As I wrote: everything is working as expected the moment I

[Bug 236983] bnxt(4) VLAN not operational unless explicit "ifconfig promisc" is used on the physical IF

2019-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983 Rodney W. Grimes changed: What|Removed |Added CC||rgri...@freebsd.org ---

[Bug 236983] bnxt(4) VLAN not operational unless explicit "ifconfig promisc" is used on the physical IF

2019-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983 --- Comment #4 from Eugene Grosbein --- (In reply to punkt.de Hosting Team from comment #2) The order can matter. Try putting "up" to the end and disable all vlan* and *csum hardware offloads. -- You are receiving this mail because: You

[Bug 236983] bnxt(4) VLAN not operational unless explicit "ifconfig promisc" is used on the physical IF

2019-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983 --- Comment #3 from punkt.de Hosting Team --- This is the non-working case: bnxt0: flags=8843 metric 0 mtu 1500 options=e427ab ether 00:25:90:5f:9a:82 hwaddr 00:25:90:5f:9a:82 nd6 options=9 media:

[Bug 236983] bnxt(4) VLAN not operational unless explicit "ifconfig promisc" is used on the physical IF

2019-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983 --- Comment #2 from punkt.de Hosting Team --- Nope - that was my first attempt. "up promisc" in rc.conf works, "up -vlanhwtag -vlanhwfilter" doesn't. Kind regards Patrick -- You are receiving this mail because: You are the assignee for

[Bug 236983] bnxt(4) VLAN not operational unless explicit "ifconfig promisc" is used on the physical IF

2019-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983 Eugene Grosbein changed: What|Removed |Added CC||eu...@freebsd.org --- Comment

[Bug 236983] bnxt(4) VLAN not operational unless explicit "ifconfig promisc" is used on the physical IF

2019-04-03 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983 Kubilay Kocak changed: What|Removed |Added Priority|--- |Normal Status|New