Hello, All.

$ host f53.n5057.z2.binkp.net
f53.n5057.z2.binkp.net is an alias for fido.roswell.systems. fido.roswell.systems has address 85.113.60.18
fido.roswell.systems has IPv6 address 2001:470:1f1d:92:f1d0:2:5057:53

Best regards, Ivan.

--- GoldED+/LNX 1.1.5-b20130515
* Origin: Area 51 (2:5057/53)

Hi Ivan,

On 2018-07-03 20:09:34, you wrote to All:

$ host f53.n5057.z2.binkp.net
f53.n5057.z2.binkp.net is an alias for fido.roswell.systems. fido.roswell.systems has address 85.113.60.18
fido.roswell.systems has IPv6 address 2001:470:1f1d:92:f1d0:2:5057:53

And here is number 80! ;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Ivan,

On Tuesday July 03 2018 20:09, you wrote to All:

fido.roswell.systems has IPv6 address 2001:470:1f1d:92:f1d0:2:5057:53

+ 19:27 [3584] call to 2:5057/53@fidonet
19:27 [3584] trying f53.n5057.z2.binkp.net [2001:470:1f1d:92:f1d0:2:5057:53]
19:27 [3584] connected
+ 19:27 [3584] outgoing session with f53.n5057.z2.binkp.net:24554
[2001:470:1f:5057:53]
- 19:27 [3584] OPT CRAM-MD5-660738db9b513bbec1cb8e37e1b54aee
+ 19:27 [3584] Remote requests MD mode
- 19:27 [3584] SYS Area 51
- 19:27 [3584] ZYZ Ivan Kovalenko
- 19:27 [3584] LOC Samara, Russia
- 19:27 [3584] NDL 300,CM,IBN,INA:f53.n5057.z2.binkp.net
- 19:27 [3584] TIME Tue, 3 Jul 2018 21:27:39 +0400
- 19:27 [3584] VER binkd/1.1a-16/Linux binkp/1.1
+ 19:27 [3584] addr: 2:5057/53@fidonet
- 19:27 [3584] OPT EXTCMD NR ND NDA GZ BZ2
+ 19:27 [3584] Remote supports EXTCMD mode
+ 19:27 [3584] Remote requests NR mode
+ 19:27 [3584] Remote requests ND mode
+ 19:27 [3584] Remote supports asymmetric ND mode
+ 19:27 [3584] Remote supports GZ mode
+ 19:27 [3584] Remote supports BZ2 mode
- 19:27 [3584] we are in ND mode
- 19:27 [3584] we are in NR mode
+ 19:27 [3584] done (to 2:5057/53@fidonet, OK, S/R: 0/0 (0/0 bytes))
19:27 [3584] session closed, quitting...

Congratulations Ivan. Welcome to the Fidonet IPv6 club!


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hello Michiel!

03 Jul 2018 19:28, Michiel van der Vlist wrote to Ivan Kovalenko:

MvdV> - 19:27 [3584] NDL 300,CM,IBN,INA:f53.n5057.z2.binkp.net
MvdV> Congratulations Ivan. Welcome to the Fidonet IPv6 club!

seems to work with that NDL line, i am sleeping :)

hope its not used in nodelist


Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.1.2 (Linux/4.17.3-gentoo (x86_64))
* Origin: I will always keep a PC running CPM 3.0 (2:230/0)

Hi Ivan!

Tuesday July 03 2018 20:09, you wrote to All:

$ host f53.n5057.z2.binkp.net
f53.n5057.z2.binkp.net is an alias for fido.roswell.systems. fido.roswell.systems has address 85.113.60.18
fido.roswell.systems has IPv6 address 2001:470:1f1d:92:f1d0:2:5057:53

