= Сообщение: 3721 из 12527 ====================================== ENET.SYSOP = От : Benny Pedersen 2:230/0 22 Apr 16 22:15:18 Кому : Kees van Eeten 22 Apr 16 22:15:18 Тема : tcp flags, but missing ina hostname FGHI : area://ENET.SYSOP?msgid=2:230/0+571aa393 На : area://ENET.SYSOP?msgid=2:280/5003.4+571a6ea7 = Кодировка сообщения определена как: LATIN-1 ================================ ============================================================================== Hello Kees!
22 Apr 2016 20:19, Kees van Eeten wrote to Benny Pedersen:
BP>> can errorflags not check if ibn is listed in flags, but at same time BP>> no ina hostname to connect to ? KvE> No errorflags can't and probably should not do that.
why not ?
KvE> As you I do not understand the use of the IBN flag if no contact KvE> information can be found anywhere.
i see only ibn flags, no port, no hostname
KvE> when 2:0/0 was listed with a IBN flag and no contact information, KvE> some complained, while the same people will defend the listing if the IBN KvE> flag without contact information for e.g Pvt nodes.
so might be old hobby to make it bad
BP>> example nodes 2:201/148 and 2:201/499, possible there is others out BP>> there, how the heck should i connect ot them ? KvE> There are many nodes that have IBM flag and no INA hostname.
nodes do care
KvE> Standard procedure is to then look for fx.nx.zx.binkp.net.
seems that it uses station name to make cname dns, hmm
KvE> There are 23 nodes in the nodelist that will then return a IP KvE> address, the two you mentions are not among them.
i let ward take it, if he want it
Regards Benny
... there can only be one way of life, and it works :)
--- Msged/LNX 6.2.0 (Linux/4.5.0-gentoo-r1 (i686)) * Origin: openvpn on its way here (2:230/0)
