Re: Why screw with the AX.25 configs?
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
On Sun, 13 Mar 2011, Curt, WE7U wrote:
So why, after sweating over a working config, does it become non-working after some time with Linux?I've had a config that I've tweaked from time to time, but now it appears to work differently in OpenSuSE-11.3.Specifically:*) I used to be able to name an AX.25 port nearly anything I wanted. For instance I have one called "aprs" and used to use one called "opentrac" also. It appears now that the "aprs" port is forced to be called "ax0" in "ifconfig",
In the Xastir AX.25 HOWTO I see this: > /usr/sbin/kissattach /dev/ttyUSB0 aprs 188.8.131.52 AX.25 port aprs bound to device ax0 Which shows that the KISS device is called "aprs", but the actual networking device underneath is "ax0". I guess the above explains the "problem" I saw sufficiently, so ignore that bit of my previous message. The queries about "ifup" and routes getting auto-set still stand though. -- Curt, WE7U. http://www.eskimo.com/~archer U.S. Weather Alerts: Firenet.us, port 14580, filter "t/n e/WE7U-WX" -- To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html