+ 03 Jul 22:07:25 [18168] call to 2:5057/53@fidonet
03 Jul 22:07:26 [18168] trying f53.n5057.z2.binkp.net [2001:470:1f1d:92:f1d0:2:5057:53]...
03 Jul 22:07:26 [18168] connected
+ 03 Jul 22:07:26 [18168] outgoing session with f53.n5057.z2.binkp.net:24554 [2001:470:1f1d:92:f1d0:2:5057:53]
- 03 Jul 22:07:26 [18168] OPT CRAM-MD5-0a2de459f2e6efbab8ba21036e9091ee
+ 03 Jul 22:07:26 [18168] Remote requests MD mode
- 03 Jul 22:07:26 [18168] SYS Area 51
- 03 Jul 22:07:26 [18168] ZYZ Ivan Kovalenko
- 03 Jul 22:07:26 [18168] LOC Samara, Russia
- 03 Jul 22:07:26 [18168] NDL 300,CM,IBN,INA:f53.n5057.z2.binkp.net
- 03 Jul 22:07:26 [18168] TIME Tue, 3 Jul 2018 23:07:26 +0400
- 03 Jul 22:07:26 [18168] VER binkd/1.1a-16/Linux binkp/1.1
+ 03 Jul 22:07:26 [18168] addr: 2:5057/53@fidonet
- 03 Jul 22:07:27 [18168] OPT EXTCMD NR ND NDA GZ BZ2
+ 03 Jul 22:07:27 [18168] Remote supports EXTCMD mode
+ 03 Jul 22:07:27 [18168] Remote requests NR mode
+ 03 Jul 22:07:27 [18168] Remote requests ND mode
+ 03 Jul 22:07:27 [18168] Remote supports asymmetric ND mode
+ 03 Jul 22:07:27 [18168] Remote supports GZ mode
+ 03 Jul 22:07:27 [18168] Remote supports BZ2 mode
- 03 Jul 22:07:27 [18168] we are in ND mode
- 03 Jul 22:07:27 [18168] we are in NR mode
+ 03 Jul 22:07:27 [18168] sending d:\fido\outbound\fidonet\13c10035.dut as 5b3bc998.pkt (890)
+ 03 Jul 22:07:27 [18168] sending 5b3bc998.pkt from 0
+ 03 Jul 22:07:27 [18168] sent: d:\fido\outbound\fidonet\13c10035.dut (890, 890.00 CPS, 2:5057/53@fidonet)
+ 03 Jul 22:07:27 [18168] done (to 2:5057/53@fidonet, OK, S/R: 1/0 (890/0 bytes))
03 Jul 22:07:28 [18168] session closed, quitting...


Have a nice night.
Stas Mishchenkov.

--- NudeGrand
* Origin: Lame Users Breeding. Simferopol, Crimea. (2:460/58)

Good ${greeting_time}, Ivan!

03 Jul 2018 20:09:34, you wrote to All:

$ host f53.n5057.z2.binkp.net
f53.n5057.z2.binkp.net is an alias for fido.roswell.systems. fido.roswell.systems has address 85.113.60.18
fido.roswell.systems has IPv6 address 2001:470:1f1d:92:f1d0:2:5057:53

Should be rejected:

,53,Area_51,Samara,Ivan_Kovalenko,-Unpublished-,300,CM,IBN, INA:f53.n5057.z2.binkp.net

The nodelist line violates the FTS-5004.


--
Alexey V. Vissarionov aka Gremlin from Kremlin
gremlin.ru!gremlin; +vii-cmiii-cmlxxvii-mmxlviii

... that's why I really dislike fools.
--- /bin/vi
* Origin: http://openwall.com/Owl (2:5020/545)

Good ${greeting_time}, Michiel!

03 Jul 2018 19:28:04, you wrote to Ivan Kovalenko:

MvdV> Congratulations Ivan. Welcome to the Fidonet IPv6 club!

I'd insist on rejecting this lam^W FTS-5004 violator.


--
Alexey V. Vissarionov aka Gremlin from Kremlin
gremlin.ru!gremlin; +vii-cmiii-cmlxxvii-mmxlviii

... GPG: 8832FE9FA791F7968AC96E4E909DAC45EF3B1FA8 @ hkp://keys.gnupg.net
--- /bin/vi
* Origin: http://openwall.com/Owl (2:5020/545)

Hello Alexey,

On Wednesday July 04 2018 01:38, you wrote to me:

MvdV>> Congratulations Ivan. Welcome to the Fidonet IPv6 club!

I'd insist on rejecting this lam^W FTS-5004 violator.

Let's give him and his NC a chance to correct it...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20130111
* Origin: Michiel's laptop (2:280/5555.1)

Hello, Michiel.

04 Jul 18 01:11, you wrote to Alexey Vissarionov:

MvdV>>> Congratulations Ivan. Welcome to the Fidonet IPv6 club!

I'd insist on rejecting this lam^W FTS-5004 violator.

Let's give him and his NC a chance to correct it...

My apologies, guys. I've just filed the request to my NC, the NL entry shall be
updated soon.

Best regards, Ivan.

--- GoldED+/LNX 1.1.5-b20130515
* Origin: Area 51 (2:5057/53)

Hello Alexey!

04 Jul 2018 01:37, Alexey Vissarionov wrote to Ivan Kovalenko:

,53,Area_51,Samara,Ivan_Kovalenko,-Unpublished-,300,CM,IBN, INA:f53.n5057.z2.binkp.net

The nodelist line violates the FTS-5004.

kodus to binkp.net provide invalid FTS to dns data


Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.1.2 (Linux/4.17.3-gentoo (x86_64))
* Origin: I will always keep a PC running CPM 3.0 (2:230/0)

Hello Michiel!

04 Jul 2018 01:11, Michiel van der Vlist wrote to Alexey Vissarionov:

MvdV> Let's give him and his NC a chance to correct it...

it basicly there own problem, but binkp.net should reject ina with binkp.net listnings


Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.1.2 (Linux/4.17.3-gentoo (x86_64))
* Origin: I will always keep a PC running CPM 3.0 (2:230/0)

Hello Ivan!

04 Jul 2018 08:38, Ivan Kovalenko wrote to Michiel van der Vlist:

My apologies, guys. I've just filed the request to my NC, the NL entry shall be updated soon.

+1

+ Origin: Area 51 (2:5057/53)

this area :)


Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.1.2 (Linux/4.17.3-gentoo (x86_64))
* Origin: I will always keep a PC running CPM 3.0 (2:230/0)

Dear Benny,

04 Jul 18 19:52, you wrote to Michiel van der Vlist:

MvdV>> Let's give him and his NC a chance to correct it...

it basicly there own problem, but binkp.net should reject ina with binkp.net listnings

Last time I checked, binkp.net did not rely solely on DDN, you could enter any RR for your node manually via a Web page (which I did long ago). So if you have
created a RR for your node in binkp.net, there should be no technical problem using a binkp.net-derived name in the nodelist flags.

The requirement in FTS-5004

If the INA flag (or any of the protocol flags) of any node carries
host name built from the FTN address using DDN or any other method,
that node MUST be skipped and MUST NOT appear in resulting NS zone.
In general, such names SHOULD NOT appear in the nodelist.

has always seemed technically unfounded (or at least the unarticulated "any other method" statement) to me. Does it mean that I can use the INA:fido.sibptus.ru flag all right, but cannot use the INA:node49.net5005.sibptus.ru flag? Why?

Victor Sudakov, VAS4-RIPE, VAS47-RIPN
--- GoldED+/BSD 1.1.5-b20160322-b20160322
* Origin: Ulthar (2:5005/49)

Hello Victor!

05 Jul 2018 12:08, Victor Sudakov wrote to Benny Pedersen:

MvdV>>> Let's give him and his NC a chance to correct it...

it basicly there own problem, but binkp.net should reject ina with
binkp.net listnings

Last time I checked, binkp.net did not rely solely on DDN, you could enter any RR for your node manually via a Web page (which I did long ago). So if you have created a RR for your node in binkp.net, there should be no technical problem using a binkp.net-derived name in the nodelist flags.

i did not know its a webpage aswell, if the web lets users create rr that are not in nodelist, hmm :)

The requirement in FTS-5004

If the INA flag (or any of the protocol flags) of any node carries
host name built from the FTN address using DDN or any other method,
that node MUST be skipped and MUST NOT appear in resulting NS zone.
In general, such names SHOULD NOT appear in the nodelist.

