All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: Thomas Graf <tgraf@suug.ch>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
	linux-decnet-user@lists.sourceforge.net
Subject: Re: [PATCH net-next 1/2] decnet: Parse netlink attributes on our own
Date: Fri, 22 Mar 2013 14:29:51 +0000	[thread overview]
Message-ID: <1363962591.2709.26.camel@menhir> (raw)
In-Reply-To: <20130322142735.GA11368@casper.infradead.org>

Hi,

On Fri, 2013-03-22 at 14:27 +0000, Thomas Graf wrote:
> On 03/21/13 at 06:04pm, Steven Whitehouse wrote:
> > You shouldn't need any special hardware to test this. A copy of iproute2
> > should be enough as you should be able to use that to create an
> > interface or two and a route between them, etc. Although DECnet routing
> > works in a different way to ip routing, the Linux implementation tries
> > to stick fairly closely to the ip way of doing things whenever it can in
> > order to share infrastructure. Now that ip has diverged a fair bit over
> > time that isn't quite as true as it was, but there shouldn't be anything
> > too surprising in there.
> 
> Alright, I did some basic testing with iproute2. I do not claim
> to understand what I did but I ran the following:
> 
> $ ip -f dnet route add 1.661 dev em1
> $ ip -f dnet route list
> 1.661 dev em1  scope link
> 
> $ ip -f dnet neigh add 6.662 dev em1
> $ ip -f dnet neigh list
> 6.662 dev em1 lladdr aa:00:04:00:96:1a PERMANENT
> 
> $ ip -f dnet addr add 1.111 dev em1
> $ ip -f dnet addr list
> 2: em1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
>     dnet 1.111/16 scope global em1

That looks sane to me. The only thing I could think of to add to that
list would be to use ip route get to do a lookup, but otherwise, that
seems to cover everything pretty much,

Steve.

  reply	other threads:[~2013-03-22 14:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-21 17:45 [PATCH net-next 0/2] Get rid of attribute parsing in rtnetlink_rcv_msg() Thomas Graf
2013-03-21 17:45 ` [PATCH net-next 1/2] decnet: Parse netlink attributes on our own Thomas Graf
2013-03-21 18:04   ` Steven Whitehouse
2013-03-22 14:27     ` Thomas Graf
2013-03-22 14:29       ` Steven Whitehouse [this message]
2013-03-22 14:31       ` David Miller
2013-03-22 16:50         ` [PATCH net-next] decnet: Move rtm_dn_policy to dn_route to make it available if !CONFIG_DECNET_ROUTER Thomas Graf
2013-03-22 16:52           ` David Miller
2013-03-21 17:45 ` [PATCH net-next 2/2] rtnetlink: Remove passing of attributes into rtnl_doit functions Thomas Graf
2013-03-21 19:19 ` [PATCH net-next 0/2] Get rid of attribute parsing in rtnetlink_rcv_msg() David Miller

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=1363962591.2709.26.camel@menhir \
    --to=swhiteho@redhat.com \
    --cc=davem@davemloft.net \
    --cc=linux-decnet-user@lists.sourceforge.net \
    --cc=netdev@vger.kernel.org \
    --cc=tgraf@suug.ch \
    /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.