AXDIGI(8)

💖 AXDIGI(8) 💖

okay bestie, gather round, because we're talking about axdigi — the little Linux Programmer's Manual icon that makes cross-port digipeating happen inside your ax25 stack. she's giving background-service main character energy and honestly? obsessed. ✨

---

🌸 NAME 🌸

axdigi — the axdigi file. that's it, that's the name. short, sweet, iconic. 💅

---

🦋 DESCRIPTION 🦋

so like, axdigi is an executable and you should load it up in your startup script with this exact command:

/usr/local/sbin/axdigi

(or whatever path you installed it to, no judgement 🫶). what does it do? it enables cross-port digipeating within your linux's ax25 stack. periodt.

⭐ Special Conditions ⭐

okay this is the part where you actually have to pay attention, bestie, because here's the tea:

in order to digipeat, you — or the user — must know your SSID associated with the ifconfig <interface> that is the direct link to the outbound path they wish to digi to. like, must must. no cap. axdigi will handle the appropriate digipeat accordingly. 💫

if you have multiple ax25 interfaces, you should somehow list them for the users in the axports description so they'll see them when doing an "Interface" command while on URONode. very demure, very mindful, very helpful.

and if the user wishes to log off URONode and digi through, then they must use the interface's SSID associated with the OUTBOUND path to their destination. not the inbound one. not the vibes one. the OUTBOUND one. 🎀

💌 commands are:

• C <destination> via <your interface-SSID> — okay so imagine the user heard station A1BCD-7 on your ax0 interface, and that interface's SSID is W1XYZ-9 (NOT the FlexID of URONode!!). then the user would enter: c a1bcd-7 via w1xyz-9 — even if their inbound interface might be ax1 and it's ifconfig shows your SSID as w1xyz-10! yes really. it's giving chaotic but it's correct. 😭

🔥 Detailed information

say you have 3 ax25 interfaces ifconfigured as:

ax0 - w1xyz-9
ax1 - w1xyz-10
ax2 - w1xyz-11

user k2lmn would enter your node via ax2 and they wish to digi to a1bcd-7 which is heard on ax0. so they would simply enter:

c a1bcd-7 via w1xyz-9

to connect. Axdigi handles the crossport functions. slay. 👑

but if they tried:

c a1bcd-7 via w1xyz-11

the connect would fail because it would attempt to digi OUT on your ax2 interface. 💀 this may get tricky so expect a need to educate your users on this. fr fr, put it in the group chat, make a lil tutorial, whatever works.

unfortunately, linux lacks native cross-port digipeating at this time so this is a work-around. lowkey tragic but we ball. 🌈

---

🎀 FILES 🎀

• /usr/local/sbin/axdigi

---

✨ SEE ALSO ✨

• axports(5)
• ax25(4)

go read those too, bestie, they're part of the lore. 🦋

---

and that's the whole page!! this Linux Programmer's Manual moment was brought to you by the 28 April 2013 edition of AXDIGI(8). tysm for reading, mwah 💖💅✨