14 Mar 12 13:26, mark lewis wrote to james coyle:

Some people stated (unless I am misunderstanding) that they paid
for the 1000 node Linux version, got the key, and the software does
not even execute on Linux.

no... the problem is that it cannot perform domain name lookups
because it uses an old method that is no longer supported by the
newer libs... it works just fine with IP numbers, though...
especially since there is no DNS lookup for them ;)

DNS lookups in the Windows version works just fine.


R\%/itt


... Only those who will risk going too far can possibly
... find out how far one can go ~ TS Eliot


--- Twit(t) Filter v2.1 (C) 2000-10
* Origin: SATX Alamo Area Net * South * Texas, USA * (1:387/22)

Hello Roy!

14 Mar 2012 11:23, Roy Witt wrote to mark lewis:

DNS lookups in the Windows version works just fine.

sure ?, does it use binkp.net now ?

----- binkp.net begins -----

; <<>> DiG 9.8.1 <<>> f0.n230.z2.binkp.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44629
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 5, ADDITIONAL: 5

;; QUESTION SECTION:
;f0.n230.z2.binkp.net. IN A

;; ANSWER SECTION:
f0.n230.z2.binkp.net. 172767 IN CNAME home.junc.org.
home.junc.org. 43167 IN A 2.104.223.10

;; AUTHORITY SECTION:
junc.org. 42091 IN NS ns5.gratisdns.dk.
junc.org. 42091 IN NS ns4.gratisdns.dk.
junc.org. 42091 IN NS ns3.gratisdns.dk.
junc.org. 42091 IN NS ns2.gratisdns.dk.
junc.org. 42091 IN NS ns1.gratisdns.dk.

;; ADDITIONAL SECTION:
ns1.gratisdns.dk. 26934 IN A 109.238.48.13
ns2.gratisdns.dk. 26934 IN A 208.43.238.42
ns3.gratisdns.dk. 26934 IN A 194.0.2.6
ns4.gratisdns.dk. 26934 IN A 87.73.3.3
ns5.gratisdns.dk. 26934 IN A 85.17.221.46

;; Query time: 9 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Mar 15 02:18:35 2012
;; MSG SIZE rcvd: 263

----- binkp.net ends -----

i belive dns record is done from my ina: hostname in nodelists :)


Regards Benny

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

--- Msged/LNX 6.2.0 (Linux/3.1.10-gentoo-r1 (i686))
* Origin: home.junc.org where qico is waiting (2:230/0)

Hello Roy,

On Wednesday March 14 2012 11:23, you wrote to mark lewis:

no... the problem is that it cannot perform domain name lookups
because it uses an old method that is no longer supported by the
newer libs... it works just fine with IP numbers, though...
especially since there is no DNS lookup for them ;)

DNS lookups in the Windows version works just fine.

But I paid for all 3 versions: DOS, Windows AND Linux....


Cheers, Michiel

--- GoldED+/W32-MINGW 1.1.5-b20110320
* Origin: http://www.vlist.org (2:280/5555)

Hello Benny,

On Thursday March 15 2012 02:16, you wrote to Roy Witt:

DNS lookups in the Windows version works just fine.

sure ?, does it use binkp.net now ?

No. fidonet.net is hard coded, not configurable.


Cheers, Michiel

--- GoldED+/W32-MINGW 1.1.5-b20110320
* Origin: http://www.vlist.org (2:280/5555)

Some people stated (unless I am misunderstanding) that they paid
for the 1000 node Linux version, got the key, and the software does
not even execute on Linux.

no... the problem is that it cannot perform domain name lookups
because it uses an old method that is no longer supported by the
newer libs... it works just fine with IP numbers, though...
especially since there is no DNS lookup for them ;)

DNS lookups in the Windows version works just fine.

right... i was speaking of the linux flavor of IREX...

)\/(ark


* Origin: (1:3634/12)

no... the problem is that it cannot perform domain name lookups
because it uses an old method that is no longer supported by the
newer libs... it works just fine with IP numbers, though...
especially since there is no DNS lookup for them ;)

