public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Livio Ceci <livio@cyclades.com.br>
To: khc@pm.waw.pl, linux-kernel@vger.kernel.org
Subject: [Fwd: HDLC driver: Frame-relay Inverse ARP]
Date: Thu, 16 May 2002 16:40:18 -0300	[thread overview]
Message-ID: <3CE40B22.199C4F07@cyclades.com.br> (raw)

[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]

Hi Mr. Halasa.

I sent you a message some days ago asking for the inverse ARP
implementation status in the hdlc driver.

Once I haven't received any answer, I started implementing it by myself,
based on linux kernel version 2.4.17. The protocol message exchange,
ARPOP_InREQUEST and ARPOP_InREPLY, is done and working fine, both being
treated by arp_rcv function in arp.c file.

Now, I would like to know which action should be taken when arp_rcv
(arp.c) receives an inverse ARP reply message. I thought just to add a
new route to the host that sent the message, but I would prefer having
your opinion about that.

I added a new paramenter in sethdlc to enable inverse arp, and just by
now the pointopoint parameter in ifconfig should be set to 0.0.0.0.
Thus, to setup a pvc :

sethdlc hdlc0 v35 clock ext
sethdlc hdlc0 fr lmi ansi dce t391 10 t392 15 n391 10 n392 10 n393 10
ifconfig hdlc0 0 0.0.0.0 up

sethdlc hdlc0 create 16 inverse_arp
ifconfig pvc0 10.0.0.2 pointopoint 0.0.0.0 mtu 1500 up

I attached a diff file with the changes I did, and also the sethdlc.
Please analyse them and send me back your comments, and if possible,
something that help me to "fill the blanks" I left as ??? in the code.

Thanks in advance.

Livio.

[-- Attachment #2: invARP.tgz --]
[-- Type: application/octet-stream, Size: 10995 bytes --]

             reply	other threads:[~2002-05-16 19:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-16 19:40 Livio Ceci [this message]
2002-05-19 15:17 ` [Fwd: HDLC driver: Frame-relay Inverse ARP] Francois Romieu

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=3CE40B22.199C4F07@cyclades.com.br \
    --to=livio@cyclades.com.br \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=livio@cyclades.com \
    /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