+1

has always seemed technically unfounded (or at least the unarticulated "any other method" statement) to me. Does it mean that I can use the INA:fido.sibptus.ru flag all right, but cannot use the INA:node49.net5005.sibptus.ru flag? Why?

it does not work since binkd only handle single root-domain in binkd.cfg

try in cfg:

root-domain sibptus.ru

and check logs, for this to work its important

node <node-number> * <password>

is used if * is not a star it disables root-domain


Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.1.2 (Linux/4.17.3-gentoo (x86_64))
* Origin: I will always keep a PC running CPM 3.0 (2:230/0)

Dear Benny,

05 Jul 18 06:46, you wrote to me:

MvdV>>>> Let's give him and his NC a chance to correct it...

it basicly there own problem, but binkp.net should reject ina
with binkp.net listnings

Last time I checked, binkp.net did not rely solely on DDN, you
could enter any RR for your node manually via a Web page (which I
did long ago). So if you have created a RR for your node in
binkp.net, there should be no technical problem using a
binkp.net-derived name in the nodelist flags.

i did not know its a webpage aswell, if the web lets users create rr
that are not in nodelist, hmm :)

Yes, it does. It started this way. It is very convenient, and works as a regular DNS zone with a Web editor.

Of course, if you try to register at https://binkp.net/ as 2:5005/49, a Netmail
with a confirmation code will be sent to 2:5005/49. So it's pretty safe, you can create any RR only for your own node.

The requirement in FTS-5004

If the INA flag (or any of the protocol flags) of any node
carries host name built from the FTN address using DDN or any
other method, that node MUST be skipped and MUST NOT appear in
resulting NS zone. In general, such names SHOULD NOT appear in
the nodelist.

+1

has always seemed technically unfounded (or at least the
unarticulated "any other method" statement) to me. Does it mean
that I can use the INA:fido.sibptus.ru flag all right, but cannot
use the INA:node49.net5005.sibptus.ru flag? Why?

it does not work since binkd only handle single root-domain in
binkd.cfg

try in cfg:

I'm not going to put "root-domain sibptus.ru" in binkd's config, that's a silly
idea. I mean that a sysop has the right to put any DNS name she finds necessary
into the INA flag, no matter if it's derived from the FTN address or not. A nodelist has no concept of "root-domain", a DNS name is just a DNS name.

Victor Sudakov, VAS4-RIPE, VAS47-RIPN
--- GoldED+/BSD 1.1.5-b20160322-b20160322
* Origin: Ulthar (2:5005/49)

On 07-05-18 06:46, Benny Pedersen wrote to Victor Sudakov <=-

it does not work since binkd only handle single root-domain in
binkd.cfg

Not entirely correct, it's one root-domain per FTN zone. You don't use root-domain in the config file, you spevify the root domain in the domain definitions. That allows you to use different root domains for different FTNs.

domain fidonet /sbbs/binkd/outbound 3 binkp.net

The last item (after the default zone), if present, is the root-domain.

I do it this way, because (1) it avoids issues with othernets, and (2) it allows me to setup a DNS service for an othernet that I run (haven't got around to doing that yet).


... Life is not a cabaret, it's a circus!
=== MultiMail/Win v0.51
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

On 2018 Jul 05 06:46:42, you wrote to Victor Sudakov:

has always seemed technically unfounded (or at least the
unarticulated "any other method" statement) to me. Does it mean that
I can use the INA:fido.sibptus.ru flag all right, but cannot use the
INA:node49.net5005.sibptus.ru flag? Why?

it does not work since binkd only handle single root-domain in binkd.cfg

binkd.conf does allow for different lookup domains... simply specify them on the domain line...

4D eg:
domain fidonet x:\\bink\\outbound 1 binkp.net
domain foobar x:\\bink\\outbound 1 foobar.org
domain deadbeef x:\\bink\\outbound 1 deadbeef.info

5D eg:
domain fidonet x:\\bink\\out\\fidonet 1 binkp.net
domain foobar x:\\bink\\out\\foobar 11 foobar.org
domain deadbeef x:\\bink\\out\\deadbeef 1111 deadbeef.info

the real question is if the FTN othernets provide DNS zone lookups for their networks that binkp.net provides for fidonet...

try in cfg:

root-domain sibptus.ru

comment that out and never use it again...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... A hot date involving me, you and a dozen habanaros...
---
* Origin: (1:3634/12.73)

Hello, mark.

06 Jul 18 19:25, you wrote to Benny Pedersen:

that I can use the INA:fido.sibptus.ru flag all right, but
cannot use the INA:node49.net5005.sibptus.ru flag? Why?

it does not work since binkd only handle single root-domain in
binkd.cfg

binkd.conf does allow for different lookup domains... simply specify
them on the domain line...

the real question is if the FTN othernets provide DNS zone lookups for their networks that binkp.net provides for fidonet...

try in cfg:
root-domain sibptus.ru

comment that out and never use it again...

Does this mean that the requirement of FTS-5004 to exclude
nodes which have INA flag referring to a fN.nN.zN.example.org
domain is a bit phony? To me, it sounds so, as the legacy software
doesn't (and it obviously can't) rely on it, while it solely
serves to help IP nodes reaching each other.

Let me allow to quote its few statements:

(a) "The fidonet.net domain however was lost for the Fidonet
community in 2011 when the keeper allowed it to expire."

(b) "...it is strongly recommended that implementations that make use
of a DDN service allow the user to easily configure the root domain
and to configure overrides for often used stationary links..."

Keeping in mind quoted above, this one

"If the INA flag (or any of the protocol flags) of any node carries
host name built from the FTN address using DDN or any other method,
that node MUST be skipped and MUST NOT appear in resulting NS zone.
In general, such names SHOULD NOT appear in the nodelist."

doesn't really look good, since as stated in (a), nobody in Fidonet
is able to get the proper domain name anymore, and (b) we're now
on our own. Hence that, it's merely a question of proper implementation
and its configuration.

So, for the resume (though I guess this is the question for Alexey
Vissarionov) -- what's the big difference, on my own example,
between f53.n5057.z2.binkp.net and fido.roswell.systems ?

Best regards, Ivan.

--- GoldED+/LNX 1.1.5-b20130515
* Origin: Area 51 (2:5057/53)

On 2018 Jul 09 14:28:16, you wrote to me:

try in cfg:
root-domain sibptus.ru

comment that out and never use it again...

Does this mean that the requirement of FTS-5004 to exclude
nodes which have INA flag referring to a fN.nN.zN.example.org
domain is a bit phony?

that's a completely different topic than the one about whether binkd supports domain lookups for FTNs other than fidonet... binkp.net provides lookups for fidonet... AFAIK, it does not provide lookups for any other FTNs... i'd be willing to bet their logs are full of lookups for othernets, though...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Laughing stock: cattle with a sense of humor..
---
* Origin: (1:3634/12.73)

On 07-09-18 15:30, mark lewis wrote to Ivan Kovalenko <=-

that's a completely different topic than the one about whether binkd supports domain lookups for FTNs other than fidonet... binkp.net
provides lookups for fidonet... AFAIK, it does not provide lookups for
any other FTNs... i'd be willing to bet their logs are full of lookups
for othernets, though...

Shouldn't be if binkd is properly configured. I bet there's no binkp.net lookups from me for anything other than Fidonet. And one could do domain lookups for othernets, just have to configure the DNS service. I started work on one for vkradio.com (most likely will use bbs.vkradio.com), but haven't got around to putting it all together.


... Morality consists in suspecting other people of not being legally married. === MultiMail/Win v0.51
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

Hello mark,

On Monday July 09 2018 15:30, you wrote to Ivan Kovalenko:

that's a completely different topic

....

Indeed.

So how are you doing with IPv6? I see that your ISP is Windstream (AS7029). Rumour has it that they offer native IPv6 to at least some of their customers. Do they offer IPv6 at your location?

Is your LAN IPv6 ready? When can we welcome you in the Fidonet IPv6 club?

