Hi All!

I am experimenting with othernets, and have a strange thing (misconfiguration on my side?)

I have 2 addresses 1 FIDO, 1 othernet.
I want binkd to use binkp.net for unknown fido addresses.
For the othernet only the nodes defined in the config should be used.

My config looks like this:
root-domain not configured.
fido domain has root-domain binkp.net
othernet has no root-domain

domain fidonet /home/fido/outbound 2 binkp.net
domain fido alias-for fidonet
domain fidonet.org alias-for fidonet
domain othernet /home/fido/outbound 2

address 2:310/31@fidonet
address 666:1/2@othernet

#root-domain binkp.net
#defnode *

If defnode * is commented out it works, but does not dial unknown fido nodes that have an entry in binkp dns.
If I enable defnode * it adds a second othernet AKA to all the nodes it tries to dial:

-h 2:310/31.1@fidonet
-d 2:12/340@fidonet
-h 2:310/31.1@othernet <-- should not be here
-d 2:12/34@othernet <-- should not be here

Is that a config error on my side?

I thought if root-domain is only configured for one domain, it should only be used in that domain.
To me it looks like it also does 2. DNS lookups for the nodenumber, and adds the same node also with domain @othernet.

Is there a way to configure binkd to a) only add @othernet AKAs to nodes that are configured for @ithernet
b) lookup unknown fido nodes in binkp.net and dial them (not for othernet)

I use HPT as a tosser and have used the domainless tosser config from the FAQ.

CU, Ricsi

--- GoldED+/LNX
* Origin: fido.ricsi.priv.at (2:310/31)

Hi All

Sorry for my repost, but does anybody has any idea?
If I enable defnode * while having an othernet active, I get polls to the fido nodenumbers with domain othernet as well.
I have only added root-domain to fido, so binkd should not try to look up othernet nodes via DNS.

Any ideas to solve this are welcome.
I will report back here after I tried the suggested solutions ;)

CU, Ricsi

27 Jan 2016 13:19, from Richard Menedetter -> All:

Hi All!

I am experimenting with othernets, and have a strange thing (misconfiguration on my side?)

I have 2 addresses 1 FIDO, 1 othernet.
I want binkd to use binkp.net for unknown fido addresses.
For the othernet only the nodes defined in the config should be used.

My config looks like this:
root-domain not configured.
fido domain has root-domain binkp.net
othernet has no root-domain

domain fidonet /home/fido/outbound 2 binkp.net
domain fido alias-for fidonet
domain fidonet.org alias-for fidonet
domain othernet /home/fido/outbound 2

address 2:310/31@fidonet
address 666:1/2@othernet

#root-domain binkp.net
#defnode *

If defnode * is commented out it works, but does not dial unknown fido nodes that have an entry in binkp dns. If I enable defnode * it adds a second othernet AKA to all the nodes it tries to dial:

-h 2:310/31.1@fidonet
-d 2:12/340@fidonet
-h 2:310/31.1@othernet <-- should not be here
-d 2:12/34@othernet <-- should not be here

Is that a config error on my side?

I thought if root-domain is only configured for one domain, it should
only be used in that domain. To me it looks like it also does 2. DNS lookups for the nodenumber, and adds the same node also with domain @othernet.

Is there a way to configure binkd to a) only add @othernet AKAs to
nodes that are configured for @ithernet b) lookup unknown fido nodes
in binkp.net and dial them (not for othernet)

I use HPT as a tosser and have used the domainless tosser config from
the FAQ.

CU, Ricsi

CU, Ricsi

--- GoldED+/LNX
* Origin: fido.ricsi.priv.at (2:310/31)

Hallo Richard!

Donnerstag, den 28. Januar 2016 22:57, Richard Menedetter schrieb an Richard Menedetter:

For the othernet only the nodes defined in the config should be used.

My config looks like this:
root-domain not configured.
fido domain has root-domain binkp.net
othernet has no root-domain

It has to have a othernet domain, mostly this othernet domain is virtually.


-+- Anfang binkd.cfg -+-
domain fidonet E:\\DBAHN\\MAILER\\OUTBOUND 2
domain fido alias-for fidonet
domain fidonet.org alias-for fidonet
domain fidonet.net alias-for fidonet
[...]
domain amiganet E:\\DBAHN\\MAILER\\OUTBOUND 2
[...]
address 2:240/5832@fidonet
address 2:240/5833@fidonet
address 2:240/5834@fidonet
address 2:24/0@fidonet
#
address 39:17/0@amiganet
address 39:17/1@amiganet
address 39:17/170@amiganet
address 39:17/5832@amiganet
address 39:17/5833@amiganet
address 39:17/5834@amiganet
[...]
node 2:310/31@fidonet fido.ricsi.priv.at PASSWORD i

#
# Default node flags. Binkd will call unlisted node if "defnode" defined.
#
#defnode -nr *
#
-+- Ende binkd.cfg -+-

-h 2:310/31.1@fidonet
-d 2:12/340@fidonet
-h 2:310/31.1@othernet <-- should not be here
-d 2:12/34@othernet <-- should not be here
Is that a config error on my side?

Yes. you have to define the nodestatements with domain and disable defnode.

CU, Ricsi

Bye/2 Torsten

... MAILBOX02: Up 05d 23h 55m (BTUp2V1.5)
--- GoldED+/EMX 1.1.4.7
* Origin: DatenBahn BBS (2:240/5832)

Hi Torsten!

29 Jan 2016 00:09, from Torsten Bamberg -> Richard Menedetter:

My config looks like this:
root-domain not configured.
fido domain has root-domain binkp.net
othernet has no root-domain

It has to have a othernet domain, mostly this othernet domain is virtually.

I think we are talking "around" each other.
With "root-domain" I mean the DNS Domain that is used to automatically look up a node if it is not defined in the config.

What I want is that "fidonet" uses the binkp.net domain.
domain fidonet /home/fido/outbound 2 binkp.net
domain othernet /home/fido/outbound 2 <- missing last argument root-domain

When I then insert a
defnode *

I would assume that it tries to look up unconfigured nodes (not in binkd.cfg) for fidonet in the fxx.nxx.zxx.binkd.net domain.
Strangely it also does it for @othernet
I have no clue what DNS domain it is using, as I have configured none!

What I am looking for is a
defnode *
only for fidonet, and not for any other domain.
How to configure that in binkd?

-h 2:310/31.1@othernet <-- should not be here
-d 2:12/34@othernet <-- should not be here
Is that a config error on my side?

Yes. you have to define the nodestatements with domain and disable defnode.

But the whole purpose of my mail was NOT to comment out defnode *.
If I do it is working, but I do not have defnode behaviour for fidonet FTN domain.

That is a very useful feature, and I want to use it for fidonet.

The question (bug??) is that it seems to make lookups also for othernet FTN domains that do not even have a DNS root-domain configured.
I should tcpdump what DNS requests binkd sends.
Will do that later, when I am at home (currently at work)

CU, Ricsi

--- GoldED+/LNX
* Origin: fido.ricsi.priv.at (2:310/31)

29 Jan 16 09:25, you wrote to Torsten Bamberg:

My config looks like this:
root-domain not configured.
fido domain has root-domain binkp.net
othernet has no root-domain

It has to have a othernet domain, mostly this othernet domain is
virtually.

I think we are talking "around" each other.
With "root-domain" I mean the DNS Domain that is used to automatically

look

up a node if it is not defined in the config.

i think that torsten is saying that you still must define a domain for that othernet...

What I want is that "fidonet" uses the binkp.net domain.
domain fidonet /home/fido/outbound 2 binkp.net
domain othernet /home/fido/outbound 2 <- missing last argument root-domain

add an argument for that last line... othernet.invalid should work...

[trim]

What I am looking for is a
defnode *
only for fidonet, and not for any other domain.
How to configure that in binkd?

you cannot... not in one config file... it is called "default node" for a reason...

you could, however, split your config into two... one for each FTN... then run two instances of binkd, on different ports, and keep them separate... then you can have defnode for fidonet only and whatever for your othernet...

)\/(ark

... Confucius Say: To make egg roll, push it.
---
* Origin: (1:3634/12.73)