Problems with FreeBSD (amd64 stable/11) router

2016-12-05 Thread Chris Ross

 Hello all.  I recently replaced my router with a FreeBSD/11 box (stable/11 
r308579).  I am running a lagg device across two bce’s, and 802.1q vlan 
interfaces atop lagg0.  I’m using pf to NAT/filter out through a single outside 
IP address.

 I’m having the following problem.  Some devices appear to be having trouble 
passing traffic.  Of course, I first assumed I was doing something wrong with 
my pf filters, but I believe now that’s not the problem.  One client machine (a 
TiVo Roamio) that produces a failure reliably, so I’ve been using it for 
testing, is showing that during a TCP session, which starts up fine, in the 
middle of a POST operation to an outside server, there are 1500 byte packets.  
These packets have the DF bit in the IP header, and then never show up on the 
external interface (vlan0).  Smaller packets in the same TCP stream do.  But, 
I’m also not seeing the ICMP from the router back to the client telling it that 
it cannot send the packet.

 I have tried all sorts of changes to my pf rules, including now allowing all 
ICMP unconditionally on all interfaces (pass out log quick inet proto icmp 
all).  I have packet traces during the failed communication across pflog0, 
vlan0 (external network) and vlan7 (internal network).  I’d be happy to answer 
any questions, or provide the traces off-list.

 Does anyone have any idea what I’ve missed?  Thank you very much for your help.

- Chris

___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

[Bug 213257] Crash in IGB driver with ALTQ

2016-12-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213257

e...@norma.perm.ru changed:

   What|Removed |Added

 CC||e...@norma.perm.ru

--- Comment #11 from e...@norma.perm.ru ---
I have two machines, both with igb(4), ALTQ and panics after an upgrade to
11.0-RELEASE. kern/213832, reported by me, may be related to this issue. Is
anyone looking into this ?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: Problems with FreeBSD (amd64 stable/11) router

2016-12-05 Thread Ryan Stone
What's the MTU on the bce and vlan interfaces?  Does the bce interface show
VLAN_MTU option set (in ifconfig)?

On Mon, Dec 5, 2016 at 10:00 AM, Chris Ross 
wrote:

>
>  Hello all.  I recently replaced my router with a FreeBSD/11 box
> (stable/11 r308579).  I am running a lagg device across two bce’s, and
> 802.1q vlan interfaces atop lagg0.  I’m using pf to NAT/filter out through
> a single outside IP address.
>
>  I’m having the following problem.  Some devices appear to be having
> trouble passing traffic.  Of course, I first assumed I was doing something
> wrong with my pf filters, but I believe now that’s not the problem.  One
> client machine (a TiVo Roamio) that produces a failure reliably, so I’ve
> been using it for testing, is showing that during a TCP session, which
> starts up fine, in the middle of a POST operation to an outside server,
> there are 1500 byte packets.  These packets have the DF bit in the IP
> header, and then never show up on the external interface (vlan0).  Smaller
> packets in the same TCP stream do.  But, I’m also not seeing the ICMP from
> the router back to the client telling it that it cannot send the packet.
>
>  I have tried all sorts of changes to my pf rules, including now allowing
> all ICMP unconditionally on all interfaces (pass out log quick inet proto
> icmp all).  I have packet traces during the failed communication across
> pflog0, vlan0 (external network) and vlan7 (internal network).  I’d be
> happy to answer any questions, or provide the traces off-list.
>
>  Does anyone have any idea what I’ve missed?  Thank you very much for your
> help.
>
> - Chris
>
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

[Differential] D8637: buf_ring.h: fix memory order issues.

2016-12-05 Thread alc (Alan Cox)
alc added a comment.


  Have you looked at https://reviews.freebsd.org/D1945, in particular, the most 
recent postings by sbahra_repnop.org?  It's not clear to me that these changes 
will address the problem described in sbahra_repnop.org's postings.  That said, 
your proposed changes do correct the most obvious remaining issues with the use 
of acquires and releases in this code.

INLINE COMMENTS

