[Bug 148807] [panic] "panic: sbdrop" and "panic: sbsndptr: sockbuf _ and mbuf _ clashing" (8.1-RELEASE/10.1-STABLE/11-CURRENT)

2017-03-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=148807 --- Comment #43 from Kubilay Kocak --- @All For issues where the 'described problem' and the 'thing(s) that need to be changed' are not one and the same, to retain all history/contextual information and not cause confusion (renaming titles,

[Bug 173444] socket: IPV6_USE_MIN_MTU and TCP is broken

2017-03-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173444 --- Comment #13 from ma...@isc.org --- (In reply to Andrey V. Elsukov from comment #11) Read the words "effective MTU" that I quoted. The "effective MTU" is 1280 with this option set. -- You are receiving this mail because: You are the a

[Bug 173444] socket: IPV6_USE_MIN_MTU and TCP is broken

2017-03-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173444 Kubilay Kocak changed: What|Removed |Added Attachment #129462|application/octet-stream|text/plain mime type|

[Bug 173444] socket: IPV6_USE_MIN_MTU and TCP is broken

2017-03-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173444 Kubilay Kocak changed: What|Removed |Added Attachment #129461|0 |1 is patch|

[Bug 173444] socket: IPV6_USE_MIN_MTU and TCP is broken

2017-03-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173444 Kubilay Kocak changed: What|Removed |Added Summary|[socket] [patch]|socket: IPV6_USE_MIN_MTU

Re: OpenVPN and policy routing

2017-03-30 Thread Victor Sudakov
Michael Sierchio wrote: > I use different FIBs in the ipfw ruleset to accomplish policy based > routing, including via a tun interface. I've just found out that even when tun0 is in fib 0, you can use it as a gateway from a different fib, and it works: root@km:~ # netstat -rn -4 -F1 Routing table

[Bug 173444] [socket] [patch] IPV6_USE_MIN_MTU and TCP is broken

2017-03-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173444 --- Comment #12 from Andrey V. Elsukov --- (In reply to marka from comment #10) > (In reply to Andrey V. Elsukov from comment #8) > So what! Most DNS/TCP response is a few of packets. What does it > matter if it is the 3 or 4 packets. Zo

[Bug 173444] [socket] [patch] IPV6_USE_MIN_MTU and TCP is broken

2017-03-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173444 --- Comment #11 from Andrey V. Elsukov --- (In reply to marka from comment #9) > (In reply to Andrey V. Elsukov from comment #7) > RFC 6691 > > o As a result, when the effective MTU of an interface varies, TCP >SHOULD use the smallest

[Bug 173444] [socket] [patch] IPV6_USE_MIN_MTU and TCP is broken

2017-03-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173444 --- Comment #10 from ma...@isc.org --- (In reply to Andrey V. Elsukov from comment #8) So what! Most DNS/TCP response is a few of packets. What does it matter if it is the 3 or 4 packets. What matters is avoiding PMTUD as it is NOT reliab

[Bug 173444] [socket] [patch] IPV6_USE_MIN_MTU and TCP is broken

2017-03-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173444 --- Comment #9 from ma...@isc.org --- (In reply to Andrey V. Elsukov from comment #7) RFC 6691 o As a result, when the effective MTU of an interface varies, TCP SHOULD use the smallest effective MTU of the interface to calculate the

[Bug 173444] [socket] [patch] IPV6_USE_MIN_MTU and TCP is broken

2017-03-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173444 --- Comment #8 from Andrey V. Elsukov --- And this is what always pisses me off. If we have 10/50/100G link with 9k MTU, bind always does IPv6 fragmentation due to this option. -- You are receiving this mail because: You are the assignee

[Bug 173444] [socket] [patch] IPV6_USE_MIN_MTU and TCP is broken

2017-03-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173444 Andrey V. Elsukov changed: What|Removed |Added CC||a...@freebsd.org --- Comment #

Re: OpenVPN and policy routing

2017-03-30 Thread Michael Sierchio
I use different FIBs in the ipfw ruleset to accomplish policy based routing, including via a tun interface. - M On Thu, Mar 30, 2017 at 9:24 AM, Andrea Venturoli wrote: > On 03/30/17 09:46, Victor Sudakov wrote: > > Will "ipfw fwd" do the trick? I could "ipfw fwd" the packets into the >> tun0 i

Re: OpenVPN and policy routing

2017-03-30 Thread Andrea Venturoli
On 03/30/17 09:46, Victor Sudakov wrote: Will "ipfw fwd" do the trick? I could "ipfw fwd" the packets into the tun0 interface, but will OpenVPN understand that? Never tried this, sorry. bye av. ___ freebsd-net@freebsd.org mailing list https

!!!! Greetings !!!!

2017-03-30 Thread kong khemara
Hello, I am Barr Kong Khemara, I humbly ask if you are related to my client who died couple of years ago in a car accident here in my country Cambodia. I wish to also inquire if it is possible to have different families with the same last name as yours by coincidence who do not share the same co

Re:Follow up: Embedded Systems Users List

2017-03-30 Thread deborah . perry
Hi, Hope you had a chance to review my previous email. Please let me know if you would be interested in reviewing a sample of your target audience. Thank you, hope to hear from you. Thanks & regards, *Deborah Perry* Marketing Analyst __

[Bug 173444] [socket] [patch] IPV6_USE_MIN_MTU and TCP is broken

2017-03-30 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=173444 --- Comment #6 from ma...@isc.org --- (In reply to Hiren Panchasara from comment #5) My test system died years ago but I believe that it still is a problem. It should be trivial to check. create a IPv6 TCP socket. set IPV6_USE_MIN_MTU=1 us

Re: OpenVPN and policy routing

2017-03-30 Thread Victor Sudakov
Andrea Venturoli wrote: > > > > Anyone experienced with OpenVPN on FreeBSD? > > > > What would be the best way to policy route a network into OpenVPN? A > > routing decision must be based on the src IP address, not the dst IP > > address. > > > > Imagine an OpenVPN client with 3 interfaces: fxp0

Re: OpenVPN and policy routing

2017-03-30 Thread Andrea Venturoli
On 03/30/17 05:22, Victor Sudakov wrote: Dear Colleagues, Anyone experienced with OpenVPN on FreeBSD? What would be the best way to policy route a network into OpenVPN? A routing decision must be based on the src IP address, not the dst IP address. Imagine an OpenVPN client with 3 interfaces: