This message was deleted.

tjkreidl: I compiled a new driver based on latest + DDK but, unfortunately, it is just as flakey

modinfo asix filename: /lib/modules/3.10.0+10/kernel/drivers/net/usb/asix.ko license: GPL description: ASIX AX88179_178A based USB 2.0/3.0 Gigabit Ethernet Devices author: David Hollis srcversion: 8C067E0D43E821F4DE1F17B

USB passtrhough on XenServer was meant more for things like cameras and pointing devices, not for high-throughput devices like NICs. USB kind of works for thumb drives, but that's about as far as you can currently push things.

Not looking at passthrough

How's the NIC connected then, just to the USB port directly using the DDK driver?

USB to Ethernet NIC. XenServer sees it as eth1

The VMs see the normal XS interface

OK. USB 2 or 3?

3

Hmmm... not sure why performance should be so bad. Do you see dropouts and such if you run "netstat -s"?

BIOS device: eth1 Kernel name: eth1 Permanent MAC: 00249B1EC3:45 Assigned MAC : 00249B1EC3:45 Driver: ax88179_178a Driver version: Firmware version: Bus Info: 2-4:1.0

It is worse that that

From a windows vm

Ping, trace, etc. Everythign works fine

Browsing to anything google works (gmail.com)

Can telnet to anything over 80

Can't browse to anything via IE or chrome, except google

Swith back to onboard interface while VM is still up. Everything works

I'm currently working to get traces at various locations

Lower the mtu?

I tested a ping with a packet size of 1472 and it works fine

Google.com, gmail works as well. It makes no sense..

Google uses IPv6 in a lot of their stuff I think

You won't be able to get 1500 mtu

because of header size

Selgan - I disabled ipv6 and tested previously. But that isn't a bad thought

I will be grabbing traces from VM, Host, Router as soon as I have a minute to do so. My guess is that XS is filtering something