开云体育

APRSC? I am not sure what that is, or how you are checking it.? It appears to be a "build your own" server (like I used for testing). You are making it into the APRS-IS backbone because you are

So, I have renamed the direwolf.conf file in the /build directory, and renamed both sdr.conf files in case they were a problem. There is still a generic.conf but that seems to be fully commented out

Funny, but that is what both the V1.6 (pg 40) and V1.7 (p43) User Manual shows: Dire Wolf version ... Reading config file /Users/<Home_Dir>/direwolf.conf But later in the manual, the path section is

I've filed an enhancement request at https://github.com/wb2osz/direwolf/issues/554 to have Direwolf specifically call out what path and configuration file it's using when it starts up. --David KI6ZHD

FWIW, I recently (2 weeks ago) moved direwolf to another computer. It was a fresh installation of v1.8D and it only created direwolf.conf in my home directory. There is not a copy in the build

Just a suggestion. Locate all the direwolf.conf files on your computer (find or locate or whatever works for you), make a list of them and their paths. Rename each one to something unique, like

It shouldn't be able to do anything over RF since I am only connected to the output of the HT. Maybe I don't have an argument in the config to stop digipeaters from repeating my location. I thought I

Looks like you are connected. Strange that you are seeing (and sending over RF) my posting some 1800 miles away. These 2 lines show you send info to APRS-IS and received it back - [ig]

Connected but not functioning yet. Dire Wolf DEVELOPMENT version 1.8 D (Oct 12 2024) Includes optional support for: ?cm108-ptt libgpiod Reading config file direwolf.conf Config file: Unrecognized

APRS.FI shows an updated position from today. So ... you are connected! Robert Giuliano KB8RCO

<insert minor swearing> Why on earth are there more than one direwolf.conf file in different locations?</end> My interpretation of the manual was that it would look in the home directory, not that

Well, I just repeated the test with different results. This time running a plain *direwolf* command line did grab the local *direwolf.conf* (in the *build* directory). It also connected to my local

Did you run *sudo make install* and *make install-conf* to install direwolf on your Pi? If you did, then there is a direwolf.conf file in your home directory (~/direwolf.conf). From the V1.7 manual,

It has been running for an hour. The log still shows no attempt to connect to the IGSERVER.

John, honestly no, I am not confident that it is using the correct configuration file. I believe there is only one file called direwolf.con, which is in the same directory as Direwolf

This does not make sense. If the configuration has a correct IGSERVER and IGLOGIN, direwolf should say something about connecting to APRS-IS. Here is an example where it was successful the first try:

One problem with our test method is that we are connecting to an address that can change. Let's try direct to the source.? In a web browser, try connecting to https://noam.aprs2.net:14501 Somewhere

Seems that I am able to access the server, which is good. I am unable to access most settings in the router thanks to the monopoly status of the internet in the USA. We only have one ISP, and they

Direwolf does support IPv6, but some Pi installs recommend disabling it.?? try ? ? ping -c 5 -6 noam.aprs2.net this will test if you Pi can reach the IPv6 server ?? The -c 5 is to limit the ping

Your pings of noam.aprs2.net show that your DNS is resolving an IPV6 address. I'm thinking perhaps Direwolf doesn't support IPv6 currently. If you don't need IPv6 I would try disabling it in your home