NRAU BALTIC støttes i DXLOG

Published: Monday, 13 February 2017

DX LOG har støtte for NRAU BALTIC CONTEST 10 januar

1. Du kan laste ned denne gratis her http://dxlog.net/ -> velg Download eller her last ned http://dxlog.net/sw/files/DXLog.net-2.5.5.msi

Installasjon

Programmet installeres i C:/programfiler/DX-log

Loggene finner du i C:/Brukere/(Brukernavn)/Documents/DX-LOG/

Oppstart

Start programmet som vanlig

velg File > NEW

Informasjon

Full ut informasjon som Callsign, Lokator Exchange etc. Adresse.

Velg Contest, Kategori, Mode, Overlay klasse, Effekt,Operatører og så OK !

ENTRY

Autostart med loggvalg

Ved oppstart kan du få loggen til å poppe opp automatisk ved å velge Option > Load contest at startup > V Enabled.

Velge vinduer man vil ha oppe i loggen

For å få opp nyttige vinduer man vil bruke så velger du Windows knappen på menyen.

Generell oppsett av radioen og programmet kan du finne på engelsk her

Konfigurere radioen

Du kan sette opp kommunikasjon for en eller to radioer i DX log.

OPTIONS > Configer Interfaces

Port konfigurasjon

1. Aktiver lydkort om du skal kjøre SSB

2. Aktiver comport 1 for Radio 1 (Hvis dette er comport for radio).

3. Comport 4 for Winkey CW

4. Comport 2 for å veksle lyd hvis du har 2 radioer eller MK2R boks.

Oppsett av radio Kenwood

Kenwood TS950/TS850 har 4800 baud

Kenwood TS2000/TS480/TS870 har 9600 baud.

Yaesu FT2000 etc har 38400 baud som standard.

Icom 19200 baud + CI-V adresse.

Sett opp Winkey

Sett opp PTT

Cabrillo

MULTI OP !

http://dxlog.net/docs/index.php/Additional_Information#Networking_over_internet

Networking over internet

When, for instance, activating a special event callsign it is possible to network multiple DXLog stations over the internet.

VLAN/VPN

The most secure way for remote networking is to rely on a VLAN (virtual LAN) software. There are several available such as:

Hamachi https://www.vpn.net/
FreeLan http://www.freelan.org/
Player.me https://player.me/
ZeroTier https://www.zerotier.com/
OpenVPN https://openvpn.net/

Each VLAN solutions have their own particular set up which is covered in their respective documentations.
With a VLAN solution, all DXLog configurations are the same as when operating in a regular LAN.

One weakness with connections over the internet (a.k.a. WAN), including VLAN solutions, is that they are prone to packet loss.
Packet loss is disastrous to DXLog's (or any logger's) standard UDP networking.

It is therefore absolutely necessary to run ONLY TCP networking over a VLAN.

Hamachi is particularly popular since it is free for up to five computers. Thanks to the communications
architecture of DXLog, this translates into up to five geographical locations.

Since DXLog is able to mix TCP and UDP networking, a distributed station set up should be configured to rely on TCP
for the wide-area network and UDP for the local network at each station location. Below you will find the station
set up for the Swedish HQ station SE9HQ in the 2019 IARU HF Championship. The DXLog.net.DXC cluster client was run
on SK3W-A which distributed spots to all stations over the network. inband interlock was used at the SK3W location.

Important to note:

For the server as well as the main clients, Server IP should be set to the server's VLAN IP address, not its LAN address.
The server should check both "Start networking server" and "UDP network broadcast for multiple stations".
The main clients should check both "Connect as network client" and "UDP network broadcast for multiple stations".
All other stations should check only "UDP network broadcast for multiple stations".
Interlock over VLAN does not work reliably because of packet loss.

Therefore, it is important to configure any interlock to only consider relevant operating positions,

which all must be local. Use the possibility to only consider named stations for the interlock in the software

interlock set up. Options|Networking|Software interlock "Custom station ID(s)"

For a large set-up with many stations connecting as clients to a central server you may overload the server if you also

distribute spots via all client-server connections. In this case, check the "No spots via client/server" option

on all stations and use local DX cluster connections via UDP at each location.

Port forwarding

If you are less worried about competitors or government agencies listening in on your contest data,
it is possible to route the traffic directly over the internet using port forwarding at the server.

Important security notice: This solution is not without risk. It offers no security or authentication.
Any DXLog station running the same contest configuration, knowing the URL or IP address and IP port of the
server can connect to the server station. There are no means to disconnect a station by force.

With a port forwarding solution, the following must be observed:

Server configuration

Only one of the stations should be configured as the server.
"Connect as client" should not be checked and "UDP network broadcast" should only be enabled if it is

used to communicate with other stations on the same LAN.

The PC acting as server must have a fixed LAN IP address. This is done either by manually configuring the

PC to use a fixed LAN IP address, or by setting up the router in the server's LAN to to always allocate

the same IP address to it.

The internet connection used by the server PC must either have a fixed public IP

address or use dynamic DNS. Otherwise clients will not be able to reliable connect over the internet.

The server's TCP/IP port (default 9888) must be forwarded to the internet by configuring the router

connecting the server's LAN to internet. Only TCP traffic should be forwarded.

DXLog UDP traffic is not carried well over the internet.

Example configuration for server for networking over internet

Example of port forwarding UI in router

All other stations

All other PC in the multi-station set up should be set up as TCP clients.
Over the internet, "Server IP" is either the public IP address of the server's internet

connection (e.g. 5.150.248.52) or the dynamic DNS address (e.g. hq.sm7iun.se).

Clients connecting over the internet does not have to enable UDP networking and should not enable a server.

A client may connect via UDP if it is on the same LAN as the server or a "master client".

A "master client" is a client that connects to the server using the "connect as client" option in

the networking set up panel. A "master client" can act as a UDP gateway which means that if

several computers on a LAN are part of the same multi station set up but the server is located

elsewhere, only one computer in that LAN needs to connect as a client and the rest can use UDP.

Software interlock is UDP-based and can reliably only be used locally. Never over the internet.

Example configuration of client for networking over internet

In a multi-station setting it is recommended to enable Options|Networking|Don't allow QSO logging if operator isn't logged
Make sure Options|Enable network is checked.