-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IGate not started on Ubuntu 16.04 #188
Comments
When direwolf starts up, it should display some information about the configuration and progress of connecting to an APRS-IS server. What do you see on the screen? How does it differ between the two cases? It should not be necessary to run direwolf as root (sudo). It could be a permission issue. What does the "id" command produce? This should really go in the discussion group. This "issues" section is meant for bug reports (defects) and enhancement requests. |
Hi.. a moment ago, I tried again with and without sudo to use it as an IGate, and guess what? Now it works!! Now I wonder what I did or how I did it the last time. As a bonus, now I see a bunch of other packets from APRS-IS on the direwolf screen, labeled as [ig->tx] or some sort... Btw, before this test, I logged in once from my APRS Droid app on my smartphone directly to the APRS-IS using the same callsign and SSID. Maybe it has an effect? I think the issue is solved for me by now. Thanks for your hard work. 73, de YD1SDL |
Hi, I want to join the discussion group. Where I can find them? |
Discussion group has moved to https://groups.io/g/direwolf |
I tried Direwolf release 1.5 (October 2018, but I downloaded it at Dec 2018) on Linux Ubuntu 16.04 machine. The APRS decoding, digipeating works well, but IGate function would not start.
In the windows machine, the Windows (same 1.5) release would start the IGate functionality just fine.
Same laptop, same network, even same configuration file.
Any idea?
Edit:
Just a moment ago, I tried to run the direwolf using sudo and now the IGate works..
The text was updated successfully, but these errors were encountered: