I am having major problems getting Binkit to call out nodes who are not part of fidonet and they use mystic systems.

Mystic requires the domain to be presented... and I've done everything I can think of to get it to work. (not passwords removed)

Also my fido connection with Mystic does not like encryption.

I'm having no problems (other than my files going in the temp directory) with my main fido feed.

I am having problems hitting the filegate at 1:261/38 they use a nonstandard port.

All in all Bink-it appears to be nuclear with the exception it does not want to deliver my mail :-(

-+-

[1:261/38@fidonet]
Host=filegate.net
Port=24555
Password=--------
Poll=Yes
AllowUnencrypted

====


[21:1/100@fsxnet]
Host=ipv4.agency.bbs.geek.nz
port=24556
Password=--------
Poll=Yes
AllowUnencrypted
SourceAddress=21:1/48@fsxnet

[44:100/0@dorenet]
Host=dreamland.darktech.org
Password=--------
Poll=Yes
AllowUnencrypted
SourceAddress=44:502/0@dorenet

---
þ Synchronet þ In

Hawke wrote to All <=-

I am having major problems getting Binkit to call out nodes who are not part of fidonet and they use mystic systems.

Mystic requires the domain to be presented... and I've done everything
I can think of to get it to work. (not passwords removed)

Yes, Mystic matches the entire address, including the domain. It's fully 5D aware.

Also my fido connection with Mystic does not like encryption.

You talking about CRAM-MD5 or something else?

I'm having no problems (other than my files going in the temp
directory) with my main fido feed.

I am having problems hitting the filegate at 1:261/38 they use a nonstandard port.

All in all Bink-it appears to be nuclear with the exception it does not want to deliver my mail :-(

I use BinkD, which has worked with every peer I've tried (and more than half, including one that I run here, run Mystic). BinkD is also fully IPv6 capable, and at least 2 of my links are already on IPv6, with more to follow when Mystic gains IPv6 capability in the near future.

[21:1/100@fsxnet]
Host=ipv4.agency.bbs.geek.nz
port=24556
Password=--------
Poll=Yes
AllowUnencrypted
SourceAddress=21:1/48@fsxnet

^^

Are you sure this isn't a typo? Host address start at 21:1/101 in fsxnet. I suspect your address should be 21:1/148.


... Don't argue with he who buys ink by the gallon.
--- MultiMail/Win32 v0.49
þ Synch

Re: Re: Binkit call out problems
By: Vk3jed to Hawke on Mon Jul 18 2016 11:01 pm

Hawke wrote to All <=-

Are you sure this isn't a typo? Host address start at 21:1/101 in fsxnet. I suspect your address should be 21:1/148.

The 1 is there in the actual configuration... could you post one of your nodes sans password?

The one node that connects I get...

7/18 04:47:06p No secure inbound configured in sbbsecho! Leaving secure 7/18 04:47:06p No secure inbound configured in sbbsecho! Leaving secure file
7/18 04:47:06p No secure inbound configured in sbbsecho! Leaving secure 7/18 04:47:06p Attempting poll for node 1:261/38@fidonet

I promise you I definately have a secure outbound defined.

Allen
---
þ S

Alprunty wrote to Vk3jed <=-

Are you sure this isn't a typo? Host address start at 21:1/101 in fsxnet. I suspect your address should be 21:1/148.

The 1 is there in the actual configuration... could you post one of
your nodes sans password?

OK, not sure what that's going to achieve. I use BinkD, not binkit, different configuration. But anyway, this is how it looks in binkd.conf. I've never used binkit, so can't comment on the specifics there.

# First specified domain sets as default domain for the 3D/4D addresses.
#
domain fidonet /sbbs/binkd/outbound 3
domain fsxnet /sbbs/binkd/outbound 3
domain sportnet /sbbs/binkd/outbound 3
domain linuxnet /sbbs/binkd/outbound 3
domain wwivftn /sbbs/binkd/outbound 3
domain vkradio /sbbs/binkd/outbound 3

# from here, I'll just use the FSX specific parts.


# Your addresses, 5D or 4D or 3D:
# address <addr1> ...
# If first address specified as 3D/4D then domain for it sets from domain
# defined in the first "domain" token. If second and more addresses specified
# as 3D/4D then domain sets from first address.
#

address 3:633/410@fidonet
address 21:1/109@fsxnet

# and finally, the host to poll (yess, I have changed the password!)

node 21:1/100 ipv4.agency.bbs.geek.nz:24556 PASSWORD i

The one node that connects I get...

7/18 04:47:06p No secure inbound configured in sbbsecho! Leaving secure 7/18 04:47:06p No secure inbound configured in sbbsecho!
Leaving secure file
7/18 04:47:06p No secure inbound configured in sbbsecho! Leaving secure 7/18 04:47:06p Attempting poll for node 1:261/38@fidonet

I promise you I definately have a secure outbound defined.

Don't you mean inbound?

Anyway, not sure what that issue is, I've never seen that error, though I'm still using sbbsecho 2.x here. I haven't tried the nightly builds yet.

Also, with regards to fsxnet, have you checked with Paul as to the error he's getting on his end?


... Features should be discovered, not documented.
--- MultiMail/Win32 v0.49
* Origin: Freeway BBS - freeway.apana.org.au (3:633/410)
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net