Hello all 1) Anyone got any advice how to overcome the following kissparms used obsolete which I noticed in the log. Extract from my kernel log file. Apr 30 11:51:12 gb7cip kernel: NET4: G4KLX/GW4PTS AX.25 for Linux. Version 0.37 for Linux NET4.0 Apr 30 11:51:12 gb7cip kernel: AX.25 Multikiss device enabled Apr 30 11:51:12 gb7cip kernel: G4KLX NET/ROM for Linux. Version 0.7 for AX25.037 Linux 2.1 Apr 30 11:53:41 gb7cip kernel: kissparms uses obsolete (PF_INET,SOCK_PACKET) Unable to get the Linux_Hams_archive search engine to work this morning on trying to check if someone has solve this already. :-( 2) I have been for the past four months trying to solve a problem (intermittent and random) where one of my kissattached interfaces (not the same one) (which all run AX25 TCP/IP & NetRom). The AX25 level 2 and netrom connections appears to fail to process the data. I can see from the listen trace I can see inbound connects and acks being returned (hear the TX tones (1200bd) or white noise(9600db) Outbound connects now being responded. All the time the TCP/IP traffic on the radio interface is still flowing. The physical ports, serial interfaces have been moved around, IRQ's changed to move isolate the problem. One thought I had was it could be related to inbound connections being made to the system by stations using automatic connections scripts as they hop, hop to connect to remote systems and the circuits is not clearing down correctly when the link fails externally for some reason. Not noticing hung open sockets on my system using 'netstats' Only cure I have found 1) is to reboot the system 2) is to kill off the kissattached driver for the interface and rerun the kissattached, reload the routing table & ifconfig params (for the IP side). Stop and restart the ax25d The ax25 & Netrom continues to work. I have not yet been able to trap the fault condition so that I can replicate the condition and give the software developers the evidence. On the hardware side I am using 7 serial ports which their own dedicated IRQ's. I ran this configuration for 7 months (2.0.35 kernel) before I rebuilt the system on a new harddisk with the Slarkware 7.0 2.2.13 kernel (December 1999) Has anyone else experienced a similar problem. Current related software installed is:- Slakware 7.0 Kernel 2.2.14 ax25-tools-0.0.6 ax25-apps-0.0.4 node-0.3.0 libax25-0.0.7 node-0.3.0 http-1.22 xd7.01j regards Paul g4apl@gb7cip. -- [EMAIL PROTECTED]