If you want to be in the first 100, you have to hurry up...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

On 2018 Jul 10 07:56:00, you wrote to me:

that's a completely different topic than the one about whether binkd
supports domain lookups for FTNs other than fidonet... binkp.net
provides lookups for fidonet... AFAIK, it does not provide lookups
for any other FTNs... i'd be willing to bet their logs are full of
lookups for othernets, though...

Shouldn't be if binkd is properly configured.

it is questionable, though... i forget which version of binkd brought in the ability to list the lookup domain on the DOMAIN lines but all the binkd versions previous to that used the root-domain line... i expect that there are still some systems out there using OS supplied installations of binkd which are
old v0.9 versions...

I bet there's no binkp.net lookups from me for anything other than Fidonet.

ideally there should not be any since the nodelist is supposed to carry all the
necessary information to connect to a system...

And one could do domain lookups for othernets, just have to configure
the DNS service. I started work on one for vkradio.com (most likely
will use bbs.vkradio.com), but haven't got around to putting it all together.

i've wondered if the binkp.net scripts and methods are documented and available
for others to be able to look over and possibly use as a base to build their own...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Stop violent crime! Make MURDER illegal!
---
* Origin: (1:3634/12.73)

On 2018 Jul 10 13:29:00, you wrote to me:

So how are you doing with IPv6? I see that your ISP is Windstream (AS7029). Rumour has it that they offer native IPv6 to at least some
of their customers. Do they offer IPv6 at your location?

i have IPv6 here but it is only to the ISP modem which is in transparent bridge
mode... IPv6 stops there...

Is your LAN IPv6 ready?

the LAN (wiring and switches) can handle it, sure... but all systems internal to the LANs (there are three of them here with a fourth one in the works) have IPv6 explicitly turned OFF... we are not fans of allowing unmonitored protocol free range on our networks...

When can we welcome you in the Fidonet IPv6 club?

never unless my firewall package adds IPv6 support PLUS the various add-ons we need are also ported to the updated firewall package... we won't mention that the mods needed to add the 4th network must also be able to be easily applied to the updated firewall package, too...

If you want to be in the first 100, you have to hurry up...

good things come to those who wait...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Cat Rule #5: Fit into the smallest space possible
---
* Origin: (1:3634/12.73)

Michiel van der Vlist : mark lewis.
On 10/07/2018 14:29 you wrote:

Is your LAN IPv6 ready?

What do you mean with this?

--
'Tommi

--- HotdogEd/2.13.5 (Android; Google Android; rv:1) Hotdoged/1480338873000 Hotd
* Origin: - nntp://rbb.fidonet.fi - Lake Ylo - Finland - (2:221/360)

Hello Tommi,

On Tuesday July 10 2018 17:53, you wrote to me:

Is your LAN IPv6 ready?

What do you mean with this?

Hmmm.. I realise the question is a bit vague. But I think the answer is clear:

i have IPv6 here but it is only to the ISP modem which is in
transparent bridge mode... IPv6 stops there...

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hello mark,

On Tuesday July 10 2018 09:39, you wrote to me:

i have IPv6 here but it is only to the ISP modem which is in
transparent bridge mode... IPv6 stops there...

Ik think that answers the question I was going to ask.

Is your LAN IPv6 ready?

When can we welcome you in the Fidonet IPv6 club?

never unless my firewall package adds IPv6 support PLUS the various add-ons we need are also ported to the updated firewall package... we won't mention that the mods needed to add the 4th network must also be able to be easily applied to the updated firewall package, too...

What happened to that pioneer spirit of the early Fidonetters? How did you manage to upgrade from IBM Token Ring, ARCNET, Aplle Talk or IPX to TCP/IP?

If you want to be in the first 100, you have to hurry up...

good things come to those who wait...

Not in this case. IPv6 is not a hype that is going to blow over. Sooner or later you will have to convert. The only reward in waiting is missing the boat.

And if you are not interested in joining the Fidonet IPv6 club, why are you here?


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)

Hello mark!

