On (10 Mar 06) mark lewis wrote to Frank Vest...

Hello mark,


 DC> % 02:36:25  Connecting to BinkP site cstation.synchro.net... %
 DC> 02:36:31  BinkP: SYS Collin County Station
 DC> % 02:36:31  BinkP: ZYZ Frank Vest
 DC> % 02:36:31  BinkP: LOC McKinney, Tx.
 DC> % 02:36:31  BinkP: NDL IBN,CM
 DC> % 02:36:31  BinkP: TIME 2006/03/02 04:37:01 -6:00
 DC> % 02:36:31  BinkP: VER Internet Rex 2.29 Win32 (binkp/1.1)
 DC> % 02:36:31 BinkP: 1:124/6308.0{at}fidonet 1:124/0.0{at}fidonet
 DC> 169:1/124.0{at}fidonet 169:3020/117.0{at}fidonet 777:777/31.0{at}fidonet
 ml> there might be part of the problem... zones 169 and 777 are not
 ml> {at}fidonet domains... i dunno what FTN domain they are but they are
 ml> definitely not fidonet... looks like frank has a bit of configuration
 ml> to work on...

 FV> Why? Frank is a part of those other FTNs
 ml> of course... they wouldn't be there if he wasn't, right? ;)

True. :)

 FV> and they are presented as they should be.
 ml> yes and no... they are properly listed for 3D/4D but not for 5D...

Where do I list them for 5D?

 FV> The {at}fidonet is not relevant unless my mailer tries to look up the
 FV> domain via DNS.
 ml> again, yes and no... those zones are not part of the FTN fidonet
 ml> domain... they are part of other FTN domains and i don't know what
 ml> their FTN names are but they are definitely not fidonet...

battlenet and x-bit

 FV> The fact that the {at}fidonet is there should not, and does not,
 FV> affect anything. Besides, things are now working properly with the
 FV> {at}fidonet. Go figger.
 ml> they don't effect anything _on_your_system_ but that is most likely
 ml> because you aren't running anything, other than the mailer, that is
 ml> truely and properly 5D aware...

Ok. Maybe.

 ml> as for working properly and not affecting anything, what say that i
 ml> join one or both of those networks... lets say that i configure my
 ml> setup with properly defined FTN domains for those zones? lets also say
 ml> that i have traffic for you in one of those networks... so my system
 ml> tries to contact yours and it sees those zones listed in the fidonet
 ml> domain... guess what's going to happen? the zones may match but the
 ml> domains don't and we won't be able to exchange traffic based on those
 ml> zone numbers like we could if they were carrying the proper domains
 ml> attached to them...

The Node I was having problems with suddenly, for no apparent reason,
became able to connect with me. After your reply, I went into
irexcfgw.exe and checked. In the binkp config for zone 777 and 169
nodes, I don't have fidonet listed as the domain. In the domain setup,
I added 777 as xbit and 169 as battlenet. The node I had the problem
with could still connect with me, but my Fidonet Hub could not. I
changed it back and my Hub can connect again, as well as the Node I
was having the trouble with. Like I said, Go figger. 

 ml> does that make sense, now?

Very little about this "here today, gone tomorrow" hiccup makes sense.

Either way, things seem to be working now.

Regards,
Frank


And remember:
"If you don't read the newspaper, you are uninformed;
 ....if you do read the newspaper, you are misinformed!"

Disclaimer:
 I know you think you understood what I wrote, But I'm not sure that
what you think you read is what I meant.
 The views expressed here are not necessarily the views of those who
disagree with me.

--- PPoint 3.01