[FADCA] Re: Rookie Mistake

[Chuck Hast]

On Thu, 30 Dec 2004 09:52:26 -0500, Charles S Schuman
<k4gbb at earthlink.net> wrote:
> As that old beer commercial says "Beware of the Penguin!"
> 
> I used your ax25.conf file as an example and several permutations of the
>   example in the HOW TO doc. The simple thing would connect and then
> disconnect.
> 
We ought to take this on list as there are several others out there who are all
going the same direction, so I have also copied it to FADCA.

Yes, that is the first thing that you always have to do is make sure
that the permissions
are set up right. Remember, those permissions are what keep Linux much freer of
viruses and hacking, they are a pain but they are really worth it
because it just
makes life misserable for the average script kiddie.


> The exe file would run from the command line w/o any problem. After many
> days of this I checked the permissions on the exe file and found that I
> didn't have a permission. I fixed that minor detail and it now works.
> 

Better that then a hack because it was open to all...


> I keep running into missing files. One was the /var/ax25/fpac/loggins.
> The docs say that the needed files will be created upon install, but
> some come up missing.
yes all you have to do is go into the /var/ax25/fpac/ and do the following
command
touch loggins
and it will create the loggins file. That should have been in the setup script
of the fpac stuff but looks like it got missed or it did no work for
some reason.
Anytime you find that a file has not been created all you need to do is use
the touch command to create the file, make sure it has the proper permissions
so that in this case fpac can log data to it and you are off and running.
Here is how it is set up on my machine.
-rw-rw-rw-    1 root     root          768 Dec 30 00:33 loggedin
Remember you can always go in and poke around using the radio loggin with
ssh. i.e.
ssh radio at 24.129.134.206
password radio


> 
> I noticed that you have numbered your AXports rather than naming them.
> I didn't catch that till I got to the FPAC node and tried to make a
> connection using a port #. I guess I'll have to go back and redo the
> AX25 setup.

Yea I fell into the same trap the AX25 How to does have you give the
ports names, but FPAC works better if they are numbers, and also that
is what we are used to with both FPAC DOS and ROSE, so just carried
it on through, I had to go in and change the files too, but once done life
is good.


> 
> One of the things that slows me down is trying to catch errors on
> startup. I have been using the ol Scroll lock trick, but it is somewhat
> imprecise and I have to write out the errors on paper. I am fairly sure
> there is a log file, but haven't figured out how to access it.
> 
> After I straighten out the Port naming thing, I'll start in on the NIC
> connection.


You can pipe your console output to a file, I just saw it the other
day, but can not
find it, you basicly pipe the I/O to a file and at the same time to
your screen so you
can see what is going on, but at the same time you can go back and look at the
file and see what scrolled off of the screen.


-- 
Chuck Hast 
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."