Duplicating panic/error: no processor for ADNL packet from .....

[spookyahell]

I do have debug turned on but receiving the same exact line a dozen times... maybe that could be handled differently...
no processor for ADNL packet from 100.64.202.1:3333....

might also just be something on my end... not sure.
I'm using a customized Python thing to respond...
might look into whitelisting an extra public port for it to test how it responds when I access it directly.

Sometimes the forwarding works just fine, sometimes it doesn't

I am running multiple instances of the program at the same time...
not sure how many will have experience with that.

[xssnick]

Hi, no processor for ADNL packet is not a problem, it displays when client or server don't know the key for ADNL tunnel, it may happen after restart of server/client, but will be recovered is seconds by initializing new tunnel.

[spookyahell]

Well... In that case, I'd suggest a different output style...

Instead of repeating the line a bazillion times it would be great if the output just read "last output line produced xxx times" (following the style of ffmpeg for example) or at least an option for that...