From: Chuck Gelm <nc8q@gelm.net>
To: tpm@prkele.tky.hut.fi
Cc: linux-hams@vger.kernel.org
Subject: Re: Status of AX.25 in 2.5 / 2.6
Date: Mon, 29 Jul 2002 16:43:20 -0400 [thread overview]
Message-ID: <3D45A8E8.7FF854CE@gelm.net> (raw)
In-Reply-To: Pine.HPX.4.10.10207291502190.25868-100000@saturn.trs.ntc.nokia.com
Dear Sirs:
The eth1 device associated with my pppoe modem
had no IP address, yet is is displayed with
root@firewall:/# ifconfig
command. Somehow my smtp, pop, web browser,
ftp, ... all seem to find it.
:-|
Chuck nc8q
Tomi Manninen OH2BNS wrote:
>
> On Mon, 29 Jul 2002, Craig Small wrote:
>
> > If you're looking for something later, you may want to solve the
> > ancient "why does an AX.25 interface need an IP address" question.
> > The answer used to be "because it does", I'm not sure if that is still
> > the case, I've got ports sitting on a Linux computer over *there*
> > (points to rowlf) that don't have IP addresses or have 0.0.0.0
>
> I think it's still the case. If an interface doesn't have an IP address,
> it won't show up in the "list of known interfaces" from the kernel
> (SIOCGIFCONF I think). So the utils/apps will never find it...
>
> I did some digging a couple of years ago and also did a patch (with code
> mostly stolen from Matt's/Jens' new-ax.25). See:
>
> http://hes.iki.fi/archive/dev-hams/2000/0055.html
>
> I never got an answer.
>
> Oh, by the way. Has anyone done anything with the NEW-AX.25 patch lately?
> I think it has some potential but unfortunately seems it's now completely
> unmaintained.
>
> --
> Tomi Manninen Internet: oh2bns@sral.fi
> OH2BNS AX.25: oh2bns@oh2rbi.fin.eu
> KP20ME04 Amprnet: oh2bns@oh2rbi.ampr.org
>
> -
> 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
next prev parent reply other threads:[~2002-07-29 20:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-26 11:42 Status of AX.25 in 2.5 / 2.6 Ralf Baechle
2002-07-26 12:16 ` Tomi Manninen OH2BNS
2002-07-26 12:50 ` Ralf Baechle DO1GRB
2002-09-27 16:36 ` mkiss problem in kernel 2.5 Arnau Sánchez
2002-07-26 12:50 ` Status of AX.25 in 2.5 / 2.6 Steven Whitehouse
2002-07-26 18:15 ` Ralf Baechle DO1GRB
2002-07-26 23:24 ` Craig Small
2002-07-27 1:07 ` Ralf Baechle DO1GRB
2002-07-27 11:10 ` Robert Jenkins
2002-07-27 13:38 ` Ken Koster
2002-07-28 13:15 ` Ralf Baechle DO1GRB
2002-07-28 17:19 ` Riley Williams
2002-07-30 8:24 ` Jason Flynn G7OCD
2002-07-28 19:10 ` Tomi Manninen
2002-07-28 22:43 ` Craig Small
2002-07-29 12:16 ` Tomi Manninen OH2BNS
2002-07-29 18:50 ` Iain Young - G7III
2002-07-30 9:44 ` Tomi Manninen OH2BNS
2002-07-31 17:53 ` Iain Young - G7III
2002-08-01 22:10 ` Ken Koster
2002-07-30 10:50 ` Craig Small
2002-07-29 20:43 ` Chuck Gelm [this message]
2002-07-29 14:49 ` Robert Jenkins
2002-07-29 15:27 ` Tomi Manninen OH2BNS
2002-07-29 17:45 ` Robert Jenkins
2002-07-29 18:07 ` Tomi Manninen
2002-07-30 8:14 ` Jason Flynn G7OCD
2002-07-30 9:38 ` Tomi Manninen OH2BNS
2002-07-29 20:52 ` Chuck Gelm
-- strict thread matches above, loose matches on Subject: below --
2002-07-29 23:44 Stewart Wilkinson
2002-07-30 9:14 ` Tomi Manninen OH2BNS
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=3D45A8E8.7FF854CE@gelm.net \
--to=nc8q@gelm.net \
--cc=linux-hams@vger.kernel.org \
--cc=tpm@prkele.tky.hut.fi \
/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