*** IMPORTANT ***
A "flag", before each section, indicates which platform is concerned by the
Q/A.
	[L]	Linux only
	[D]	DOS only
	[W]	Windows only


-------------------------------------------------------------------------------
[LDW] DXNet is working stable, gets connected and transmits and receives data,
like announcements, wwv, wcy. However for some reason it doesn't perform its
 core business: transmitting and receiving DX messages.
-------------------------------------------------------------------------------
	Try setting the PC time to UTC or use the set/tz command in DXNET...

	73 de Aurelio-pa3ezl

-------------------------------------------------------------------------------
[L] Each time dxnet crashes, a "core" file appairs in the work directory.
What can I do with this ?
-------------------------------------------------------------------------------
	
	When dxnet crashes for any reason it generates a coredump (core) 
	which may be usefull knowing why it crashed.
	
	The binary which is installed when you issue a "make install" is
	not so usefull because it has been stripped (all debug info are
	gone). If you want to play with coredumps, you must install
	the debug binary of dxnet. Just copy the one which has been
	compiled : 
		
		cp /usr/local/src/dxnetsrc/dxnet/dxnet /usr/local/dxnet/
	
	That way the next time dxnet will crash a core will be copied by the
	system in the work directory of dxnet. To learn more on the reason
	dxnet crashed, you can ie gdb which is a powerfull text-mode debuger.
	
		Run gdb : gdb dxnet --core=core
	
	Then send a copy of what you get to olecam@online.fr. Don't forget
	to specify what version of dxnet has generated this core.

	
-------------------------------------------------------------------------------
[L] When dxnet crashes it doesn't generate any coredump. What can I do ?
-------------------------------------------------------------------------------

	It depends of the settings of you installation. The easier way
	to get this cured is to add the following row in your dxnet.sh, 
	just before the	one which starts dxnet :
	
		ulimit -c unlimited
	


-------------------------------------------------------------------------------
[LDW] How to create a connection script file ?
-------------------------------------------------------------------------------

        When you get to the level where you need to make a forward script
        the best thing to start with is go through the entire connect path
        'by hand' and carefully note the text that you get back in each
        packet. This is helpfull to find the correct 'trigger' text to
        include in the script. To give you an example.

        I want to figure out the path to a neighbour node PA3GOJ-8
        (CLX-node). I know my first 'stop' is a gateway, PI5EHV. From there
        I have to telnet to an ampr.org address on a certain port. After
        logging in I will then be connected directly to PA3GOJ-8-clx-cluster.


        Here is the output (broken down) to find the entries in pa3goj.fwd
        file.

        '>>>' commands that I send BY HAND
        '>' Text that I receive back

        [aurelio@wendy aurelio]$ >>>telnet claudia
                                    ^connect to PI5EHV (claudia.esrac.ele.
                                    tue.nl)
        >Trying 131.155.192.179...
        >Connected to claudia.
        >Escape character is '^]'.
        >
        >FlexNode v0.4c (pi5ehv.ampr.org)
        >
        >login: >>>pi5ehv-8
                   ^^^^^^^^ I need to login at PI5EHV by sending my callsign,
                            no password required.


        >FlexNode v0.4c - ESRAC:PI5EHV - Help: ? - Cluster: DX - Convers:
         W - Xnet: X
        >*** Please NO SOFTWARE downloading via the laps
        >*** Last login: Mon Feb 26 19:32:48
        >***      From: 131.155.192.173
        
        >=>
        >>> t pa3goj 41112
            ^^^^^^^^^^^^^^ Telnet to pa3goj(.ampr.org) on port 41112

        >ESRAC:PI5EHV} Trying pa3goj.ampr.org:41112... Type <RETURN> to abort
        >ESRAC:PI5EHV} Connected to pa3goj.ampr.org:41112 (Escape: CTRL-Y)
        >Welcome to the clx gateway - you logged in from 44.137.24.19/1472.
        >Your callsign:>>>pi5ehv-8
                           ^^^^^^^^ I enter the callsign (normally equal to
                                    your dxnet callsign)
        >Password:>>> <password>
        >Hello pi5ehv-8, you were validated - now connecting to clx.
        >*** connected to clx
        ^^^^^^^^^^^^^^^^^^^^^ We are connected! The next packet should have
                              the PC18^ stuff etc..
        >>>^Y
           ^^ I force a disconnect

        So.. now I have enough information to create the pa3goj.fwd file.
        Here you see the result.

        ##### START of pa3goj.fwd
        PA3GOJ-8
        .c inet PA3GOJ-8 131.155.192.179
                         ^^^^^^^^^^^^^^^ IP number of claudia
                Then one packet before the 'login' ext is
                >FlexNode v0.4c (pi5ehv.ampr.org)
                So I will trigger my next command after receiving
                'FlexNode' string
        +FlexNode
        ^^^^^^^^^ After DXNET sees this string it has to send the login
                  string, i.e. pi5ehv-8
        .pi5ehv-8
        ^^^^^^^^^ I have to make sure I'm logged in properly before starting
                  the telnet to pa3goj. So wait until 'FlexNode' string is
                  received
                  >FlexNode v0.4c - ESRAC:PI5EHV - Help: ? - etc...

        +FlexNode
        .t 44.137.4.25 41112
        ^^^^^^^^^^^^^^^^^^^^ Send Telnet command
        +Connected
        ^^^^^^^^^^ Wait until 'Connected' string is received..
                   >ESRAC:PI5EHV} Connected to pa3goj.ampr.org:41112
                   (Escape: CTRL-Y)

        #10
        ^^^Wait 10 seconds to receive the 'Connected' string. If it's not
           received ABORT connect script.

        .pi5ehv-8\n<password>
        ^^^^^^^^^^^^^^^^^^^^^ This might be confusing! DXNET will ONLY
                              evaluate a received line if that line was
                              terminated with an EOL character. CLX will
                              NOT send an EOL character after:
                              '>Your callsign:'. Same goes for '>Password:'.
                              The '\n' between pi5ehv-8 and <password>
                              FORCES DXNET to send first 'pi5ehv-8' then a
                              'RETURN character' and then the 'password'.

        +validated
        ^^^^^^^^^^ Now we need to wait for the FIRST packet with 'PC18^'
                   string. Here it's important to trigger on a string of
                   text in the packet JUST BEFORE the packet with 'PC^18'.
                   Of course the line of the trigger string needs to have an
                   EOL character. In DXNET 4.1 it's actually NOT necessary to
                   trigger on a string out of the packet before the packet
                   with PC18. You can instead safely choose 'PC18' as string!!!
                   Thanks to Olivier!
        #30
        ^^^ Wait 30 seconds for 'validated' string. If it's not received..
            abort connect script.

        #### END OF pa3goj.fwd

        Okay, I hope this elaborate example will shed some light on how to
        make a working .fwd script file. If there are still things unclear
        let me know.

        Best 73 & GL!
        Aurelio-pa3ezl/aa2wh


-------------------------------------------------------------------------------
[LW] How to connect to a remote cluster via internet ?
-------------------------------------------------------------------------------

	That is only possible from dxnet itself if you're using either the
	linux or windows version. For the DOS one, the only way is to 
	connect through any kind of gateway (dxtelnet, jnos, ...)

	This is script connection example given by Jean, VE2PKT :
	
	--- k1xx.fwd ---
	K1XX
	.C inet k1xx 205.247.190.48 2323
	+ultranet.com
	.ve9emo-9\rpassword\r
	+K1XX
	.c sl0 k1xx
	+K1XX


-------------------------------------------------------------------------------
[LW] I want my cluster to be connectable from the Internet. What do I have to
do for ?
-------------------------------------------------------------------------------

	[Windows-specific] AGWpe has nothing to do for that stuff in the dxnet
	settings. DxNet can even works without AGW if it is intended to run a 
	"TCP/IP only" cluster.

	To configure dxnet for listening a TCP/IP port, add the following row 
	in ~\dxnet\system\dxnet.cfg. This can be entered on the console as well
	but dxnet won't remamber this setting the next time you restart it.

		set/port inet:<nnnn>

	where <nnnn> is the port number (ie : set/port inet:9000). 

	Then, to connect to dxnet from the Internet, just open a telnet session
	like following :

		TELNET <your_ip_address> 9000

	If you're telneting from the computer dxnet is running on, you can of
	course use "localhost" rather than your IP address :

		TELNET localhost 9000

	Notice that, by default, dxnet will ask the incoming user for a 
	password and the connection will be established only if he has been
	already registred by the sysop. If you prefer to open freely to 
	everybody, add the following command in ~\dxnet\system\dxnet.cfg :

		SET/TELNET OPEN

	Then the first time a new user will connect via TELNET, dxnet will
	prompt for a password and it will generate automaticaly a new entry in
	the password database.


-------------------------------------------------------------------------------
[LW] I don't want to reject the telnet users wich are not registred yet. I 
prefer to get my cluster telnetable by everybody. What do I have to 
do ?
-------------------------------------------------------------------------------

	See "I want my cluster to be connectable from the Internet. What is
	the prefered way ?" question.

	Remark : only a callsign is acceptable as login. Any entry which does 
	not look to be a valid callsign will be rejected.

