Hey Kai!

Sep 04 18:31 06, Kai Richter wrote to Maurice Kinal:

 KR> I don't know internet services well. How do husky and ftp fit 
 KR> together?

Actually pretty good but I have to script the BSO part out.  The *.clo or
.hlo or whatever is meaningless to a scripted ftp client but is still
usable if I cat the outbound(s) listed in that file to the ftp client which
then transfers it to the server.

 KR> Does it work with the filebox feature of hpt?

Not without scripting.  I suppose it could be hacked to be more ftp-ish but
that is more work then it's worth.  Scripting works excellent and costs
little in work.

For instance on the point I just use bash and the BSO like;

---------------------------------------------------------------------
if [ -e $HOME/coffin-point/out/008c000d.clo ]; then
    outfile=`cat $HOME/coffin-point/out/008c000d.clo | cut -f2 -d "^"`
    rm $HOME/coffin-point/out/008c000d.clo
    lftp -u ftpusername,supersecretpassword ftp-server-ip-address \
        -e "cd fido/in.sec;put -E $outfile;exit"
fi
---------------------------------------------------------------------

There is more to it then just the above but that is the part unique to
sending to the bossnode.  The 'if' checks if hpt packed anything and if it
did then the outfile is just the raw pkt to be sent with the normal leading
^ character cut out since lftp (the ftp client) takes care of deleting the
pkt after it confirms the the server recieved it.  On the server there is a
job running in the background that runs htp on there if it sees any pkt's
from it's points and then processes it for the hub in the normal fashion so
that it can be transferred to the hub via binkd, usually as hold since
there is no way for the server to tell if the hub is running and binkd
wastes too many resources trying if for whatever reason the hub is down. 
If the hub was also using normal tcpip then the server here could easily
tell if the hub is up and listening but I guess the hub doesn't care about
my resources so if I wish to robotize binkd for crash I will need a better
way to do it.  I haven't figured out a way with that particular hub since
he insists on hiding behind a service that doesn't tell.  No big deal as it
isn't mission critical internetworkingly speaking.

Also 'sed' could be used to strip the '^' character from the outfile but
'cut' works good as shown above.  Lots of good ways in Linux eh?

 KR> User login into the ftp user/homedir and then transfer per 
 KR> scriptfile?

Yes.  I use lftp but ncftp works great too.  openssh's scp or sftp could
also work and might be best over the internet depending on the
server/client relationship.  Since the point and the server have a trusted
LAN connection (not internetted) then ftp is GREAT!!!  :-)

 KR> Can your way handle a single config for the user passwords and 
 KR> outbounds?

Yes.  Also on *nix systems secure copy could be used so it can even be
encrypted if one is really paranoid.

 KR> Can you do crashmail to nodelist IP-nodes without prior contact to 
 KR> that nodes?

Nope.  Too unreliable on the internet methinks.  I suppose you could but I
don't advise it.  Dialup would work better for that since the connection is
direct and would be virtually impossible to spoof a data dialed number.  I
guess it depends on how reliable and secure one wishes an internetted node
to be.  Myself I trust nothing to work properly on the internet unless it
is a proven internetted connection ... such as ftp or ssh or simular.  Also
those typoe of connections allow for better robotization if the
participants are doing things tcpip-ish rather then faked out dialup
methods on a tcpip network.

I've seen too many weird things going on.  ;-)

Life is good,
Maurice

--- Msged/LNX 6.2.0