DNS lookups in the Windows version works just fine.

Same for the OS/2 version. :)

--- BBBS/2 v4.01 Flag
* Origin: Omicron Theta * Buffalo, NY * telnet://fpsoft.net:2323 (1:261/20)

15 Mar 12 02:16, Benny Pedersen wrote to Roy Witt:

DNS lookups in the Windows version works just fine.

sure ?, does it use binkp.net now ?

Not sure what binkp.net is...but:

Sample from Irex log:

% 15:31:04 (524) Starting thread 0 (8, b, 406670)
% 15:31:04 (184) Connecting to BinkP site sysgod.org... ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

% 15:31:04 (184) BinkP: OPT ENC-DES-CBC
CRAM-MD5-698d9a4a61805301387f11b09857
% 15:31:04 (184) BinkP: SYS Cyberia TCP/IP
% 15:31:04 (184) BinkP: ZYZ Scott Little
% 15:31:04 (184) BinkP: LOC Sydney
% 15:31:04 (184) BinkP: PHN sysgod.org
% 15:31:04 (184) BinkP: NDL MO,CM,TCP,IFC,TEL,VMP,BND
% 15:31:04 (184) BinkP: TIME Thu, 15 Mar 2012 03:29:38 +1000
% 15:31:04 (184) BinkP: VER Argus/3.210/ binkp/1.0
% 15:31:05 (184) BinkP: 3:712/848@fidonet 3:712/0@fidonet 3:3/0@fidonet
115:6
% 15:31:05 (524) Task 0 is done.
* 15:31:05 (524) Sent 0 files (0K)
% 15:31:05 (536) Starting event.

----- binkp.net begins -----

; <<>> DiG 9.8.1 <<>> f0.n230.z2.binkp.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44629
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 5, ADDITIONAL: 5

;; QUESTION SECTION:
;f0.n230.z2.binkp.net. IN A

;; ANSWER SECTION:
f0.n230.z2.binkp.net. 172767 IN CNAME home.junc.org. home.junc.org. 43167 IN A 2.104.223.10

;; AUTHORITY SECTION:
junc.org. 42091 IN NS ns5.gratisdns.dk. junc.org. 42091 IN NS ns4.gratisdns.dk. junc.org. 42091 IN NS ns3.gratisdns.dk. junc.org. 42091 IN NS ns2.gratisdns.dk. junc.org. 42091 IN NS ns1.gratisdns.dk.

;; ADDITIONAL SECTION:
ns1.gratisdns.dk. 26934 IN A 109.238.48.13 ns2.gratisdns.dk. 26934 IN A 208.43.238.42 ns3.gratisdns.dk. 26934 IN A 194.0.2.6 ns4.gratisdns.dk. 26934 IN A 87.73.3.3 ns5.gratisdns.dk. 26934 IN A 85.17.221.46

;; Query time: 9 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Mar 15 02:18:35 2012
;; MSG SIZE rcvd: 263

----- binkp.net ends -----

i belive dns record is done from my ina: hostname in nodelists :)

Regards Benny

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

--- Msged/LNX 6.2.0 (Linux/3.1.10-gentoo-r1 (i686))
* Origin: home.junc.org where qico is waiting (2:230/0)

R\%/itt


... Only those who will risk going too far can possibly
... find out how far one can go ~ TS Eliot


--- Twit(t) Filter v2.1 (C) 2000-10
* Origin: SATX Alamo Area Net * South * Texas, USA * (1:387/22)

15 Mar 12 11:39, Michiel van der Vlist wrote to Roy Witt:

no... the problem is that it cannot perform domain name lookups
because it uses an old method that is no longer supported by the
newer libs... it works just fine with IP numbers, though...
especially since there is no DNS lookup for them ;)

DNS lookups in the Windows version works just fine.

MvdV> But I paid for all 3 versions: DOS, Windows AND Linux....