> buf_ring.h:78
>   do {
> + cons_tail = atomic_load_acq_32(&br->br_cons_tail);
>   prod_head = br->br_prod_head;

Was there a reason for moving this load?

> buf_ring.h:98
>*/   
>   while (br->br_prod_tail != prod_head)
>   cpu_spinwait();

You may need to use a load acquire on br_prod_tail here to establish an 
unbroken synchronizes-with chain between the thread that enqueues an item X and 
the thread that later dequeues it if there are other concurrent enqueues.

> buf_ring.h:117
>   do {
> + prod_tail = atomic_load_acq_32(&br->br_prod_tail);
>   cons_head = br->br_cons_head;

Was there a reason for moving this load?

> buf_ring.h:159
>   prod_tail = atomic_load_acq_32(&br->br_prod_tail);
> - 
> - cons_next = (cons_head + 1) & br->br_cons_mask;
> -#ifdef PREFETCH_DEFINED
> - cons_next_next = (cons_head + 2) & br->br_cons_mask;
> -#endif
> + cons_head = br->br_cons_head;
>   

Was there a reason for swapping the order of the preceding loads?

> buf_ring.h:174
>   buf = br->br_ring[cons_head];
> + br->br_cons_head = cons_next;
>  

Was there a reason for swapping the order of the preceding loads?

REVISION DETAIL
  https://reviews.freebsd.org/D8637

EMAIL PREFERENCES
  https://reviews.freebsd.org/settings/panel/emailpreferences/

To: oleg, kmacy, kib, alc
Cc: emaste, freebsd-net-list
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: Problems with FreeBSD (amd64 stable/11) router

2016-12-05 Thread Chris Ross

> On Dec 5, 2016, at 11:59, Ryan Stone  wrote:
> 
> What's the MTU on the bce and vlan interfaces?  Does the bce interface show 
> VLAN_MTU option set (in ifconfig)?

  I had manually set these to try to work out the problem earlier in my 
experimentation, but am now back (unless I missed something) to the natural 
MTUs on all interfaces.  The vlan’s all show 1496, and the bee’s (and lagg0) 
show 1500.  The options on each of the bce’s show VLAN_MTU, and a few other 
VLAN_ options.

- Chris


> On Mon, Dec 5, 2016 at 10:00 AM, Chris Ross  wrote:
> 
>  Hello all.  I recently replaced my router with a FreeBSD/11 box (stable/11 
> r308579).  I am running a lagg device across two bce’s, and 802.1q vlan 
> interfaces atop lagg0.  I’m using pf to NAT/filter out through a single 
> outside IP address.
> 
>  I’m having the following problem.  Some devices appear to be having trouble 
> passing traffic.  Of course, I first assumed I was doing something wrong with 
> my pf filters, but I believe now that’s not the problem.  One client machine 
> (a TiVo Roamio) that produces a failure reliably, so I’ve been using it for 
> testing, is showing that during a TCP session, which starts up fine, in the 
> middle of a POST operation to an outside server, there are 1500 byte packets. 
>  These packets have the DF bit in the IP header, and then never show up on 
> the external interface (vlan0).  Smaller packets in the same TCP stream do.  
> But, I’m also not seeing the ICMP from the router back to the client telling 
> it that it cannot send the packet.
> 
>  I have tried all sorts of changes to my pf rules, including now allowing all 
> ICMP unconditionally on all interfaces (pass out log quick inet proto icmp 
> all).  I have packet traces during the failed communication across pflog0, 
> vlan0 (external network) and vlan7 (internal network).  I’d be happy to 
> answer any questions, or provide the traces off-list.
> 
>  Does anyone have any idea what I’ve missed?  Thank you very much for your 
> help.
> 
> - Chris
> 
> ___
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
> 

___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

[Bug 213257] Crash in IGB driver with ALTQ

2016-12-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213257

--- Comment #12 from ncrog...@gmail.com ---
If you're not actually using ALTQ (i.e., in a loaded PF configuration), I would
 suggest simply removing ALTQ from your kernel config and building a new
kernel.

If you ARE utilizing altq with an igb interface, try setting
hw.igb.num_queues=1 in loader.conf. ALTQ isn't able to utilize more than one
interface queue anyways.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 213257] Crash in IGB driver with ALTQ

2016-12-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213257

--- Comment #13 from ncrog...@gmail.com ---
This issue is also discussed here:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208409

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 214832] if_pflog subrulenr incorrectly set

2016-12-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214832

--- Comment #3 from commit-h...@freebsd.org ---
A commit references this bug:

Author: kp
Date: Mon Dec  5 21:52:11 UTC 2016
New revision: 309563
URL: https://svnweb.freebsd.org/changeset/base/309563

