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 I'
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?
C
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://www.freebsd
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:
[adm
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
su
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
Ricardo changed:
What|Removed |Added
CC||maveric...@outlook.pt
--- Comment #38 fr
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 it
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 beca
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.
___
f
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
fixe
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
Eitan Adler changed:
What|Removed |Added
Status|In Progress |Open
--- Comment #33 from Eitan Adle
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 ar
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 checksum errors? 'netstat -s
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:
ifconfig_xn1="DHCP
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #29 from Roger Pau Monné ---
(In reply to kpielorz from comment #28)
Can you provide a little more info about your router configuration? In my tests
I've only enabled net.inet.ip.forwarding=1 in the VM acting as a router and
co
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 packets
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.
Roger.
--
You are
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 above described tests.
Here'
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #25 from Roger Pau Monné ---
Could you please apply the following patch on top of the other three and report
the results back? It should print some messages on the console (dmesg) when
doing packet forwarding.
https://people.f
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 a file and nc some data
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 mail because:
You ar
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #22 from kpiel...@tdx.co.uk ---
(In reply to Roger Pau Monné from comment #21)
Hi,
pcaps are at (for a short time) http://www.pielorz.com/xn_pcaps.tar.gz
These are xn0.pcap.san and xn1.pcap.san ('.san' because I sanitised the
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 traces on both interfa
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #20 from kpiel...@tdx.co.uk ---
(In reply to Roger Pau Monné from comment #19)
Hi,
I applied the previously missing d6611 patch (so I have d6611, d6612, d6656
applied) - but it still doesn't work :(
If I live migrate the test
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #19 from Roger Pau Monné ---
(In reply to Sydney Meyer from comment #18)
Sorry, I've failed to post the three links, and the also failed to understand
what you were trying to tell me. Here are the proper links:
https://reviews
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:
You are the assignee for t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #17 from kpiel...@tdx.co.uk ---
(In reply to Roger Pau Monné from comment #16)
Hi,
I've tested these patches now. I installed a HEAD snapshot, and updated it to
r301543M.
The VM can route traffic with '-rxcsum -txcsum -tso -l
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #16 from Roger Pau Monné ---
(In reply to Sydney Meyer from comment #15)
Hello,
To clarify this, the current code in HEAD should work when doing packet
forwarding if rxcsum, txcsum, tso and lro are disabled.
Then, the 3 patc
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 typo or are there actually
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 disable all the hardwa
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
that's disguising the bug.
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 Linux Dom0?
--
You ar
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.
___
freebsd-xen@freebsd.org mailing list
ht
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
--- Comment #10 from Roger Pau Monné ---
(In reply to Sydney Meyer from comment #9)
Just as a side note, I haven't been able to reproduce this using a FreeBSD
Dom0, I will now try with a Linux Dom0 (I guess Linux is more picky about
checks
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 DomU Router)
10.0.2.1/24 on
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 example) 'gateway_en
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
Michael MacLeod changed:
What|Removed |Added
CC||mikemacl...@gmail.com
--- Commen
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261
Sean Bruno changed:
What|Removed |Added
CC||sbr...@freebsd.org
--- Comment #4 fro
--On 18 February 2015 14:49 -0500 Michael MacLeod
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 since
at least FBSD8 I t
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 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
>> - FreeBSD 10
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 th
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) - th
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 traffic
46 matches
Mail list logo
