User Tools

Site Tools


packet:xrouter-qttermtcp

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
packet:xrouter-qttermtcp [2023/07/29 13:19] – created m0ltepacket:xrouter-qttermtcp [2023/07/29 14:49] (current) m0lte
Line 1: Line 1:
 ====== HOWTO Use QTTermTCP With XRPi / XRLin ====== ====== HOWTO Use QTTermTCP With XRPi / XRLin ======
  
-12th April 2023, G8PZT+29 July 2023, G8PZT
  
 NOTE: This is a "quick and dirty" howto. Please feel free to refine it, NOTE: This is a "quick and dirty" howto. Please feel free to refine it,
Line 48: Line 48:
  
 <code> <code>
- sudo setcap cap_net_bind_service=pe xrpi+sudo setcap cap_net_bind_service=pe xrpi
 </code> </code>
  
- (substitute xrlin for xrpi if you are on x86)+(substitute xrlin for xrpi if you are on x86)
  
 You can avoid this by setting the port numbers to something above 1024. You can avoid this by setting the port numbers to something above 1024.
Line 188: Line 188:
 Click OK and you're all done. Click OK and you're all done.
  
-As far as I can see, QTTermTCP only allows incoming connections when it +Note: In "Single Window" mode, QTTermTCP will not accept incoming 
-is idle, ie when it is not downlinked to XRouter. There may be other +connections while it is connected to XRouter. However in "tabbed" or 
-modes which allow this, but that is outside the scope of this document.+"MDI" mode it will.
  
 +
 +===== Monitor Traffic =====
 +
 +
 +XRouter will send monitor traffic to QTTermTCP, but it will be in XRouter
 +format, not BPQ format, i.e. it will look like this:
 +
 +<code>
 + *** 14:40:51 port 4 rcvd:
 + AX25: G8PZT>G8PZT-1 <RR R R4>
 +
 + *** 14:41:00 port 4 rcvd:
 + AX25: G8PZT>G8PZT-1 <I C R4 S4> ilen=20 pid=207 NET/ROM
 +   NTRM: G8PZT-8 to G8PZT-9 ttl=25 cct=0100 <DISC REQ> 
 +
 + *** 14:41:00 port 4 sent:
 + AX25: G8PZT-1>G8PZT <I C R5 S4> ilen=20 pid=207 NET/ROM
 +   NTRM: G8PZT-9 to G8PZT-8 ttl=25 cct=D208 <DISC ACK> 
 +</code>
 +
 +The displayed port numbers are XRouter's PORT numbers not QTTermTCP's.
 +
 +If your XRouter ports are numbered consecutively from 1, they will agree
 +with the port mumbers under QTTermTCP's "Monitor" tab. If however
 +XRouter's port numbers don't start at 1, or have gaps, QTTermTcp's
 +"Monitor" tab will list consecutively numbered ports, with the XRouter
 +port numbers in brackets like this:
 +
 +<code>
 + Port 1 (2) "Ethernet LAN"
 + Port 2 (4) "Link to KIDDER"
 + Port 3 (5) "Test Port 1"
 + and so on...
 +</code>
 +
 +===== Corrupted Display =====
 +
 +
 +Older versions of QTTermTCP (e.g. 0.0.58) have a bug which loses some
 +data packets, causing a corrupted display. This was reported to G8BPQ
 +and the fixed version should by now be available.
  
 ===== And Finally: ===== ===== And Finally: =====
Line 198: Line 239:
 Please report any errors, omissions or compatibilty issues to Please report any errors, omissions or compatibilty issues to
  
- g8pzt@blueyonder.co.uk+g8pzt@blueyonder.co.uk
  
 or to the xrouter mailing list (where you will also find the latest or to the xrouter mailing list (where you will also find the latest
 versions of XRouter) at versions of XRouter) at
  
- http://groups.io/g/xrouter+http://groups.io/g/xrouter
  
 XRouter documentation can be found at http://ohiopacket.org/xrpi XRouter documentation can be found at http://ohiopacket.org/xrpi
packet/xrouter-qttermtcp.1690636793.txt.gz · Last modified: 2023/07/29 13:19 by m0lte