Text 5484, 140 rader
Skriven 2013-01-07 00:50:18 av FidoNews Robot (2:2/2.0)
Ärende: FidoNews 30:01 [03/10]: Getting Fidonet Technical
=========================================================
=================================================================
                    GETTING FIDONET TECHNICAL
=================================================================

                           BBS name field
                  Stas Degteff 2:5080/102@fidonet

Nodelist issue: What (and who) binkp-capable nodes uses BBS name field
for the indication of actual host name or IP address.

Preamble.

Between members of the Fidonet Standard Technical Comittee discuttion
is conducted about usage a 3th field of the node line in the nodelist
(BBS name field). This discuttion induced me to make small research: I
selected all nodes with records contain somewhere like host name or IP
address in the nodelist, next I checked these values for validity and
another.

Method of research.

I use unixtools (grep/egrep, cut, sort, wc, string), networktools
(telnet) and nmap program in the GNU/Linux enviroment. I take 1st
fidonet nodelist of the 2013 produced by Ward Dossche for Zone 2:
nodelist.001 at 1 jan 2013.

I use following commands to select data from nodelist:
  grep -v '^;' nodelist.001
  - for drops all comment lines;
  cut -d , -f 3
  - for take 3th field from node lines;
  egrep '([A-Z].+)?,[0-9]+,[0-9]+\.[0-9.]+,'
  - for select nodes with IPv4 address in the 3th field;
  egrep -i '([A-Z].+)?,[0-9]+,\[[0-9a-f]+:[0-9a-f:]+\],'
  - for select nodes with IPv6 address in the 3th field;
  egrep -i '([A-Z].+)?,[0-9]+,[[:alnum:]]+\.[[:alnum:].-]+[a-z]{2},'
  - for select nodes with some like host name in the 3th field;
  egrep 'IBN:[0-9]+(,|.$)'
  - for select nodes with port specified in the IBN flag;
  cut -d , -f 3 | egrep -v '(_|fidonet\.net)'
  - for exclude ahead invalid values in the 3th field ("_" are invalid
    char for the host name according RFC 1035, "fidonet.net" are lost
    domain name for fidonet community);
  egrep -v ',INA:'
  - for exclude nodes with hostname or IP address specified in the INA
    flag;
  egrep -i ",IBN:[0-9a-z-]+\.[0-9a-z.-]+(,|.$)"
  - for select nodes with hostname or IP address specified in the IBN
    flag;
  egrep ",IBN:[0-9]+(,|.$)"
  - for select nodes with port specified in the IBN flag;
  sort -u | wc -l
  - for count unique values;
  nmap -sT -p24554 (hosts list)
  - for mass-testing binkp port on many hosts.

In the several cases I use manual operations for node alive testing. I
look an alternate port in the "IBN:portnumber" field and I used
"telnet" program to connect to his port of host presented in the 3th
field. If telnet returned binkp handshake sequence, I tried to extract
(FTN) address of the node using a "string" utility.

Results of research.

1. Nodes with IPv6 address in the BBS name field: none.
2. Nodes with IPv4 address in the BBS name field: 9 all, 7 unique IP
   addresses.
3. Nodes with hostname-like value in the BBS name field: 291 all, 274
   unique, 81 with fidonet.net hierarhy (80 unique). 194 approaches to
   real host names.
4. Nodes with IPv4 address in the BBS name field and nor
   "INA:host_or_address" nor "IBN:host_or_address" flags: 5 unique IP.
5. Nodes with hostnames in the BBS name field and nor
   "INA:host_or_address" nor "IBN:host_or_address" flags (part of 194
   nodes): 146 unique (and tested later).
6. Tested nodes with IPv4 address in the BBS name field and nor "INA:"
   nor "IBN:host_or_address" flags (5 unique IP addresses): 2 hosts
   up, but only one host replies with binkp.
7. Tested nodes with approaches to real host name in the BBS name
   field and nor "INA:host_or_address" nor "IBN:host_or_address" flags
   (make test for standard binkp port 24554): 144 unique hosts, 113 IP
   addresses resolved, 75 hosts up and only 52 nodes replied on binkp.
8. Special case - test nodes with approaches to real host name in the
   BBS name field and nor "INA:host_or_address" nor
   "IBN:host_or_address" flags but with port number in "IBN:port":
   - 2:222/42 replies on specified 200/TCP with binkp;
   - 2:2432/344 AKA 2:2432/348 replies on specified 24555/TCP with
     binkp, and repries on standard 24554/TCP with binkp with AKA
     2:2432/349 (third node of same sysop), separate node with
     alternate port is not needed for this case.
9. Nodes wih IP address in 3rd field and nonstandard port is not exist
   in nodelist.

Some selective control tests.

A. Tested nodes with IPv4 address in the BBS name field and presented
   "INA:":
  - 2:5020/214 - IP in the 3rd field same as in "INA:";
  - 2:5020/4441 - IP in the 3rd field different with hostname in
    "INA:" and node replies only on hostname specified in "INA:" flag
    (3rd field contain invalid IP address or not an IP address but
    only similar to IP address).
B. Nodes with different information in the "INA:" and 3rd field:
  - 2:5011/92 - "izverg.no-ip.info" in the 3rd field and invalid
    (outdated) "INA:f92.n5011.z2.fidonet.net", node don't reply on
    binkp;
  - 2:5000/54 - "f54.n5000.z2.fidonet.net" in the 3rd field are
    invalid and connect to "fido.olmisoft.com" (taken from
    "INA:fido.olmisoft.com") rejected;
  - 2:464/95 - "pedal.isd.dp.ua" in the 3rd field are invalid because
    resolved to nonroutable (intranet) IP address 10.98.3.58 (see
    RFC1918);
  - 2:2437/224 - "travelbit.dyndns.org" in the 3rd field and
    "INA:travelbit.servebeer.com" resolved to same IP;
  - 2:2/1002 - "fidonet.org" in the 3rd field is not node's hostname
    but address of mail server, host name looks in
    "INA:many-glacier.mine.nu".

Corollaries.

BBS name field uses for present actual information about connectivity
very few nodes (53 from 3100 non-technical nodes) and this method may
be recognized the outdated now and should be obsoleted in the official
documents.

Respectively I will delete this way from my DDN-script and DDN
generating on my node - nodelist.grumbler.org. (See FTS-5004 or
FSP-1035 "DNS Distributed Nodelist" for information about DDN.)

Done.

If you want to discuss with me, you may write message to "FIDONEWS"
echo but please type "Stas Degteff" into "TO:" field that I saw this
message in carboncopies area. Or you may write netmail to me.


-----------------------------------------------------------------

--- Azure/NewsPrep 3.0
 * Origin: Home of the Fidonews (2:2/2.0)