[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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'm not an expert on the networking subsystem).

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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?

Cheers

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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.org/doc/handbook/svn.html) and you would then build a new
kernel with the patches applied
(https://www.freebsd.org/doc/handbook/makeworld.html).

You will have to ask the pfsense community how to apply those patches and
rebuild the pfsense kernel.

Roger.

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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:

[admin@pfs-fw01]/: find / -iname 'ip_fastfwd.c'
[admin@pfs-fw01]/:

pfSense 2.4.5-RELEASE-p1 (amd64) 
built on Tue Jun 02 17:51:17 EDT 2020 
FreeBSD 11.3-STABLE

Thank you!!

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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
subsystem, as I think some modifications to common code are required. When
trying to solve this I've made the following patches:

https://reviews.freebsd.org/D6611
https://reviews.freebsd.org/D6612

(this last one might not be required:)

https://reviews.freebsd.org/D6656

I'm afraid those patches are old, so they might not apply cleanly. Let me know
if you can apply and give them a try, and whether they fix anything.

Roger.

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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 takes a non
trivial amount of time to setup a way to reproduce it (last time I tried I had
to setup a forwarding VM).

Could you perhaps document the faster way to reproduce it, and the one that
likely involves less setup? That would be helpful (for me at least) and maybe
others that will look into the issue.

Thanks, Roger.

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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 because:
You are the assignee for the bug.
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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.
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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
fixed in current or anything.

It affects anything working with 'low level' packets - so NAT, OpenVPN, DHCP
et'al. - e.g. with OpenVPN it seems packet coalescing 'behind the scenes' ends
up presenting  way over 1500 byte packets to OpenVPN - which it point blank
refuses to handle.

Workaround we're using here is to set 'hw.xen.disable_pv_nics=1' in
/boot/loader.conf on FreeBSD with a small mod to 'qemu-dm-wrapper' on the Xen
Server, and a custom field added to affected VM's in XenCenter that the wrapper
'keys off' - this turns xn0 into vtnet0 for these hosts - these do work with
the above applications, and are still live-migratable (and appear to be better
performance than re0 NIC's).

-Karl

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261

Eitan Adler  changed:

   What|Removed |Added

 Status|In Progress |Open

--- Comment #33 from Eitan Adler  ---
batch change:

For bugs that match the following
-  Status Is In progress 
AND
- Untouched since 2018-01-01.
AND
- Affects Base System OR Documentation

DO:

Reset to open status.


Note:
I did a quick pass but if you are getting this email it might be worthwhile to
double check to see if this bug ought to be closed.

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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 are receiving this mail because:
You are the assignee for the bug.
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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
-f inet' should tell you if there are any checksum errors, at least from a
FreeBSD point of view.

It would also be interesting to do the same on the Dom0 itself, but I'm not
aware of the rune to obtain that information from Linux.

Roger.

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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" // This is our 'Internet' feed via ADSL modem
ifconfig_xn0="inet x.x.x.x netmask 255.255.255.0" // Local LAN IP
gateway_enable="YES"
firewall_enable="YES"
firewall_type="OPEN"
natd_enable="YES"
natd_interface="xn1"
natd_flags=""

'ipfw show' gives:

00050 1226  417933 divert 8668 ip4 from any to any via xn1
...
65000 7324 1573607 allow ip from any to any
655350   0 deny ip from any to any


I can try and setup a non natd case again - but that will involve quite a few
changes, as I have no easily routed networks at our office.

-Karl

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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 are being
forwarded. If I move the VM to another node (so it works) - I get nothing
logged, and if I move it back to the same node as the other test VM's - it
stops working, and I still get nothing logged - sorry!

-Karl

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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 receiving this mail because:
You are the assignee for the bug.
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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's the full dmesg output:

Copyright (c) 1992-2016 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 11.0-ALPHA2 #0 r301752M: Thu Jun  9 23:05:34 CEST 2016
sydney@head:/usr/obj/usr/src/sys/GENERIC amd64
FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM
3.8.0)
WARNING: WITNESS option enabled, expect reduced performance.
can't re-use a leaf (ixl_rx_miss_bufs)!
VT(vga): text 80x25
XEN: Hypervisor version 4.4 detected.
CPU: Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz (3600.07-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x306c3  Family=0x6  Model=0x3c  Stepping=3
 
Features=0x1783fbff
 
Features2=0xfffa3203
  AMD Features=0x28100800
  AMD Features2=0x21
  Structured Extended Features=0x72a
  XSAVE Features=0x1
Hypervisor: Origin = "XenVMMXenVMM"
real memory  = 528482304 (504 MB)
avail memory = 465608704 (444 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: 
random: unblocking device.
ioapic0: Changing APIC ID to 1
MADT: Forcing active-low polarity and level trigger for SCI
ioapic0  irqs 0-47 on motherboard
random: entropy device external interface
kbd1 at kbdmux0
netmap: loaded module
module_register_init: MOD_LOAD (vesa, 0x80f2eb70, 0) error 19
random: registering fast source Intel Secure Key RNG
random: fast provider: "Intel Secure Key RNG"
vtvga0:  on motherboard
cryptosoft0:  on motherboard
acpi0:  on motherboard
acpi0: Power Button (fixed)
acpi0: Sleep Button (fixed)
cpu0:  on acpi0
hpet0:  iomem 0xfed0-0xfed003ff on acpi0
Timecounter "HPET" frequency 6250 Hz quality 950
attimer0:  port 0x40-0x43 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
atrtc0:  port 0x70-0x71 irq 8 on acpi0
Event timer "RTC" frequency 32768 Hz quality 0
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <32-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
isab0:  at device 1.0 on pci0
isa0:  on isab0
atapci0:  port
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc400-0xc40f at device 1.1 on pci0
ata0:  at channel 0 on atapci0
ata1:  at channel 1 on atapci0
pci0:  at device 1.3 (no driver attached)
xenpci0:  port 0xc000-0xc0ff mem 0xf200-0xf2ff irq
24 at device 2.0 on pci0
vgapci0:  mem
0xf000-0xf1ff,0xf30d-0xf30d0fff at device 3.0 on pci0
vgapci0: Boot video device
atkbdc0:  port 0x60,0x64 irq 1 on acpi0
atkbd0:  irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0:  irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse Explorer, device ID 4
fdc0:  port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
fdc0: does not respond
device_attach: fdc0 attach returned 6
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart0: console (9600,n,8,1)
xenpv0:  on motherboard
granttable0:  on xenpv0
xen_et0:  on xenpv0
Event timer "XENTIMER" frequency 10 Hz quality 950
Timecounter "XENTIMER" frequency 10 Hz quality 950
xenstore0:  on xenpv0
evtchn0:  on xenpv0
privcmd0:  on xenpv0
debug0:  on xenpv0
orm0:  at iomem 0xef000-0xe on isa0
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
fdc0: No FDOUT register!
ppc0: cannot reserve I/O port range
Timecounters tick every 1.000 msec
xenballoon0:  on xenstore0
xctrl0:  on xenstore0
xs_dev0:  on xenstore0
xenbusb_front0:  on xenstore0
xenbusb_add_device: Device device/suspend/event-channel ignored. State 6
xn0:  at device/vif/0 on xenbusb_front0
xn0: Ethernet address: 00:16:3e:f1:04:bd
xn1:  at device/vif/1 on xenbusb_front0
xn1: Ethernet address: 00:16:3e:f1:14:bd
xn0: backend features: feature-sg feature-gso-tcp4
xn2:  at device/vif/2 on xenbusb_front0
xn1: backend features: feature-sg feature-gso-tcp4
xn2: Ethernet address: 00:16:3e:f1:24:bd
xenbusb_back0:  on xenstore0
xn2: backend features: feature-sg feature-gso-tcp4
xbd0: 3072MB  at device/vbd/51712 on xenbusb_front0
xbd0: features: flush, write_barrier
xbd0: synchronize cache commands enabled.
taskqgroup_adjust failed cnt: 1 stride: 1 mp_ncpus: 1 smp_started: 0
taskqgroup_adjust failed cnt: 1 stride: 1 mp_ncpus: 1 smp_started: 0
Timecounter "TSC-low" frequency 1800037036 Hz quality 800
WARNING: WITNESS option enabled, 

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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 between two FreeBSD VMs connected
trough a third VM, all running this revision, on the same Linux, respective
NetBSD dom0 host.

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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 are the assignee for the bug.
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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 interfaces
(xn0/xn1), that would help me quite a lot, the following rune should get you
the traces:

# tcpdump -n -i  -s0 -w .pcap

The resulting pcap files are going to be quite big, so you will probably have
to upload them somewhere. Just 10s of capture while trying to route traffic is
probably fine.

Thanks, Roger.

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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 the bug.
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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 three patches?

Sydney

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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 hardware offload features on both nics
(rxcsum, txcsum, tso and lro). Could someone give it a try?

I'm also working on making forwarding work _without_ having to disable all
those features, so that we can get optimal performance, however those patches
have not yet been reviewed:

https://reviews.freebsd.org/D6656
https://reviews.freebsd.org/D6612
https://reviews.freebsd.org/D6612

Roger.

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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.

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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 are receiving this mail because:
You are the assignee for the bug.
___
freebsd-xen@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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
https://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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 xn1 <--> (PC2) 10.0.2.2/24 on xn0.

- Install FreeBSD on DomU Router with 2 paravirtual network interfaces in
different subnets
- sysctl net.inet.ip.forwarding=1 on Router
- Setup PC1/2 with FreeBSD/Linux/Windows with the FreeBSD Router as their
Gateway.
- On PC1: dd if=/dev/zero bs=1M | nc -l 5001
- On PC2: nc 1.2.3.4 5001 | dd of=/dev/zero bs=1M
- Or any other TCP-Connection, e.g. ssh, for that matter.

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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_enable="YES"' etc. and
configure it to route or NAT traffic to the Internet."

Can you please provide examples about how to route NAT traffic to the Internet?
A very simple (reduced) use-case that can be used to reproduce this issue would
help me a lot.

Thanks, Roger.

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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
- Windows machines still cannot pass traffic through it as a router :( [not
tested Linux - but I'd guess from past experience a Linux PV instance will be
the same]

So whilst this is a work around (of sorts) for FreeBSD boxes using another
FreeBSD box as a router - it's not usable in mixed platforms.

There's obviously some weird interaction still going on with PV to PV network
traffic involving FreeBSD when it's 'routing' things.

-Karl

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261

rait...@gmail.com changed:

   What|Removed |Added

 CC||rait...@gmail.com

--- Comment #6 from rait...@gmail.com ---
(In reply to Sean Bruno from comment #4)

Following Sean's idea, I was playing with the PV network frontend options, and
got one FreeBSD 10.1 RELEASE to get its traffic routed by another FreeBSD 10.1
RELEASE, both within the same XenServer 6.5 host and both with xn1 over the
same host-VLAN.

router0# ifconfig xn1 -txcsum -tso4 -lro
vm0# ifconfig xn1 -txcsum -tso4 -lro

Without this config on both domUs, I can not do a:

# fetch http://www.google.com/
  (obs.: on success, result will be stored in fetch.out; 
 needs two control-C to stop)

But with the indicated configuration, I can exec the above command like a
charm. I could even SSH into the vm0 from the Internet.

Best regards,
Raimundo Santos

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188261

Sean Bruno sbr...@freebsd.org changed:

   What|Removed |Added

 CC||sbr...@freebsd.org

--- Comment #4 from Sean Bruno sbr...@freebsd.org ---
I use an HVM based VM in the rootbsd cloud.  Recently on -current I had to
disable rxcsum and txcsum on my vm interfaces to make it happy with PF

ifconfig_xn0=inet XXX.XXX.XXX.XXX netmask 0xfffc -rxcsum -txcsum

Maybe try that?

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

Re: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[Karl Pielorz]

--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 since
at least FBSD8 I think, or whenever XENHVM became an option.


As the original bug filer...

I've tried FBSD 9, 10 and 11 - I was hoping (under the you never know 
banner) that XS 6.5 with updated Xen etc. might make a difference - but 
sadly it doesn't, as people have pointed out - it's a likely issue with 
netfront/back code in FBSD.


This is a real pain for us - apart from the hours initially wasted figuring 
it out - and the 'accidents' when people forget, we either have a bunch of 
non-agile machines polluting our main pools, or a secondary pool of shame 
where all the FBSD boxes that do things like VPN, routing, DHCP, 
firewalling are running in HVM mode [and again, not agile]. Performance of 
HVM NIC's and  disk isn't as good as PV either (as you'd expect).


I have the stuff to test this setup in house here - I just don't know where 
to start to look at it :( - but open to suggestions ;)


Cheers,

-Karl
___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org

Re: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[Marko Lerota]

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 the problem
still exists (incase anyone else runs into it) - there's been a least a couple
of other people run into this issue setting up VM's for routing etc.


And there is a problem with disk speed also. Xenserver is no FreeBSD
friendly.
___
freebsd-xen@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-xen
To unsubscribe, send any mail to freebsd-xen-unsubscr...@freebsd.org

Re: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[Michael MacLeod]

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 at 2:44 PM, Miguel Clara miguelmcl...@gmail.com
wrote:

 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
- 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) - there's been a least a
  couple
  of other people run into this issue setting up VM's for routing etc.
 
 
  And there is a problem with disk speed also. Xenserver is no FreeBSD
  friendly.
 
 
 I don't even have network with FreeBSD on and XenSource NetBSD host... I
 think the main issue is really the xennet(back/front) code in 10, since I
 have no issue in 9.

 See: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369

 Would be awesome if someone with good xennet(back/front) knowledge could
 look into it, and maybe the same for the disk part.

 Under a linux dom0 network works and tbh I havent tested later but disk
 performance still could use some improvements.



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

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

Re: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[Miguel Clara]

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
   - 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) - there's been a least a
 couple
 of other people run into this issue setting up VM's for routing etc.


 And there is a problem with disk speed also. Xenserver is no FreeBSD
 friendly.


I don't even have network with FreeBSD on and XenSource NetBSD host... I
think the main issue is really the xennet(back/front) code in 10, since I
have no issue in 9.

See: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188369

Would be awesome if someone with good xennet(back/front) knowledge could
look into it, and maybe the same for the disk part.

Under a linux dom0 network works and tbh I havent tested later but disk
performance still could use some improvements.



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

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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) - there's been a least a couple
of other people run into this issue setting up VM's for routing etc.

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

[Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host.

[bugzilla-noreply]

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 through the other
FreeBSD 'router' machine) you can do:

  ifconfig xn0 -txcsum

And it will fix that single client. No amount of option fiddling (other than
restarting in HVM mode) will fix the 'router' machine - i.e. it's not possible
to fix the 'router' machine so that clients don't need any fix.

I've been unable to test disabling txcsum on Windows clients running on the
same XenServer as I can't see where I can do that.

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