https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #43 from Roger Pau Monné ---
(In reply to Ricardo from comment #42)
No, those patches have not been committed to FreeBSD upstream, partly to my
lack of nagging, partly because I wasn't sure this was the best way to fix it
(as
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #42 from Ricardo ---
Thank you very much for your replies Roger.
I will try to take it to the Netgate/pfSense community and see if they can help
me from there!
So from what I understand this issue was never officially fixed?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #41 from Roger Pau Monné ---
(In reply to Ricardo from comment #40)
Oh, I'm afraid I don't know how to apply those against a pfesne build. With
plain FreeBSD you would checkout the source from svn or git (see
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #40 from Ricardo ---
Hi Roger thank you so much for the quick reply!!
So looking for where to apply the patch I don't have the directory /sys and
/usr/src/sys is empty/doesn't exist.
Tried to find it but without success:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #39 from Roger Pau Monné ---
(In reply to Ricardo from comment #38)
Hello,
I've looked into it in the past, but I'm not a networking expert, and properly
solving those issues requires a very good understanding of the network
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #37 from Roger Pau Monné ---
(In reply to karl from comment #36)
Yes, I assumed so. I'm currently quite busy, so I don't think I will have time
to look into this ATM.
One thing I remember about reproducing this issue is that
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #36 from k...@pielorz.com ---
(In reply to Roger Pau Monné from comment #35)
Hi,
Disabling LRO/TSO doesn't make any difference - I think we'd tried that
previously as a possible fix.
-Karl
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #35 from Roger Pau Monné ---
Does this still happen if you disable LRO/TSO? (packets with size > 1500)
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #34 from k...@pielorz.com ---
(In reply to Eitan Adler from comment #33)
Hi - this issue still exists, I've just re-tested in 10.4 and 11.1. I'm not
able to test 12.x at the moment, but I have no reason to believe it's been
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #33 from Eitan
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #32 from kpiel...@tdx.co.uk ---
(In reply to Roger Pau Monné from comment #31)
Hi,
I can't see any obvious checksum errors recorded, and like yourself - I don't
know how to get similar information from dom0
-Karl
--
You
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #31 from Roger Pau Monné ---
(In reply to kpielorz from comment #30)
Oh right, this is kind of different from my test setup, it could explain why it
works in my case but not in yours. Do you see any
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #30 from kpiel...@tdx.co.uk ---
(In reply to Roger Pau Monné from comment #29)
Hi,
This machine is running natd [this was briefly mentioned in the original ticket
way-back-when] - so in /etc/rc.conf I have:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #28 from kpiel...@tdx.co.uk ---
(In reply to Roger Pau Monné from comment #27)
Hi,
I've applied the patch and rebuilt/re-installed the kernel. Sadly I too get no
output to the console / dmesg or /var/log/messages while
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #27 from Roger Pau Monné ---
(In reply to Sydney Meyer from comment #26)
Thanks, since in your case the patches seem to solve the issue, I'm waiting for
the feedback from Karl with the debug patch applied.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #26 from Sydney Meyer ---
(In reply to Roger Pau Monné from comment #25)
I have applied your patch on top of the others and there seems to be no output
related to packet forwarding, when doing the
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #24 from Sydney Meyer ---
FWIW, i have applied the three patches to r301515M and on a dom0 running Xen
4.4.1 with Linux 4.5.1, and a Xen 4.5.3 / NetBSD 7.0.1 host i was able to ping,
connect via ssh, scp
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #23 from Roger Pau Monné ---
(In reply to kpielorz from comment #22)
Thanks for the traces, I will try to prepare a debug patch for you either this
afternoon or tomorrow morning.
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #21 from Roger Pau Monné ---
(In reply to kpielorz from comment #20)
Yes, I think I know what the issue is. What OS are the other DomUs on the same
host using?
If you can provide me with complete tcpdump
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #18 from Sydney Meyer ---
I don't know if i missed something, but i see only two diffs on phabricator,
D6656 and D6612, where the last one is linked two times.
--
You are receiving this mail because:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #15 from Sydney Meyer ---
(In reply to Roger Pau Monné from comment #14)
Hello Roger,
https://reviews.freebsd.org/D6656
https://reviews.freebsd.org/D6612
https://reviews.freebsd.org/D6612
is this a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #14 from Roger Pau Monné ---
Hello,
I've recently committed a bunch of netfront fixes that I think should help
solve this issue. ATM, the only reliable way to do packet forwarding on a
FreeBSD DomU is to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #13 from Andreas Pflug ---
Yes, only Linux Dom0.
I've only seen one anomaly with offloading, which was fixed in Windows PVM
drivers a long time ago, so I assume that there's something in FreeBSD Dom0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #12 from Roger Pau Monné ---
(In reply to Andreas Pflug from comment #11)
I know, I'm just pointing out that this doesn't happen with a FreeBSD Dom0
running FreeBSD DomUs.
I guess you are always using a
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #11 from Andreas Pflug ---
It is a problem with DomUs, not Dom0.
--
You are receiving this mail because:
You are the assignee for the bug.
___
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #9 from Sydney Meyer ---
In its most basic form, without doing nat, without have pf loaded, the problem
comes up e.g. in the following setup:
(PC1) 10.0.1.2/24 on xn0 <--> 10.0.1.1/24 on xn0 (FreeBSD
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #8 from Roger Pau Monné ---
Hello,
I would really like to reproduce this, but sadly my FreeBSD network knowledge
is very limited, so please bear with me. When you say:
"Set this first machine up with (for
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #7 from kpiel...@tdx.co.uk ---
(In reply to raitech from comment #6)
Hi,
I've tested those options here - and they do work *for FreeBSD* boxes.
However - if you set '-txcsum -tso4 -lro' on the FreeBSD box acting as a router
-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
rait...@gmail.com changed:
What|Removed |Added
CC||rait...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
Sean Bruno sbr...@freebsd.org changed:
What|Removed |Added
CC||sbr...@freebsd.org
--On 18 February 2015 14:49 -0500 Michael MacLeod mikemacl...@gmail.com
wrote:
I've been using the OSS Xen releases for years, and have never been able
to get PVM domU to be functional as a gateway - I've either had to use
HVM or setup a separate box as the router. This has been the case
On 02/18/15 14:51, bugzilla-nore...@freebsd.org wrote:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #3 from kpiel...@tdx.co.uk ---
I just re-tested this with:
- XenServer 6.5
- FreeBSD 10.1 amd64
Installing FreeBSD in PVHVM mode (i.e. with 'xn0' NIC etc.) - and
I've been using the OSS Xen releases for years, and have never been able to
get PVM domU to be functional as a gateway - I've either had to use HVM or
setup a separate box as the router. This has been the case since at least
FBSD8 I think, or whenever XENHVM became an option.
On Wed, Feb 18, 2015
On Wed, Feb 18, 2015 at 6:01 PM, Marko Lerota mler...@pdsvelebit.hr wrote:
On 02/18/15 14:51, bugzilla-nore...@freebsd.org wrote:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #3 from kpiel...@tdx.co.uk ---
I just re-tested this with:
- XenServer 6.5
-
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #3 from kpiel...@tdx.co.uk ---
I just re-tested this with:
- XenServer 6.5
- FreeBSD 10.1 amd64
Installing FreeBSD in PVHVM mode (i.e. with 'xn0' NIC etc.) - and the problem
still exists (incase anyone else runs into it) -
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #2 from kpiel...@tdx.co.uk ---
Having setup a test system with FreeBSD 9.2-STABLE, 10-STABLE, 11-CURRENT etc.
this bug still exists on all of those, regardless of version.
For a 'Client' (i.e. a guest VM trying to route
36 matches
Mail list logo