Karl, (and Larry too)
I would have replied sooner but I wanted to try something first. There is a message
from Tomi Manninen about this same problem. Tomi recommends adding an IP address to
the device when bringing it up. So I did: ifconfig bcsf0 down, then:
ifconfig bcsf0 10.0.0.5 hw ax25 K5DKZ-1 up
The error messages went away but call still did not work right. It keyed the radio
and left it keyed. (I tried this on ttyS1 as well as ttyS0 with the same results.)
I then reinstalled RH 5.2 2.0.36 with /boot = to 10 meg; a 60meg swap partition, and
the rest of the 1.6gig hard drive under / . I made sure that LILO was installed on
the /boot partition. If you let it do the default Workstation or Server
installation, LILO goes to the MBR. I have had problems in the past with LILO in the
MBR. Its only a problem if you don't know that is where it is. I carefully followed
the instructions to recompile the kernel after installing the kernel sources. (The
source code was not installed during the re-installation.) I edited lilo.conf to
allow a boot from either
the new kernel or the old one. I installed the old ax25-util rpm and created the
axports
file in /etc/ax25. I followed the ax25 howto for baycom. (no IP addresses). bc0
came up and worked fine with call and listen. Using ifconfig, I found that the bc0
device had been assigned IPs of 0.0.0.0. That was not the case under 2.2.10 with the
bcsf0 device. It works now but the MTU for the bc0 device is 1500 instead of the 256
it is supposed to be. So I'm not out of the woods yet. It works but I'm not sure
why with an MTU of 1500.
It takes about 2 hours to make a kernel on the 486/40. I wanted to use 2.2.10 to be
able to tryout ipchains. Now I am going to settle ipfwadm as I have it installed on
the pentium that is acting as a server and router now. When I free up the pentium, I
can use it for further experiments and find out what is going on. The pentium does a
kernel in under 15 minutes.
One other bit of info that might be useful. I used fdisk to create the partitions
and disk druid to set the labels. If you forget to activate the first partition with
fdisk -a, you will get the 'rom bios not found' error and the system will not boot
off the hard drive.
73
Frank Kamp
K5DKZ
"Karl F. Larsen" wrote:
> Hi Frank, for whatever it's worth I have exactly the same problem
> with my system and kernel 2.2.5 which is: Listen and everything works
> perfect except "call". I am using Red Hat 6 that makes changing things
> hard.
>
> On Tue, 6 Jul 1999 [EMAIL PROTECTED] wrote:
>
> } Larry,
> }
> } I'm using the 'old' ax25-utils-2.1.42a-3.i386.rpm. The tar.gz package would
> } not compile for me even when I installed the X11R6 libraries. If you do a
> } 'make config' on the tar.gz package it will tell you more than you wanted to
> } know about what is 'good' and what is 'bad' about your Linux installation. It
> } was telling me I needed X11R6 and XForms before it could compile everything.
> } You can get the tar.gz package to install sample configuration files by doing
> } 'make installconf'.
> }
> } I am now trying to setup one 486/40 as a router and server. Trying to use RH
> } 5.2 with a 2.2.10 kernel. Want to be able to use the thing as a Samba server,
> } Modem server, and Packet machine for Baycom. As you might expect everything
> } works except for Baycom. (Should have quit when I was ahead.) I keep getting:
> }
> } axconfig: port bcsf0 not active
> } listen: no AX.25 port data configured
> }
> } If I leave it alone and wait I get:
> }
> } Port: bcsf0 AX25: 'and lots of recieved data'
> }
> } But the call utility will not work.
> }
> } If I do netstat, it verifies that there are no ax25 sockets active. So how am
> } I recieving the data off the Baycom modem?
> }
> } I'm sure it has something to do with configuration. I had this problem before
> } and solved it by fixing the axports file, but that same fix will not work now.
> } Begining to wonder if all the neat routing features of 2.2.10 are in conflict
> } with ax25. Its probably something really stupid that I didn't comprehend after
> } reading the manuals for the fourth time. (Or maybe a hardware problem.}
> }
> } Hope you are having better luck.
> }
> } 73,
> } Frank Kamp
> } K5DKZ
> }
> } Larry Molitor wrote:
> }
> } > Frank,
> } >
> } > Thanks for the response.
> } >
> } > Seems like your experiences mostly parallel mine.
> } >
> } > I used the "new" rpm's and had it somewhat working, but as you said, no
> } > config files. I tried the "new" tar'd stuff, but could never get them to
> } > compile. I assume that means I'm missing something again. I am trying to do
> } > this with a minimum system, and keep running into problems with missing
> } > libraries and such.
> } >
> } > Were you using the "new" rpm's or the 2.1.42a-3 versions?
> } >
> } > I'll give your suggestions a try, but not sure if that's a good test. This
> } > thing is so screwed up now I may have to start all over.... again....
> } >
> } > 73,
> } >
> } > Larry - W7IUV
> } > [EMAIL PROTECTED]
> } > http://www.axtek.com/w7iuv
> } > Amp pix at http://207.108.137.61
> }
> }
>
> Best wishes
>
> - Karl F. Larsen, [EMAIL PROTECTED] (505) 524-3303 -
