For pyTivo with Python 2.7.8 the network traffic is being modified somehow on the Host

[Steven Wilson]

I've been using pyTivo and VirtualBox on the same host for a long time. It worked fine until I upgraded from 4.3.12 to 4.3.16. There were no errors produced, but my TiVo could not access pyTivo. I downgraded back to 4.3.12 and pyTivo started working again. Not really sure what log files I could produce to demonstrate the problem. I do not see any errors in any of the Windows log files and pyTivo shows no problems. I can only surmise that it is some sort of networking issue. However I can still access the web address for the program, ​http://pytivohost:9032, from another computer. Only my TiVo cannot access it.

I'm running Windows 7 Home Premium 64-bit with 16GB of RAM. Not particularly relevant, but my guests are also Windows 7 64-bit. The problem exists whether any guests are running or not.

[Steven Wilson]

This appears to have something to do with the default beacon address of 255.255.255.255. I changed it to my local subnet, 192.168.1.255 as an example, and it resolved the issue without having to downgrade, but this doesn't explain why I had to make this change.

[Frank Mehnert]

Regarding the log files: The most important log file is always the VBox.log file of such a VM session. This gives, for example, a quick overview about your VM setup.

[Steven Wilson]

VBlox.log

[Steven Wilson]

VBox.log

[Steven Wilson]

I just tested with 4.3.18. No change. Beacon of 255.255.255.255 still fails, but workaround of setting beacon to the specific subnet broadcast mask still works.