Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Nächste Überarbeitung | Vorhergehende Überarbeitung | ||
ax25 [2018/01/08 11:24] dh3wr angelegt |
ax25 [2018/02/27 11:08] (aktuell) dh3wr [Connecting old Packet-Radio only transmitters via AX.25] |
||
---|---|---|---|
Zeile 1: | Zeile 1: | ||
====== Connecting old Packet-Radio only transmitters via AX.25 ====== | ====== Connecting old Packet-Radio only transmitters via AX.25 ====== | ||
- | There are several reasons why one would like to connect an old AX.25 Packet-Radio only Transmitter to the DAPNET: * No possibility to change the hardware due to restrictions or motivation | + | There are several reasons why one would like to connect an old AX.25 Packet-Radio only Transmitter to the DAPNET: |
- | * No IP connectivity at the transmitter location | + | * No possibility to change the hardware due to restrictions or motivation |
- | * Sentimental reasons to keep the RPC PCB :-) | + | * No IP connectivity at the transmitter location |
+ | * Sentimental reasons to keep the RPC PCB :-) | ||
For thoses cases we provide two possible solutions: | For thoses cases we provide two possible solutions: | ||
Zeile 19: | Zeile 20: | ||
- The antenna gain minus the cable losses in dBi | - The antenna gain minus the cable losses in dBi | ||
- The output power in Watt | - The output power in Watt | ||
- | - the antenna height above ground (not NN!) | + | - the antenna height above ground im meters (not NN!) |
The DAPNET team will check you request and provide a software solution with dapnet-proxy to connect your transmitter to the network. | The DAPNET team will check you request and provide a software solution with dapnet-proxy to connect your transmitter to the network. | ||
- | TBC | + | ===== Individual interfacing from AX.25 to TCP ===== |
+ | If you don't like the centralized way of connecting your old AX.25 transmitter, you can also setup you own interface from AX.25 to TCP. A Raspberry Pi is enough to do so. | ||
+ | |||
+ | The following steps are needed: | ||
+ | |||
+ | - Connect your RPC card by means of a USB-2-Serial converter | ||
+ | - Setup the ax0 kernel network device with kissattach. Edit ///etc/ax25/axport// before. | ||
+ | - Install xinetd | ||
+ | - Add the file below to a file in ///etc/xinetd.d// | ||
+ | - Use the DAPNET-Proxy to connect yourself with a DAPNET-Node | ||
+ | - Get your new transmitter registered into the DAPNET network (see above) | ||
+ | |||
+ | <file> | ||
+ | # description: Example AX.25 Interface to DB0SDA C9000 | ||
+ | service rpc_db0sda | ||
+ | { | ||
+ | disable = no | ||
+ | type = UNLISTED | ||
+ | port = 19999 | ||
+ | id = funkruf | ||
+ | socket_type = stream | ||
+ | protocol = tcp | ||
+ | user = root | ||
+ | wait = no | ||
+ | server = /usr/bin/axcall | ||
+ | server_args = -r -S -R -s db0sda-12 -r ax0 db0sda-7 | ||
+ | } | ||
+ | </file> | ||
+ | In this example //db0sda-12// is the defined master callsign in your RPC card and //ax0// is the AX.25 kernel-interface you created with //kissattach// and //db0sda-7// is the AX.25 connect path incl. the destination callsign (most probably only your RPC callsign). | ||
+ | |||
+ | Further information on the [[dapnetproxy|DAPNET-Proxy]] is [[dapnetproxy|here]]. | ||