From: Ramin Alidousti <ramin@UU.NET>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Will advanced linux routing help me
Date: Wed, 25 Apr 2001 12:50:42 +0000 [thread overview]
Message-ID: <marc-lartc-98820315409677@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98816711030206@msgid-missing>
On Wed, Apr 25, 2001 at 09:39:27AM +0200, Arthur van Leeuwen wrote:
> Doei, Arthur. (The tricky part is the link-state monitoring... at the TCP/IP
> level this is theoretically impossible...)
Yes, indeed. There is no special protocol for this. That's why OSPF and
his younger and older brothers have those HELO packets. That's why TCP
has the optional keepalive segments (although, in case of TCP it's an
end-to-end behaviour).
If you know the IP of the next hop router and if that router has not been
instructed to ignore ICMP requests, ping might help. If you don't know
the IP, pinging to the subnet broadcast will also do.
Ramin
>
> --
> /\ / | arthurvl@sci.kun.nl | Work like you don't need the money
> /__\ / | A friend is someone with whom | Love like you have never been hurt
> / \/__ | you can dare to be yourself | Dance like there's nobody watching
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
next prev parent reply other threads:[~2001-04-25 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-25 2:51 [LARTC] Will advanced linux routing help me Sushil Suresh
2001-04-25 7:39 ` Arthur van Leeuwen
2001-04-25 12:50 ` Ramin Alidousti [this message]
2001-04-27 10:41 ` Sushil Suresh
2001-04-27 10:49 ` Sushil Suresh
2001-04-27 11:41 ` Arthur van Leeuwen
2001-04-27 13:30 ` Ramin Alidousti
2001-04-27 13:32 ` Ramin Alidousti
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=marc-lartc-98820315409677@msgid-missing \
--to=ramin@uu.net \
--cc=lartc@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.