so ive been running a TNC-Pi on my pi3 with Direwolf for a few weeks now and everything locally seems fine — i can see my own beacon showing up in Xastir and other stations are hitting my digipeater no problem. but none of it seems to be making it to aprs.fi. like at all. my station just doesnt show up there and when i check the raw packets nothing is coming through from my callsign-10.

im running the WIDE1-1,WIDE2-1 path on my beacons, RF is going out fine, i can hear other traffic on 144.390. the igate part of direwolf is configured with my passcode and everything, i double checked that like three times. server is set to rotate.aprs.net port 14580. filter is set for a 200km radius around my grid square.

is there something dumb im missing in the direwolf config? i feel like ive been staring at this for so long i cant see the obvious thing anymore

check your IGSERVER line and also make sure IGLOGIN actually has the right callsign-ssid format. i had mine set as just my base call without the ssid and it connected fine but wasnt passing authentication properly. also worth looking at the direwolf log output when it starts up — if the igate login fails it does print something but its easy to scroll past. another thing to check is whether your firewall is blocking outbound on 14580, had that bite me once on a fresh pi install.

yeah what he said about the log is key. but also — are you sure your beacons are actually getting picked up by another igate and not just your own? if direwolf is set to igate but something in the filter config is wrong it might just be silently dropping stuff. aprs.fi has a raw data view, search for your call there and see if anything at all shows up, sometimes theres a delay too but like 24 hours and nothing means somethings definitely broken in the chain. i went through almost the exact same thing and it turned out i had a typo in my passcode, just one digit off, connection succeeds but you get no igate priveleges