From: <dplatt@radagast.org>
To: linux-hams@vger.kernel.org
Subject: Re: ax25ipd issue
Date: Sat, 11 Jun 2005 13:18:32 -0700 [thread overview]
Message-ID: <1DhCR6-3jp-00@radagast.org> (raw)
> AX25IP works with not TCP, not UDP, but with IP protocol 93. It's a
> stateless protocol consisting of not much else than wrapping an
> AX.25 packet to an IP frame. Then there are variants that use UDP
> to do pretty much the same.
>
> If doing a DNS lookup for each outgoing AX.25 packet is ok for
> people then so be it. You have the source. Modify it.
>
> I find it braindead. The fix should be something else.
I'm not sure that actually doing a DNS lookup (via the resolver
interface) is necessary or desireable.
However, I do think that when the daemon does such a lookup, and
caches the resulting IP address, it should also cache the current time
and the time-to-live value from the DNS lookup. Once the response's
time-to-live expires, it should discard the callsign-to-IP-address
mapping and look it up again.
For the daemon to assume that a DNS response has an effectively
infinite lifetime is not a good thing.
next reply other threads:[~2005-06-11 20:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 20:18 dplatt [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-11 13:38 ax25ipd issue Chuck Hast
2005-06-11 15:41 ` John Hurst
2005-06-12 19:05 ` Bernard Pidoux
2005-06-12 21:37 ` Chuck Hast
2005-06-11 19:43 ` Tomi Manninen
2005-06-11 19:54 ` Jeremy Utley
2005-06-11 20:09 ` Tomi Manninen
2005-06-11 20:19 ` John Hurst
2005-06-11 20:32 ` David D. Hagood
2005-06-11 20:51 ` Chuck Hast
2005-06-11 20:45 ` Chuck Hast
2005-06-23 11:51 ` Steve Fraser
2005-06-23 12:15 ` Chuck Hast
2005-06-23 16:13 ` Bernard Pidoux
2005-06-11 23:03 ` Steve Fraser
2005-06-12 4:50 ` Jeremy Utley
2005-06-12 14:24 ` Tomi Manninen
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=1DhCR6-3jp-00@radagast.org \
--to=dplatt@radagast.org \
--cc=linux-hams@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.