You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When aprsd only has tcp kiss enabled, it gives attribute error. I was able to fix this by changing Line 92 in kiss.py to all lowercase. Once the attribute error was fixed, it looks asit does when running on the 'IS' connection. However, it doesn't seem to be parsing the "thirdparty" packets and never receives a ping message over kiss. I would look further into fixing this and contribute but not knowing the work flow is my limiting factor. Would take me a bit, but would figure it out. Everything seems to work fine when connection IS enabled and tcp disabled.
I am running direwolf that seems to send everything over the kiss port as third party. I have tested APRSISCE with the same connection and it seems to work fine.
The text was updated successfully, but these errors were encountered:
When aprsd only has tcp kiss enabled, it gives attribute error. I was able to fix this by changing Line 92 in kiss.py to all lowercase. Once the attribute error was fixed, it looks asit does when running on the 'IS' connection. However, it doesn't seem to be parsing the "thirdparty" packets and never receives a ping message over kiss. I would look further into fixing this and contribute but not knowing the work flow is my limiting factor. Would take me a bit, but would figure it out. Everything seems to work fine when connection IS enabled and tcp disabled.
I am running direwolf that seems to send everything over the kiss port as third party. I have tested APRSISCE with the same connection and it seems to work fine.
The text was updated successfully, but these errors were encountered: