Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen Revision Vorhergehende Überarbeitung | Letzte Überarbeitung Beide Seiten der Revision | ||
dapnetproxy [2018/01/08 13:20] dh3wr [Function description] |
dapnetproxy [2018/01/08 13:21] dh3wr |
||
---|---|---|---|
Zeile 3: | Zeile 3: | ||
===== Background ===== | ===== Background ===== | ||
- | In the former [[Funkrufmaster|http://ham-pager.sourceforge.net]]-Network the connection to the transmitter was established by the Funkrufmaster sofware. So the client was listening on its AX.25 interface for a connect from the master. | + | In the former [[http://ham-pager.sourceforge.net|Funkrufmaster]]-Network the connection to the transmitter was established by the Funkrufmaster sofware. So the client was listening on its AX.25 interface for a connect from the master. |
Using IP as the main protocol to connect transmitters and the DAPNET-Nodes, this direction of connection establishment was inverted. Incoming connections are in some cases a problem with IP: Think of transmitters connected via UMTS or restrictive internet access point, where incoming port forwarding is not possible. | Using IP as the main protocol to connect transmitters and the DAPNET-Nodes, this direction of connection establishment was inverted. Incoming connections are in some cases a problem with IP: Think of transmitters connected via UMTS or restrictive internet access point, where incoming port forwarding is not possible. | ||
So in DAPNET, the transmitter connects itself to the node. As the software of the old RPC transmitters should not be changed, DAPNET-Proxy was born. | So in DAPNET, the transmitter connects itself to the node. As the software of the old RPC transmitters should not be changed, DAPNET-Proxy was born. |