Problem with 5030/74

Michiel van der Vlist написал(а) к All в Dec 17 17:40:06 по местному времени:

Нello All,

Can one of you Russian speaking guys please help this guy? The problem appears to be that his firewall blocks the binkp port on IPv6.

+ 17:37 [3844] call to 2:5030/74@fidonet
17:37 [3844] trying f74.n5030.z2.binkp.net [2a05:3580:de00:1687:21f:c6ff:fe1e:b46a]...
? 17:37 [3844] connection to 2:5030/74@fidonet failed: {W32 API error
10061} Connection refused
17:37 [3844] trying f74.n5030.z2.binkp.net [188.242.45.253]:24554...
17:37 [3844] connected
+ 17:37 [3844] outgoing session with f74.n5030.z2.binkp.net:24554 [188.242.45.253]
- 17:37 [3844] OPT CRAM-MD5-1e1b687cd636d9d9c562bf87872725ee
+ 17:37 [3844] Remote requests MD mode
- 17:37 [3844] SYS Cat's Shadow
- 17:37 [3844] ZYZ Michael Skolsky
- 17:37 [3844] LOC Saint-Petersburg, Russia
- 17:37 [3844] NDL 4M,TCP,BINKP,ICM,INA:cats-home.net
- 17:37 [3844] TIME Mon, 18 Dec 2017 19:37:49 +0300
- 17:37 [3844] VER binkd/1.1a-47/Linux binkp/1.1
+ 17:37 [3844] addr: 2:5030/74@fidonet

Tnx.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303

Alexey Vissarionov написал(а) к Michiel van der Vlist в Dec 17 21:01:20 по местному времени:

Доброго времени суток, Michiel!
18 Dec 2017 17:40:06, ты -> All:

MvdV> Can one of you Russian speaking guys please help this guy? The
MvdV> problem appears to be that his firewall blocks the binkp port on
MvdV> IPv6.

MvdV> [2a05:3580:de00:1687:21f:c6ff:fe1e:b46a]...
MvdV> ? 17:37 [3844] connection to 2:5030/74@fidonet failed: {W32 API
MvdV> error 10061} Connection refused
MvdV> [188.242.45.253]:24554...
MvdV> 17:37 [3844] connected

% nc -6 cats-home.net 24554

with

# tcpdump -nlvv host 2a05:3580:de00:1687:21f:c6ff:fe1e:b46a

in parallel, results in:

20:45:51.832045 IP6 (hlim 64, next-header: TCP (6), length: 32) 2a01:4f8:221:3dc1:900d:f001:dead:f001.37076 > 2a05:3580:de00:1687:21f:c6ff:fe1e:b46a.24554: S, cksum 0x61f7 (correct), 101011674:101011674(0) win 14400 <mss 1440,nop,nop,sackOK,nop,wscale 7>

20:45:51.869458 IP6 (hlim 55, next-header: TCP (6), length: 20) 2a05:3580:de00:1687:21f:c6ff:fe1e:b46a.24554 > 2a01:4f8:221:3dc1:900d:f001:dead:f001.37076: R, cksum 0xd7e1 (correct), 0:0(0) ack 101011675 win 0

So, most likely the binkd there simply listens only at IPv4.


--
Alexey V. Vissarionov aka Gremlin from Kremlin
gremlin ПРИ gremlin ТЧК ru; +vii-cmiii-ccxxix-lxxix-xlii

... Чем умные отличаются от дураков? Умные дурачатся, а дураки умничают.
--- /bin/vi

Michiel van der Vlist написал(а) к Alexey Vissarionov в Dec 17 20:45:29 по местному времени:

Нello Alexey,

On Monday December 18 2017 21:01, you wrote to me:

AV> So, most likely the binkd there simply listens only at IPv4.

Maybe. But in that case I would expect a time-out rather than a connection refused.

So maybe you can contact him to help solve the problem?

The Ipv6 list now counts 58 nodes. It would be nice if we could make it 60 by the end of the year.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303

Alexey Vissarionov написал(а) к Michiel van der Vlist в Dec 17 23:11:32 по местному времени:

Доброго времени суток, Michiel!
18 Dec 2017 20:45:28, ты -> мне:

AV>> So, most likely the binkd there simply listens only at IPv4.
MvdV> Maybe. But in that case I would expect a time-out rather than a
MvdV> connection refused.

Answer with TН_RST flag set is a normal way for the OS kernel to reject connection to a port nothing listens on.

MvdV> So maybe you can contact him to help solve the problem?

Unlikely.

MvdV> The Ipv6 list now counts 58 nodes. It would be nice if we could
MvdV> make it 60 by the end of the year.