Log:
  pflog: Correctly initialise subrulenr

  subrulenr is considered unset if it's set to -1, not if it's set to 1.
  See contrib/tcpdump/print-pflog.c pflog_print() for a user.

  This caused incorrect pflog output (tcpdump -n -e -ttt -i pflog0):
rule 0..16777216(match)
  instead of the correct output of
rule 0/0(match)

  PR:   214832
  Submitted by: andywh...@gmail.com

Changes:
  head/sys/netpfil/pf/if_pflog.c

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


Re: File duplication on NFSv4 exported ZFS filesystems to centos client

2016-12-05 Thread Rick Macklem
Jordan Ladora wrote:

>Ahh!! Thank you!
>
>Previously, I tried exporting just the top-level zfs, but then couldn't
>access the zfs filesystems inside from the client, but listing *all* of
>them in /etc/exports and only mounting the top-level zfs works perfectly.
>
>Just wondering, by the way, if you knew why 'echo' doesn't work on NFS
shares?
How does it "not work?". I did a trivial test with the FreeBSD client and it 
seemed
to work.

If you run a test of "echo" while running the following on the FreeBSD server 
and
then email me the out.pcap file as an attachment, I can take a look at it.
# tcpdump -s 0 -w out.pcap host 

rick
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Differential] D8637: buf_ring.h: fix memory order issues.

2016-12-05 Thread oleg (Oleg Bulyzhin)
oleg added a comment.


  In https://reviews.freebsd.org/D8637#180625, @alc wrote:
  
  > Have you looked at https://reviews.freebsd.org/D1945, in particular, the 
most recent postings by sbahra_repnop.org?  It's not clear to me that these 
changes will address the problem described in sbahra_repnop.org's postings.  
That said, your proposed changes do correct the most obvious remaining issues 
with the use of acquires and releases in this code.
  
  
  Yes, i've looked at https://reviews.freebsd.org/D1945 but somehow i've missed 
sbahra_repnop.org's comments. Since i was trying to fix different issue 
(https://lists.freebsd.org/pipermail/freebsd-net/2013-December/037265.html) and 
remove my own rmb() hack the problem described by sbahra_repnop.org is still 
here. I'll post updated diff tomorrow.

INLINE COMMENTS

> alc wrote in buf_ring.h:98
> You may need to use a load acquire on br_prod_tail here to establish an 
> unbroken synchronizes-with chain between the thread that enqueues an item X 
> and the thread that later dequeues it if there are other concurrent enqueues.

AFAIK 'synchronizes-with chains' are about RMW operations in between 
load_acq/store_rel sequence. Can you explain why load_acq is necessary here? I 
think producer should not care about visibility of br->br_ring[prod_head] 
stores of other producers.
Correct order of our own stores guaranteed by store_rel(&br->br_prod_tail) (and 
load_acq() in consumer).

REVISION DETAIL
  https://reviews.freebsd.org/D8637

EMAIL PREFERENCES
  https://reviews.freebsd.org/settings/panel/emailpreferences/

To: oleg, kmacy, kib, alc
Cc: emaste, freebsd-net-list
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 208409] [PATCH] igb and ALTQ

2016-12-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208409

Kubilay Kocak  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2132
   ||57

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 213257] Crash in IGB driver with ALTQ

2016-12-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213257

Kubilay Kocak  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2084
   ||09
  Flags||mfc-stable9?,
   ||mfc-stable10?,
   ||mfc-stable11?
   Keywords|IntelNetworking |crash, needs-qa
 Status|New |Open

--- Comment #14 from Kubilay Kocak  ---
For anyone who is experiencing this crash/panic, please include as a single
plaintext file attachment (not as a comment):

- Crash backtrace (gdb -> bt)
- Full version (uname -a) of the system
- pciconf -lv output

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"


[Bug 214832] if_pflog subrulenr incorrectly set

2016-12-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214832

Kubilay Kocak  changed:

   What|Removed |Added

  Flags||maintainer-feedback?(kp@fre
   ||ebsd.org), mfc-stable9?,
   ||mfc-stable10?,
   ||mfc-stable11?
   Assignee|freebsd-net@FreeBSD.org |k...@freebsd.org
URL||https://svnweb.freebsd.org/
   ||base/releng/11.0/sys/netpfi
   ||l/pf/if_pflog.c?view=markup
   ||#l224
 Status|New |In Progress
 CC||freebsd-net@FreeBSD.org

--- Comment #4 from Kubilay Kocak  ---
Assign to committer resolving.

Are stable/{11,10,9} affected?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"