06 Jul 2018 19:25, mark lewis wrote to Benny Pedersen:

binkd.conf does allow for different lookup domains... simply specify
them on the domain line...

4D eg:
domain fidonet x:\\bink\\outbound 1 binkp.net
domain foobar x:\\bink\\outbound 1 foobar.org
domain deadbeef x:\\bink\\outbound 1 deadbeef.info

5D eg:
domain fidonet x:\\bink\\out\\fidonet 1 binkp.net
domain foobar x:\\bink\\out\\foobar 11 foobar.org
domain deadbeef x:\\bink\\out\\deadbeef 1111 deadbeef.info

i only use fidonet in 5d, so not need all this lines with is only usefull for multiple 4d or 5d fidonet zones, when there is only one outgiong hole, all need
to use it

the real question is if the FTN othernets provide DNS zone lookups for their networks that binkp.net provides for fidonet...

try in cfg:
root-domain sibptus.ru

comment that out and never use it again...

its not my domain, so dont care :)


Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.1.2 (Linux/4.17.4-gentoo (x86_64))
* Origin: I will always keep a PC running CPM 3.0 (2:230/0)

Hello, Michiel van der Vlist.
On 10/07/2018 22:07 you wrote:

On Tuesday July 10 2018 17:53, you wrote to me:

Is your LAN IPv6 ready?

What do you mean with this?

Hmmm.. I realise the question is a bit vague.

Ok. :)

'Tommi

--- Hotdoged/2.13.5/Android
* Origin: ipv6 point k6000 (2:221/6.6000)

Hello Tommi!

11 Jul 2018 09:09, Tommi Koivula wrote to Michiel van der Vlist:

Hello, Michiel van der Vlist.
On 10/07/2018 22:07 you wrote:

On Tuesday July 10 2018 17:53, you wrote to me:

Is your LAN IPv6 ready?

What do you mean with this?

Hmmm.. I realise the question is a bit vague.

Ok. :)

is it monday ?


Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.1.2 (Linux/4.17.4-gentoo (x86_64))
* Origin: I will always keep a PC running CPM 3.0 (2:230/0)

Hello, Benny Pedersen.
On 11/07/2018 06:19 you wrote:

On Tuesday July 10 2018 17:53, you wrote to me:

Is your LAN IPv6 ready?

What do you mean with this?

Hmmm.. I realise the question is a bit vague.

Ok. :)

is it monday ?

I don't know, I'm on vacation.

'Tommi

--- Hotdoged/2.13.5/Android
* Origin: ipv6 point k6000 (2:221/6.6000)

Hello Tommi!

11 Jul 2018 09:35, Tommi Koivula wrote to Benny Pedersen:

I don't know, I'm on vacation.

no beer, no problem, skaal :)


Regards Benny

... there can only be one way of life, and it works :)

--- Msged/LNX 6.1.2 (Linux/4.17.4-gentoo (x86_64))
* Origin: I will always keep a PC running CPM 3.0 (2:230/0)

On 07-10-18 09:25, mark lewis wrote to Tony Langdon <=-

Shouldn't be if binkd is properly configured.

it is questionable, though... i forget which version of binkd brought
in the ability to list the lookup domain on the DOMAIN lines but all
the binkd versions previous to that used the root-domain line... i
expect that there are still some systems out there using OS supplied installations of binkd which are
old v0.9 versions...

Yeah the versions I've run all allowed DNS server information on the domain line. I had to go that way, because using root-domain actually broke my othernet polling, even though they had valid node entries, with hardcoded domain names.

I bet there's no binkp.net lookups from me for anything other than Fidonet.

ideally there should not be any since the nodelist is supposed to carry all the
necessary information to connect to a system...

Yep, though I have seen binkd attempt to look up DNS information for othernets, even when there was a node line.

i've wondered if the binkp.net scripts and methods are documented and available
for others to be able to look over and possibly use as a base to build their own...

I have seen scripts in the wild to generate the DNS RRs. Tried one against my nodelist and discovered some syntax errors in my master file, which I subsequently fixed. :)