I'll write in R50.SYSOP.DRUNK with this idea.
Possibly, there would be 64...


--
Alexey V. Vissarionov aka Gremlin from Kremlin
gremlin ПРИ gremlin ТЧК ru; +vii-cmiii-ccxxix-lxxix-xlii

... Пока теоретики рисуют карты, практики меняют ландшафты
--- /bin/vi

Michiel van der Vlist написал(а) к Alexey Vissarionov в Dec 17 01:12:25 по местному времени:

Нello Alexey,

On Monday December 18 2017 23:11, you wrote to me:

AV> Answer with TН_RST flag set is a normal way for the OS kernel to
AV> reject connection to a port nothing listens on.

So your theory is that his binkd listens on IPv4 only.

MvdV>> So maybe you can contact him to help solve the problem?

AV> Unlikely.

Why? Нe advertises IPv6 connectivity. Won't you help him to get his function to perform as advertised?

MvdV>> The Ipv6 list now counts 58 nodes. It would be nice if we could
MvdV>> make it 60 by the end of the year.

AV> I'll write in R50.SYSOP.DRUNK with this idea.
AV> Possibly, there would be 64...

Great!, ;-)


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303

Michael Skolsky написал(а) к Alexey Vissarionov в Dec 17 14:53:40 по местному времени:

Привет, Alexey!

18 дек 17 21:01, Alexey Vissarionov -> Michiel van der Vlist:

AV> 20:45:51.832045 IP6 (hlim 64, next-header: TCP (6), length: 32)
AV> 2a01:4f8:221:3dc1:900d:f001:dead:f001.37076 >
AV> 2a05:3580:de00:1687:21f:c6ff:fe1e:b46a.24554: S, cksum 0x61f7
AV> (correct), 101011674:101011674(0) win 14400 <mss
AV> 1440,nop,nop,sackOK,nop,wscale 7>

AV> 20:45:51.869458 IP6 (hlim 55, next-header: TCP (6), length: 20)
AV> 2a05:3580:de00:1687:21f:c6ff:fe1e:b46a.24554 >
AV> 2a01:4f8:221:3dc1:900d:f001:dead:f001.37076: R, cksum 0xd7e1
AV> (correct), 0:0(0) ack 101011675 win 0

AV> So, most likely the binkd there simply listens only at IPv4.


У меня сложилось такое же впечатление.

- 19 Dec 13:13:58 [1394] incoming from 2607:5300:100::43d (36040)
? 19 Dec 13:13:58 [2823] getpeername: Transport endpoint is not connected
+ 19 Dec 13:13:58 [2823] incoming session with unknown
? 19 Dec 13:13:58 [2823] recv: Connection reset by peer
+ 19 Dec 13:13:58 [2823] done (?, failed, S/R: 0/0 (0/0 bytes))
19 Dec 13:13:58 [2823] session closed, quitting...

Если кто подскажет, куда копать -- было б здорово. С маху не увидел настроек IPv6 для входящих соединений в шаблоне конфига BinkP.
IPv6 завёлся относительно недавно, пока не всё на домашнем сервере настроено.

С наилучшими пожеланиями, Michael.

--- -cats-home.net

Michiel van der Vlist написал(а) к Michael Skolsky в Dec 17 13:30:10 по местному времени:

Нello Michael,

On Tuesday December 19 2017 14:53, you wrote to Alexey Vissarionov:

AV>> So, most likely the binkd there simply listens only at IPv4.

MS> У меня сложилось такое же впечатление.

I don't know what you did but you fixed it!

+ 12:38 [112] call to 2:5030/74@fidonet
12:38 [112] trying f74.n5030.z2.binkp.net [2a05:3580:de00:1687::220]...
12:38 [112] connected
+ 12:38 [112] outgoing session with f74.n5030.z2.binkp.net:24554
[2a05:3580:de00:1687::220]
- 12:38 [112] OPT CRAM-MD5-162d02a84becd977051f2cb526310dee
+ 12:38 [112] Remote requests MD mode
- 12:38 [112] SYS Cat's Shadow
- 12:38 [112] ZYZ Michael Skolsky
- 12:38 [112] LOC Saint-Petersburg, Russia
- 12:38 [112] NDL 4M,TCP,BINKP,ICM,INA:cats-home.net
- 12:38 [112] TIME Tue, 19 Dec 2017 14:38:36 +0300
- 12:38 [112] VER binkd/1.1a-47/Linux binkp/1.1
+ 12:38 [112] addr: 2:5030/74@fidonet

Congratulations and welcome to the Fidonet IPv6 club!


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303