wohler's Posts

Yes, the same for me. I got my nine bytes back, and that was with the existing version of Fusion (12.1.2). Upon starting Fusion, I was welcomed to a screen saying that Fusion version 12.2.0 was avail... See more...
Yes, the same for me. I got my nine bytes back, and that was with the existing version of Fusion (12.1.2). Upon starting Fusion, I was welcomed to a screen saying that Fusion version 12.2.0 was available that "supported Monterey". It provided a hardware version upgrade to version 19. Thus, another solution to this problem is to install Monterey. Thanks again, gringley!
@gringley, thank you so much for posting here! It's like back to the future. I haven't had to mess with the MTU since the 80s and thought it was a solved problem. The number that worked for me on my... See more...
@gringley, thank you so much for posting here! It's like back to the future. I haven't had to mess with the MTU since the 80s and thought it was a solved problem. The number that worked for me on my Debian Bullseye system was 1491. $ sudo ip link set eth0 mtu 1491 I also updated the network settings in the GUI so the interface would be initialized properly (GNOME 3 menu in upper right > Wired Connection > Wired Settings > Interface Gear Icon > Identity > MTU). Thanks again. I've already joyfully thrown out all of my inadequate workarounds.
Thanks, mate. Even though your symptoms were a little different, it was worth a shot. My virtualDev setting was already e1000. I tried e1000e and vmxnet3 and experienced the same symptoms. I left it ... See more...
Thanks, mate. Even though your symptoms were a little different, it was worth a shot. My virtualDev setting was already e1000. I tried e1000e and vmxnet3 and experienced the same symptoms. I left it at e1000e though.
I recently upgraded to Big Sur and found I had to upgrade Fusion to version 12 as well. I have a Debian Linux client. Ever since then, my bridged network has been behaving strangely. Viewing Google ... See more...
I recently upgraded to Big Sur and found I had to upgrade Fusion to version 12 as well. I have a Debian Linux client. Ever since then, my bridged network has been behaving strangely. Viewing Google pages in the browser seems to work, but every other page comes up blank. fetchmail can't connect to my mail server. My NAS can start an rsync backup to my client, but it always eventually dies with: Connection to 192.168.50.4 closed by remote host. rsync: connection unexpectedly closed (653017239 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(605) [receiver=3.0.9] rsync: connection unexpectedly closed (58 bytes received so far) [generator] rsync error: unexplained error (code 255) at io.c(605) [generator=3.0.9] My NAT adapter is working as it always has. Am I waiting for a Big Sur or Player 12 update that will magically fix bridged networking, or is there some tweaking that is required to fix this?