Hi again,
Thanks for the follow up.
In message <0006082050271Q.01326@pa3gcu>, Richard Adams
<[EMAIL PROTECTED]> writes
>On Thu, 08 Jun 2000, Paul Lewis wrote about, kissparams & mkiss:
>> Hello All
>>
>>
>> I am still looking for a reason why my ax25/netrom ports stop decoding,
>> while tcp/ip still over the failed port.
>>
>> I noticed from the logs the following.
>>
>> Is there a problem with the kissparams code as reported in the kernel
>> log listed below.
>
>I belive Tomi has said before, you can ignore them, but for the record my
>comments.
OK
>BTW; just about all of my ax25 stuff is modules.
I have since moving to 2.2.# kernels started using modules, including
AX25 related code.
I use separate TNC's running in Kiss Mode (TheNet X1j4 Select Kiss mode)
been running TheNet nodes since about 1989 :-)
>
>> Jun 8 18:59:09 gb7cip kernel: NET4: G4KLX/GW4PTS AX.25 for Linux.
>> Version 0.37
>> Jun 8 18:59:09 gb7cip kernel: AX.25 Multikiss device enabled
>> Jun 8 18:59:09 gb7cip kernel: G4KLX NET/ROM for Linux. Version 0.7 for
>> AX25.037
>>
>>
>> Jun 8 19:00:25 gb7cip kernel: kissparms uses obsolete
>> (PF_INET,SOCK_PACKET)
>
>I have serveral machines all running kernel ax25 netrom, drivers include
>mkiss scc dxlmodem, i also get the obsolite message for;
>netromd and mheardd, but not from kissparms, further more i cant say i have
>seen your problem.
> I have seen scc interfaces simply stop working including IP traffic, but
>that was in 2.0.xx kernls, i must say i have no problem now.
>
>A small comment, you said there is only one way to get the interface going
>again, thats rebooting, now i would bet if you did ifconfig ax0 down, (if it
>be ax0 causing problems) then up it again as per your start scripts all
>would work again as it should, that was what i used to do, in fact i had
>scripts running under cron to keep the system going.
I have tried that on a couple of occasions Richard.
Downing the interface, and manually calling the commands to reconfigure.
Seems to cause more problems.
When the interface is dropped. XFBBD falls over as lost an interface,
and the LINKS linux_node command causes a code dump. Unloading and
reloading the interface does not seem to overcome that.
This as been identified in the other thread when Tomi ask me to try and
cat /proc/net/ax25 which cause a dump. So looks like something is
getting corrupted in this area.
Reloaded the system yesterday evening. Now waiting for the next
occurrence.
[snip]
--
[EMAIL PROTECTED]