I'm glad that I'm not in the same boat with Linux users. There are so many different versions of it, it's no wonder that so many things don't work.,.

At least the work-arounds gives Linux users something to do...

R\%/itt


... Only those who will risk going too far can possibly
... find out how far one can go ~ TS Eliot


--- Twit(t) Filter v2.1 (C) 2000-10
* Origin: SATX Alamo Area Net * South * Texas, USA * (1:387/22)

15 Mar 12 13:30, mark lewis wrote to Roy Witt:

Some people stated (unless I am misunderstanding) that they paid
for the 1000 node Linux version, got the key, and the software does
not even execute on Linux.

no... the problem is that it cannot perform domain name lookups
because it uses an old method that is no longer supported by the
newer libs... it works just fine with IP numbers, though...
especially since there is no DNS lookup for them ;)

DNS lookups in the Windows version works just fine.

right... i was speaking of the linux flavor of IREX...

Since there are 4 OS versions of Rex, please state in your messages which
one you're referring to. Telling a Win OS user that Rex doesn't do
something (while speaking of Linux) leads some people a-stray.

R\%/itt


... Only those who will risk going too far can possibly
... find out how far one can go ~ TS Eliot


--- Twit(t) Filter v2.1 (C) 2000-10
* Origin: SATX Alamo Area Net * South * Texas, USA * (1:387/22)

15 Mar 12 20:25, Robert Wolfe wrote to Roy Witt:

no... the problem is that it cannot perform domain name lookups
because it uses an old method that is no longer supported by the
newer libs... it works just fine with IP numbers, though...
especially since there is no DNS lookup for them ;)

DNS lookups in the Windows version works just fine.

Same for the OS/2 version. :)

Maybe there needs to be a IREX4LIN echo...


R\%/itt


... Only those who will risk going too far can possibly
... find out how far one can go ~ TS Eliot


--- Twit(t) Filter v2.1 (C) 2000-10
* Origin: SATX Alamo Area Net * South * Texas, USA * (1:387/22)

Hello Roy!

16 Mar 2012 04:10, Roy Witt wrote to Benny Pedersen:

% 15:31:04 (524) Starting thread 0 (8, b, 406670)
% 15:31:04 (184) Connecting to BinkP site sysgod.org... ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

dig sysgod.org
dig f848.n712.z3.binkp.net

gives same ip here :)


Regards Benny

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

--- Msged/LNX 6.2.0 (Linux/3.1.10-gentoo-r1 (i686))
* Origin: home.junc.org where qico is waiting (2:230/0)

Hello Roy,

On Friday March 16 2012 04:10, you wrote to Benny Pedersen:

sure ?, does it use binkp.net now ?

Not sure what binkp.net is...but:

binkp.net is the successor of fidonet.net. That latter folded because the caretaker let the domain expire.

And no, Irex does not wok with binkp.net because fidonet.net is hard coded.


Cheers, Michiel

--- GoldED+/W32-MINGW 1.1.5-b20110320
* Origin: http://www.vlist.org (2:280/5555)

17 Mar 12 01:26, Benny Pedersen wrote to Roy Witt:

% 15:31:04 (524) Starting thread 0 (8, b, 406670)
% 15:31:04 (184) Connecting to BinkP site sysgod.org...
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

dig sysgod.org
dig f848.n712.z3.binkp.net

gives same ip here :)

If you ping sysgod.org, ping will lookup the dynamic IP [203.206.223.152]
and use that to send the ping packet bounced off of the dynamic address of sysgod.org: Since Rex is hard-coded to use fnz.fidonet, it cannot use binkp.net, but it can and does use a DNS lookup and will send packets to
the listed IP...


R\%/itt


... Only those who will risk going too far can possibly
... find out how far one can go ~ TS Eliot


--- Twit(t) Filter v2.1 (C) 2000-10
* Origin: Roiz Flying \A/ Service * South Texas * USA * (1:387/22)

17 Mar 12 09:38, Michiel van der Vlist wrote to Roy Witt:

MvdV> Hello Roy,

MvdV> On Friday March 16 2012 04:10, you wrote to Benny Pedersen:

sure ?, does it use binkp.net now ?

Not sure what binkp.net is...but:

MvdV> binkp.net is the successor of fidonet.net. That latter folded
MvdV> because the caretaker let the domain expire.

AFAIK, the hard coded addressing system didn't work very well in
Rex anyway.

MvdV> And no, Irex does not wok with binkp.net because fidonet.net is
MvdV> hard coded.

Just as I thought. TNX for that info.


R\%/itt


... Only those who will risk going too far can possibly
... find out how far one can go ~ TS Eliot


--- Twit(t) Filter v2.1 (C) 2000-10
* Origin: Roiz Flying \A/ Service * South Texas * USA * (1:387/22)

sysgod.org: Since Rex is hard-coded to use fnz.fidonet, it cannot use binkp.net, but it can and does use a DNS lookup and will send packets to the listed IP...

This may not be the best solution but you might be able to hexedit the
binary to change the hostname to "binkp.net"

--- Mystic BBS v1.10 A11 (Linux)
* Origin: Clutch BBS * telnet://clutch.darktech.org (1:250/310)

Hello james!

18 Mar 12 18:58, james coyle wrote to Roy Witt:

sysgod.org: Since Rex is hard-coded to use fnz.fidonet, it cannot
use binkp.net, but it can and does use a DNS lookup and will send
packets to the listed IP...

This may not be the best solution but you might be able to hexedit the binary to change the hostname to "binkp.net"

Or kludge a HOSTS entry so that fidonet resolves however you wish?

.\\ike

--- GoldED/2 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Some people stated (unless I am misunderstanding) that they paid
for the 1000 node Linux version, got the key, and the software does
not even execute on Linux.

no... the problem is that it cannot perform domain name lookups
because it uses an old method that is no longer supported by the
newer libs... it works just fine with IP numbers, though...
especially since there is no DNS lookup for them ;)

DNS lookups in the Windows version works just fine.

right... i was speaking of the linux flavor of IREX...

Since there are 4 OS versions of Rex, please state in your messages
which one you're referring to. Telling a Win OS user that Rex
doesn't do something (while speaking of Linux) leads some people
a-stray.

if they read all of the message or thread, they should be able to tell which was being discussed... the original that i commented to is still above and specifically states linux ;)

but i do see your point...

)\/(ark


* Origin: (1:3634/12)

DNS lookups in the Windows version works just fine.

sure ?, does it use binkp.net now ?

Not sure what binkp.net is...but:

binkp.net is what was quickly put in place to replace fidonet.net when its domain registration expired and the owner couldn't get in to pay up the subscription... loosing fidonet.net would have really hurt fidonet's internet side operations...

)\/(ark


* Origin: (1:3634/12)

MvdV> binkp.net is the successor of fidonet.net. That latter folded
MvdV> because the caretaker let the domain expire.

i thught this was resolved and regained?

MvdV> And no, Irex does not wok with binkp.net because fidonet.net is
MvdV> hard coded.

it shouldn't be too hard to fix... especially since binkd.net is shorter than fidonet.net ;)

)\/(ark


* Origin: (1:3634/12)

sysgod.org: Since Rex is hard-coded to use fnz.fidonet, it cannot
use binkp.net, but it can and does use a DNS lookup and will send
packets to the listed IP...

This may not be the best solution but you might be able to hexedit
the binary to change the hostname to "binkp.net"

seems to me to possibly be a valid fix... however, one must ensure that the string terminator is correct or that the length byte is properly adjusted ;)

)\/(ark


* Origin: (1:3634/12)

sysgod.org: Since Rex is hard-coded to use fnz.fidonet, it cannot
use binkp.net, but it can and does use a DNS lookup and will send
packets to the listed IP...

This may not be the best solution but you might be able to hexedit the binary to change the hostname to "binkp.net"

Or kludge a HOSTS entry so that fidonet resolves however you wish?

can you do something similar to CNAME in the HOSTS file? it is a DNS lookup we are trying to handle and the DNS domain that was used no longer exists if i've been keeping up properly...

granted, with less than 9000 nodes in fidonet now, it isn't that hard to do but
i don't know that i want to manage a HOSTS file with that many entries ;)

)\/(ark


* Origin: (1:3634/12)

18 Mar 12 18:58, james coyle wrote to Roy Witt:

sysgod.org: Since Rex is hard-coded to use fnz.fidonet, it cannot
use binkp.net, but it can and does use a DNS lookup and will send
packets to the listed IP...

This may not be the best solution but you might be able to hexedit
the binary to change the hostname to "binkp.net"

I'd rather not use binkp.net at all since each IP node has either a DNS
look up alias or if a static IP, that IP can be found in the nodelist.

AFAIK, that binkp.net is for you guys that use Linux.


R\%/itt


... Only those who will risk going too far can possibly
... find out how far one can go ~ TS Eliot


--- Twit(t) Filter v2.1 (C) 2000-10
* Origin: Roiz Flying \A/ Service * South Texas * USA * (1:387/22)

I'd rather not use binkp.net at all since each IP node has either a
DNS look up alias or if a static IP, that IP can be found in the
nodelist.

AFAIK, that binkp.net is for you guys that use Linux.

actually, binkp.net replaces the old fidonet.net in that it provides the standard conversion between fidonet addresses and their internet equivelent... the only "rough" part being that the second level domain name has changed from "fidonet" to "binkp"... other than that, everything else is exactly the same...

but it should also be noted, as you demonstrated IIRC, that fidonet.net address
conversion is still working because it appears that the DNS domain server operators for that domain still have control over them even though the domain appears to have changed hands... BUT when that stops working, then some folk will /HAVE/ to change their software...

)\/(ark


* Origin: (1:3634/12)

Hello Roy,

On Sunday March 18 2012 05:47, you wrote to me:

MvdV>> binkp.net is the successor of fidonet.net. That latter folded
MvdV>> because the caretaker let the domain expire.

AFAIK, the hard coded addressing system didn't work very well in
Rex anyway.

Indeed, it didn't work all that well and its usefulness was limited. Frankly I found it more a hindrance than a help. I would have disabled it if that was possible.


Cheers, Michiel

--- GoldED+/W32-MINGW 1.1.5-b20110320
* Origin: http://www.vlist.org (2:280/5555)

Hello mark,

On Monday March 19 2012 14:34, you wrote to Roy Witt:

Not sure what binkp.net is...but:

binkp.net is what was quickly put in place to replace fidonet.net when
its domain registration expired and the owner couldn't get in to pay
up the subscription... loosing fidonet.net would have really hurt fidonet's internet side operations...

One of the reasons I never embraced f5555.n280.z2.fidonet.net is that it depends on one person. Fidonet is not a legal entity, so the domain must be registered by a private person. If that person dies, looses interest or leaves Fidonet with slamming doors, there is a problem.

Shifting to binkp.net is no good for those with legacy software that is not configurable. Plus that the basic problem - dependency on one person - remains.

To my surprise I find that f5555.n280.z2.binkp.net exists. I never asked for that, I can only assume someone scanned the nodelist and derived a zone file for binkp.net from it. Makes me wonder why. The added value is zero as all the information is already in the nodelist.


Cheers, Michiel

--- GoldED+/W32-MINGW 1.1.5-b20110320
* Origin: http://www.vlist.org (2:280/5555)

Hello mark,

On Monday March 19 2012 14:37, you wrote to Roy Witt:

MvdV>> binkp.net is the successor of fidonet.net. That latter folded
MvdV>> because the caretaker let the domain expire.

i thught this was resolved and regained?

That happend a couple of years back. I don't know about the present status.

MvdV>> And no, Irex does not work with binkp.net because fidonet.net is
MvdV>> hard coded.

it shouldn't be too hard to fix... especially since binkd.net is
shorter than fidonet.net ;)

Probably. But I have better things to do than kicking dead horses...


Cheers, Michiel

--- GoldED+/W32-MINGW 1.1.5-b20110320
* Origin: http://www.vlist.org (2:280/5555)

Not sure what binkp.net is...but:

binkp.net is what was quickly put in place to replace fidonet.net when
its domain registration expired and the owner couldn't get in to pay
up the subscription... loosing fidonet.net would have really hurt fidonet's internet side operations...

MvdV> One of the reasons I never embraced f5555.n280.z2.fidonet.net is
MvdV> that it depends on one person. Fidonet is not a legal entity, so
MvdV> the domain must be registered by a private person. If that person
MvdV> dies, looses interest or leaves Fidonet with slamming doors,
MvdV> there is a problem.

or if they loose the access credentials as happened with fidonet.net...

MvdV> Shifting to binkp.net is no good for those with legacy software
MvdV> that is not configurable. Plus that the basic problem -
MvdV> dependency on one person - remains.

existing legacy software can be patched... we know this from makenl and bluewave ;)

MvdV> To my surprise I find that f5555.n280.z2.binkp.net exists. I
MvdV> never asked for that, I can only assume someone scanned the
MvdV> nodelist and derived a zone file for binkp.net from it. Makes me
MvdV> wonder why.

why? to be able to continue providing the service...

MvdV> The added value is zero as all the information is already in the
MvdV> nodelist.

really? the whole idea was to not have to list domains in the nodelist with all
the problems that might have come with them... and the problem did come and still remain but that's another story... in any case, once you know the zone, net, node and point numbers, then looking up that system's ip information is a simple domain lookup away...

there is a "manager" for each zone's dns zone and NCs are or can be the managers for their nets... this way each section is easily maintained and kept up to date like the nodelist... one can even make use of the dns SRV (or SVR?) records and denote certain ports for contact...

)\/(ark


* Origin: (1:3634/12)

Hello mark,

On Wednesday March 21 2012 13:18, you wrote to me:

Not sure what binkp.net is...but:

MvdV>> Shifting to binkp.net is no good for those with legacy software
MvdV>> that is not configurable. Plus that the basic problem -
MvdV>> dependency on one person - remains.

existing legacy software can be patched... we know this from makenl
and bluewave ;)

Unpractical and messy.

MvdV>> To my surprise I find that f5555.n280.z2.binkp.net exists. I
MvdV>> never asked for that, I can only assume someone scanned the
MvdV>> nodelist and derived a zone file for binkp.net from it. Makes
MvdV>> me wonder why.

why? to be able to continue providing the service...

What service? Who does it serve?

MvdV>> The added value is zero as all the information is already in
MvdV>> the nodelist.

really?

Yes of course. f5555.n280.z2.binkp.net is a CNAME entry for fido.vlist.eu. The only source that information could have come from is the nodelist. Because I never had any contact with the keeper of binkp.net or his delegates and i am 100% sure that my NC and RC didn't either.

the whole idea was to not have to list domains in the nodelist

Is that so?

with all the problems that might have come with them... and the
problem did come and still remain but that's another story... in any
case, once you know the zone, net, node and point numbers, then
looking up that system's ip information is a simple domain lookup
away...

Again: what is the added value of extracting the host name fido.vlist.eu from the nodelist - the primary source of information - and use that for the DNS lookup instead of composing the f.n.z.binkp.net hostname from the fidonet address, getting the CNAME record that points to the same hostname as the one in the nodelist and do a DNS lookup for that?

What is the added value of the extra step?

there is a "manager" for each zone's dns zone and NCs are or can be
the managers for their nets...

There is no such "manager" for R28.

this way each section is easily maintained and kept up to date like
the nodelist...

But what is the added value of the information is already in the nodelist?

one can even make use of the dns SRV (or SVR?) records and denote
certain ports for contact...

The nodelist provides for providing port info as well.


Cheers, Michiel

--- GoldED+/W32-MINGW 1.1.5-b20110320
* Origin: http://www.vlist.org (2:280/5555)

Hello mark.

19 Mar 12 14:37, you wrote to Roy Witt:

it shouldn't be too hard to fix... especially since binkd.net is
shorter than fidonet.net ;)

one can always resort to binaries editing the irex elf/exe what ever, but remember to backup the originals

sed -e s/fidonet.org/binkp.net<spacepads so it match lenght of fidonet.org>/ irexd

who will make a patch for any os ?


Benny

--- GoldED+/LNX 1.1.5-b20120229
* Origin: me at junc dot org (2:230/0)

20 Mar 12 21:53, mark lewis wrote to Roy Witt:

I'd rather not use binkp.net at all since each IP node has either a
DNS look up alias or if a static IP, that IP can be found in the
nodelist.

AFAIK, that binkp.net is for you guys that use Linux.

actually, binkp.net replaces the old fidonet.net in that it provides
the standard conversion between fidonet addresses and their internet equivelent... the only "rough" part being that the second level
domain name has changed from "fidonet" to "binkp"... other than that, everything else is exactly the same...

It didn't work in Irex when it was 'fidonet'...Since that is hardcoded
into Irex, it can't be changed. Unless you are inclined to dig into the
code and re-code it to use 'binkp'... Who's to say what repercussions that would have on the rest of the program.

but it should also be noted, as you demonstrated IIRC, that
fidonet.net address conversion is still working because it appears
that the DNS domain server operators for that domain still have
control over them even though the domain appears to have changed
hands... BUT when that stops working, then some folk will /HAVE/ to
change their software...

Or someone will have coded a workaround.


R\%/itt


... Only those who will risk going too far can possibly
... find out how far one can go ~ TS Eliot


--- Twit(t) Filter v2.1 (C) 2000-10
* Origin: Roiz Flying \A/ Service * South Texas * USA * (1:387/22)

21 Mar 12 10:30, Michiel van der Vlist wrote to Roy Witt:

MvdV>>> binkp.net is the successor of fidonet.net. That latter folded
MvdV>>> because the caretaker let the domain expire.

AFAIK, the hard coded addressing system didn't work very well in
Rex anyway.

MvdV> Indeed, it didn't work all that well and its usefulness was
MvdV> limited. Frankly I found it more a hindrance than a help.

I find it a hinderance everytime that a new node is entered and Rex wants
to use the nodelisting to enter that node's fnz.fidonet address.

MvdV> I would have disabled it if that was possible.

I would have too. These days I just have to remember to enter addressing manually.


R\%/itt


... Only those who will risk going too far can possibly
... find out how far one can go ~ TS Eliot


--- Twit(t) Filter v2.1 (C) 2000-10
* Origin: Roiz Flying \A/ Service * South Texas * USA * (1:387/22)

it shouldn't be too hard to fix... especially since binkd.net is
shorter than fidonet.net ;)

one can always resort to binaries editing the irex elf/exe what
ever, but remember to backup the originals

exactly what i was referring to...

sed -e s/fidonet.org/binkp.net<spacepads so it match lenght of fidonet.org>/ irexd

why space padding? the strings are null terminated... no padding needed...

who will make a patch for any os ?

i dunno...

)\/(ark


* Origin: (1:3634/12)

Hello mark!

22 Mar 2012 15:04, mark lewis wrote to Benny Pedersen:

why space padding? the strings are null terminated... no padding needed...

how can i know ?


Regards Benny

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

--- Msged/LNX 6.2.0 (Linux/3.1.10-gentoo-r1 (i686))
* Origin: home.junc.org where qico is waiting (2:230/0)

Hello Roy,

On Thursday March 22 2012 05:25, you wrote to me:

I find it a hinderance everytime that a new node is entered and Rex
wants to use the nodelisting to enter that node's fnz.fidonet address.

Same here.

MvdV>> I would have disabled it if that was possible.

I would have too. These days I just have to remember to enter
addressing manually.

As I wrote, I do not often add new nodes to the node mangare, so it is not that
big a deal. The other bugs are more annoying.


Cheers, Michiel

--- GoldED+/W32-MINGW 1.1.5-b20110320
* Origin: http://www.vlist.org (2:280/5555)

why space padding? the strings are null terminated... no padding needed...

how can i know ?

are you not a "hacker" in the old school sense of the phrase? simple look at the existing and you will see one of two basic formats and possibly one that incorporates both... the most obvious format is the null terminated which doesn't care about string length other than seeking to the first nul character in the field... that C style... pascal style carries a string length byte at the beginning of the string chatacter array ;)

)\ /(ark


* Origin: (1:3634/12)

Hello mark!

19 Mar 12 14:44, mark lewis wrote to Mike Tripp:

Or kludge a HOSTS entry so that fidonet resolves however you
wish?

can you do something similar to CNAME in the HOSTS file? it is a DNS lookup we are trying to handle and the DNS domain that was used no
longer exists if i've been keeping up properly...

granted, with less than 9000 nodes in fidonet now, it isn't that hard
to do but i don't know that i want to manage a HOSTS file with that
many entries ;)

I was just suggesting a single entry that would remap fidonet.net to binkp.net's IP as opposed to hex-editing the hard-coded string. Sorry I can't test to sanity-check...don't have any downlinks that require Irex's features currently, and didn't use this particular one when I did. I would expect resolution to be handled remotely, if you can just reach the right resolver.<g>

.\\ike

--- GoldED/2 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)

Hello mark!

19 Mar 12 14:44, mark lewis wrote to Mike Tripp:

Or kludge a HOSTS entry so that fidonet resolves however you
wish?

can you do something similar to CNAME in the HOSTS file? it is a DNS
lookup we are trying to handle and the DNS domain that was used no
longer exists if i've been keeping up properly...

granted, with less than 9000 nodes in fidonet now, it isn't that hard
to do but i don't know that i want to manage a HOSTS file with that
many entries ;)

I was just suggesting a single entry that would remap fidonet.net to binkp.net's IP as opposed to hex-editing the hard-coded string. Sorry I

Have you tried editing Window's HOSTS file? Or whatever equivalent
other OS's use?

can't test to sanity-check...don't have any downlinks that require
Irex's features currently, and didn't use this particular one when I
did. I would expect resolution to be handled remotely, if you can just
reach the right resolver.<g>

.\\ike

--- GoldED/2 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k
(1:382/61)

--- GEcho/32 & IM 2.50
* Origin: http://www.fidonet.ca (1:140/12)

Hello mark!

Tuesday March 20 2012 21:53, mark lewis wrote to Roy Witt:

but it should also be noted, as you demonstrated IIRC, that
fidonet.net address conversion is still working because it appears
that the DNS domain server operators for that domain still have
control over them even though the domain appears to have changed
hands... BUT when that stops working, then some folk will /HAVE/ to
change their software...

fidonet.net resolves to 176.9.1.244, but none of the f.n.z.fidonet.net addresses I tried come up with anything other than NXDOMAIN, at least with the 2 ISPs I tested with.

Andrew

---
* Origin: Bits & Bytes BBS * V.Everything! * 860/535-4284 (1:320/119)

Hello Bob!

30 Mar 12 08:33, Bob Seaborn wrote to Mike Tripp:

I was just suggesting a single entry that would remap fidonet.net
to binkp.net's IP as opposed to hex-editing the hard-coded string.
Sorry I

Have you tried editing Window's HOSTS file? Or whatever
equivalent other OS's use?

That was =my= suggestion, but I don't run Irex currently and didn't futz with fnz when I did. Seems you could just cheat fidonet.net to binkp.net's IP locally if they're providing exactly the same service, though I wouldn't find the fly in the ointment without actual testing.

.\\ike

--- GoldED/2 2.50+
* Origin: -=( The TechnoDrome )=- Austin,TX 512-327-8598 33.6k (1:382/61)