Taomyn

Unfortunately nothing you have written is of help, yes I am up to date, always a few days after patches are released and I have tested uPnP from several systems...

> For anyone else coming here from Google with this same issue, I had both upnp and NAT-PMP ticked. When they were both ticked - opnsense would not response to...

> I figured out my problem - turned out it wasn't opnsense at all. It was a multicast issue. I tracked this down by running tcpdump on the lan interface...

I did some more digging and discovered another test I was performing on my domain, disabling NTLM, was also applied to this server when it shouldn't have been. When I...

> Actually, you should really specify the correct port. The failing MeatPack log shows a different port being used than the one logged in the "working" log. Does MeatPack fail...

> If that doesn't work, I'll need the rest of the octoprint.log file, since the excerpt is missing info about the `ttyACM0` connection attempt. No joy I'm afraid: ``` 2021-01-28...

> Looks like it's still trying to read from `ttyS0` in that excerpt. The PackingSerial() class doesn't decide which port to open. OctoPrint tells it what port to open. >...

> And a final note, when Marlin merged my file they did some refactoring which may not have been tested. The builds that were tested were built from a patch...

> No problem, then for the time being try replacing meatpack.cpp with the file I linked above, and then rebuild. > It would not compile  I did have issues...

> Indeed, the toggle command was removed in the header. Here's a fix, removed that case statement. > [meatpack_cor.zip](https://github.com/scottmudge/OctoPrint-MeatPack/files/5895363/meatpack_cor.zip)