... Got my tie caught in the fax... Suddenly I was in L.A.
=== MultiMail/Win v0.51
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

Hello, mark.

09 Jul 18 15:30, you wrote to me:

that's a completely different topic than the one about whether binkd supports domain lookups for FTNs other than fidonet... binkp.net

So IMHO again, it's basically all up to configuration.

Best regards, Ivan.

--- GoldED+/LNX 1.1.5-b20130515
* Origin: Area 51 (2:5057/53)

* Originally in ipv6
* Crossposted in binkd

On 2018 Jul 11 12:16:00, you wrote to me:

ideally there should not be any since the nodelist is supposed to
carry all the necessary information to connect to a system...

Yep, though I have seen binkd attempt to look up DNS information for othernets, even when there was a node line.

yes, this was brought up some time in the recent past in the BINKD echo when i asked for an option to turn off DNS lookups and just use node numbers... i don't mind a lookup when i want to poll a domain but i don't need to know IPs for the rest of their AKAs... certainly i don't need the gigs of data from all those lookups stuffing up my pipe...

i've wondered if the binkp.net scripts and methods are documented and
available for others to be able to look over and possibly use as a
base to build their own...

I have seen scripts in the wild to generate the DNS RRs. Tried one against my nodelist and discovered some syntax errors in my master
file, which I subsequently fixed. :)

nice... pointers? i've also cross-posted this to BINKD since it is rather far afield for this area...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Make millions: Start a restaurant called No Stupid Birthday Songs.
---
* Origin: (1:3634/12.73)

On 07-11-18 19:57, Ivan Kovalenko wrote to mark lewis <=-

that's a completely different topic than the one about whether binkd supports domain lookups for FTNs other than fidonet... binkp.net

So IMHO again, it's basically all up to configuration.

Yes, binkd can be configured to look up DNS for any domain you shoose on a domain by domain basis.


... Kettle, plug, fridge, milk, coffee. Yawn.
=== MultiMail/Win v0.51
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

Hello, Tony.

13 Jul 18 17:10, you wrote to me:

that's a completely different topic than the one about whether
binkd supports domain lookups for FTNs other than fidonet...
binkp.net

So IMHO again, it's basically all up to configuration.

Yes, binkd can be configured to look up DNS for any domain you shoose
on a domain by domain basis.

Very nice. Well, with all respect to standarts, I find this FTS-5004 restriction on INA contents redundant and unreasonable.

Best regards, Ivan.

--- GoldED+/LNX 1.1.5-b20130515
* Origin: Area 51 (2:5057/53)

On 07-13-18 13:47, Ivan Kovalenko wrote to Tony Langdon <=-

Very nice. Well, with all respect to standarts, I find this FTS-5004 restriction on INA contents redundant and unreasonable.

Doesn't seem to make any sense.


... Heads will have to roll!
=== MultiMail/Win v0.51
--- SBBSecho 3.03-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

* Originally in ipv6
* Crossposted in ftsc_public

On 2018 Jul 13 13:47:56, you wrote to Tony Langdon:

that's a completely different topic than the one about whether binkd
supports domain lookups for FTNs other than fidonet... binkp.net

So IMHO again, it's basically all up to configuration.

Yes, binkd can be configured to look up DNS for any domain you shoose
on a domain by domain basis.

Very nice. Well, with all respect to standarts, I find this FTS-5004 restriction on INA contents redundant and unreasonable.

perhaps you'd get better results bring it up over in FTSC_PUBLIC where it is better discussed??

TBH, i didn't really understand what you were trying to say and was even more confused when you attached it to my thread which was about something completely
different...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... An honest politician is one who, when bought, stays bought.
---
* Origin: (1:3634/12.73)

Dear Ivan,

13 Jul 18 13:47, you wrote to Tony Langdon:

Very nice. Well, with all respect to standarts, I find this FTS-5004 restriction on INA contents redundant and unreasonable.

+1

Victor Sudakov, VAS4-RIPE, VAS47-RIPN
--- GoldED+/BSD 1.1.5-b20160322-b20160322
* Origin: Ulthar (2:5005/49)