From: "IT3 Stuart Blake Tener, USN" <teners@bh90210.net>
To: "Mike McCarthy, W1NR" <lists@w1nr.net>, linux-hams@vger.kernel.org
Subject: Re: Some packet questions...
Date: Tue, 31 Oct 2006 12:03:06 -0800 [thread overview]
Message-ID: <C16CEBFA.A30C%teners@bh90210.net> (raw)
In-Reply-To: <000301c6fceb$26ee8dc0$05fcfc0a@LoJackOne.LoJack.com>
On 10/31/06 4:50 AM, "Mike McCarthy, W1NR" <lists@w1nr.net> wrote:
> Nothing has really changed in many years, so the documentation hasn't had
> any reason to be revised.
>
> I found my local IP address coordinator very helpful in getting IP over
> AX.25 running.
I have been given so many stories concerning IP address coordination that I
got fed up with even trying to coordinate! First I was assigned a 32 address
block in the Philly area, then I was told in California that it would not be
workable. Why not? If this is truly an IP network, why would I need to have
a new set of IP address when only the physical location changed?
I am still interested now to find out what my current IP assignment is, and
as well what the 32 address range is I was given.
>
> There have been major changes to the Kernel drivers for many of the AX.25
> protocols having to do with SMP. With dual core processor based systems
> common, this was really needed.
Currently I have a PowerBook (PowerPC based Mac) but plan to upgrade in the
coming months (post Xmas when many "new" Macbooks have been returned after
the Xmas shopping season!) and purchase a new MacBook Pro. When I do that I
will be having an x86 based machine to run both MacOS and Linux on, thus a
machine that support SMP will be of distinct interest to me in the very near
future.
>
> Do you know what Linux distribution you plan to use? I prefer openSUSE
> (www.opensuse.org) because the AX.25 kernel modules are built in by default.
I tilt in the general direction of deploying either Fedora (I am more a
RedHat type weenie than SuSE) or Ubuntu on the Mac. Alternatively, I have a
Sun E450 and would consider deploying Ubuntu on it as well, and want to make
AX.25/IP work.
> No Kernel rebuilding required. The Ham Radio packages are also available at
> ftp.w1nr.net. If you go that route, use 10.1 "remastered". The kernel that
> shipped with 10.0 was broken as the AX.25 SMP modifications were not quite
> fully debugged. The management interface in SUSE can't be beat.
Where does SMP based AX.25 stand in the instant sir?
>
> Mike, W1NR
>
> ----- Original Message -----
> From: "IT3 Stuart Blake Tener, USN" <teners@bh90210.net>
> To: <linux-hams@vger.kernel.org>
> Sent: Monday, October 30, 2006 4:56 PM
> Subject: Some packet questions...
>
>
>> To whom it shall concern:
>>
>> It has been an exceeding long time since I have been active in the what
>> was "a new mode" back in the day, Packet Radio! Since the late 90s it
>> seems
>> a lot has changed, and the word on the street is that packet has all but
>> in
>> most cases evaporated from the once large network it was (at least from
>> the
>> few people I spoke to at a Hamfest recently in the East Coast).
>>
>> Now, personally, I do not know if the evaporation of packet has, indeed
>> really become occurrent, but I am curious to find out if there will be
>> much
>> of an activity level in most major metropolitan areas that I should I
>> think
>> about rebuilding a packet station, and how well it works these days.
>>
>> I plan to use a W32A that I have (for the moment) as the radio with the
>> olde 5w/35w amplifier I have from (gasp) RF Concepts/Kantronics, as well
>> as
>> an IC-91AD and/or D700A.
>>
>> There is an AX.25 How-To which is very olde that is instructive to the
>> concerns of asserting AX.25 protocol via the Linux Kernel. I am interested
>> to configure a Linux box for the purposes of having an AX.25 router, has a
>> copy of this document been updated anytime lately?
>>
>> I was reading in Page 83 of the November 2006 CQ Magazine that someone
>> used a metalized windshield sunshade, and since I was in the kitchen
>> making
>> some pasta at the time, how workable would it be to put a mag-mount on top
>> of a large pasta pot as a ground plane, any comments on that? The antenna
>> under consideration for the "Pasta Pot Ground Plane" would be an SG7900A.
>>
>> Stuart, N3GWG (Amateur Extra)
>>
>>
>> --
>>
>> Very Respectfully,
>>
>> IT3 Stuart Blake Tener, USN
>> Beverly Hills, California
>> Amateur Radio Call Sign: N3GWG (Extra)
>> email: teners@bh90210.net
>> phone: +(1) 310.358.0202 (Beverly Hills, CA)
>> phone: +(1) 215.338.6005 (Philadelphia, PA)
>> E-Fax: +(1) 915.773.0935 (Telecopier)
>>
>> Military emails (checked monthly until remote NMCI access is secured)
>> NIPRNET: stuart.tener@navy.mil / tenerstu@nro.mil / stuart.tener@dia.mil
>> SIPRNET: NONE
>> TS/SCI: cntensb@dia.ic.gov (JWICS) / tenerstu@nro.ic.gov (GWAN)
>> TS/SCI: cntensb@mail.dia.us.qlat (Stone Ghost, TS//SI/REL
>> AUS/CAN/GBR/USA)
>>
>> One must like the horse to ride.
>>
>> Confidentiality Notice: This e-mail message, including any attachments, is
>> for the sole use of the intended recipient(s) and may contain confidential
>> and/or privileged information. Any unauthorized review, use, disclosure or
>> distribution is prohibited. If you are not the intended recipient, please
>> contact the sender by reply e-mail and destroy all copies of the original
>> message.
>>
>>
>>
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>
--
Very Respectfully,
IT3 Stuart Blake Tener, USN
Beverly Hills, California
Amateur Radio Call Sign: N3GWG (Extra)
email: teners@bh90210.net
phone: +(1) 310.358.0202 (Beverly Hills, CA)
phone: +(1) 215.338.6005 (Philadelphia, PA)
E-Fax: +(1) 915.773.0935 (Telecopier)
Military emails (checked monthly until remote NMCI access is secured)
NIPRNET: stuart.tener@navy.mil / tenerstu@nro.mil / stuart.tener@dia.mil
SIPRNET: NONE
TS/SCI: cntensb@dia.ic.gov (JWICS) / tenerstu@nro.ic.gov (GWAN)
TS/SCI: cntensb@mail.dia.us.qlat (Stone Ghost, TS//SI/REL AUS/CAN/GBR/USA)
One must like the horse to ride.
Confidentiality Notice: This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential
and/or privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.
next prev parent reply other threads:[~2006-10-31 20:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 21:56 Some packet questions IT3 Stuart Blake Tener, USN
2006-10-31 12:50 ` Mike McCarthy, W1NR
2006-10-31 20:03 ` IT3 Stuart Blake Tener, USN [this message]
2006-10-31 20:29 ` Bob Nielsen
2006-10-31 20:56 ` IT3 Stuart Blake Tener, USN
2006-10-31 23:46 ` Bob Nielsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C16CEBFA.A30C%teners@bh90210.net \
--to=teners@bh90210.net \
--cc=linux-hams@vger.kernel.org \
--cc=lists@w1nr.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox