Now I started to see this on FreeBSD as well (which I didn't for the last few days). Linux is the only one that's properly working. So it might be just something else.
2017-02-25 20:31 GMT+02:00 Tomohiro Kusumi <[email protected]>: >> What's the NIC? > > [root@]~# uname -r > 4.6-RELEASE > [root@]~# dmesg | grep em0 | head -1 > em0: <Intel(R) PRO/1000 Network Connection 82545EM_COPPER 7.4.2> port > 0x2000-0x203f mem 0xfdff0000-0xfdffffff,0xfd5c0000-0xfd5dffff irq 7 at > device 1.0 on pci2 > >> And what's the emulated NIC mode in the vmware? > > It's NAT (not bridge) if I got your question correctly. > > > > 2017-02-25 17:06 GMT+02:00 Sepherosa Ziehau <[email protected]>: >> What's the NIC? And what's the emulated NIC mode in the vmware? >> >> On Sat, Feb 25, 2017 at 9:11 PM, Tomohiro Kusumi >> <[email protected]> wrote: >>> This reproduces with DragonFly 4.4 as well on VMware. >>> >>> wget of dfly-x86_64-4.6.1_REL.iso stops at around after it has >>> received the first 10-20MB of the file. >>> >>> It's actually not completely stopped, but each tcp packet is only >>> receiving 0 or 1 byte of data (once it has received the first 10-20MB) >>> while tcp window size stays at around 60000. >>> This of course doesn't happen with Linux or FreeBSD. >>> Sounds like our bug. >>> >>> >>> 2017-02-24 20:52 GMT+02:00 Tomohiro Kusumi <[email protected]>: >>>> I'm using VMware. >>>> >>>> Ping as well as wget of a small file (like some KB to 1MB or so) work >>>> fine, but can't wget a large file like our iso image. >>>> wget stops at around 2-10% of progress. >>>> >>>> I also failed to git clone a repository from github whose du -sh is around >>>> 9MB. >>>> It stopped at around 10% progress or so. >>>> >>>> I'm not sure if 4.5 was working on VMware. >> >> >> >> -- >> Tomorrow Will Never Die
