All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Kocian <milon@wq.cz>
To: Denys Fedoryshchenko <denys@visp.net.lb>
Cc: Patrick McHardy <kaber@trash.net>,
	Ben Greear <greearb@candelatech.com>,
	Stephen Hemminger <shemminger@vyatta.com>,
	netdev@vger.kernel.org
Subject: Re: Could you make vconfig less stupid?
Date: Tue, 7 Oct 2008 14:48:21 +0200	[thread overview]
Message-ID: <20081007124820.GG4606@ntm.vs.lam.cz> (raw)
In-Reply-To: <200810071520.56610.denys@visp.net.lb>

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

On Tue, Oct 07, 2008 at 03:20:56PM +0300, Denys Fedoryshchenko wrote:
 
> 

> diff -Naur iproute2.backup/ip/iplink.c iproute2/ip/iplink.c
> --- iproute2.backup/ip/iplink.c	2008-10-05 15:41:59.000000000 +0000
> +++ iproute2/ip/iplink.c	2008-10-07 12:14:28.000000000 +0000
> @@ -54,6 +54,10 @@
>  	fprintf(stderr, "	                     mtu MTU }\n");
>  	fprintf(stderr, "	                     netns PID }\n");
>  	fprintf(stderr, "       ip link show [ DEVICE ]\n");
> +	fprintf(stderr, "       ip link add link PARENTDEV type { vlan | veth } { ... | help }\n");
> +	fprintf(stderr, "       ip link add link PARENTDEV NEWDEVICE type macvlan { ... | help }\n");
> +	fprintf(stderr, "       ip link change link PARENTDEV type { vlan | veth } { ... | help}\n");
> +	fprintf(stderr, "       ip link del dev DEVICE\n");
>  	exit(-1);
>  }
>  
hello,

btw. How can I see vlan id on device ?
After:
# ip l a l eth0 type vlan id 100
# ip a
I see:

64: vlan0@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN 
    link/ether 00:16:d3:3e:4e:b9 brd ff:ff:ff:ff:ff:ff

No vlan id in interface name ?

# ip -V
ip utility, iproute2-ss080725

regards,

-- 
Milan Kocian

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2008-10-07 13:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-06 18:24 Could you make vconfig less stupid? Stephen Hemminger
2008-10-06 22:26 ` Patrick McHardy
2008-10-07  2:32   ` Ben Greear
2008-10-07 11:31     ` Patrick McHardy
2008-10-07 12:20       ` Denys Fedoryshchenko
2008-10-07 12:24         ` Patrick McHardy
2008-10-07 12:48         ` Milan Kocian [this message]
2008-10-07 12:49           ` Denys Fedoryshchenko
2008-10-07 12:56             ` Patrick McHardy
2008-10-07 13:16               ` Martin Josefsson
2008-10-07 13:54                 ` Patrick McHardy
2008-10-07 13:57                 ` Patrick McHardy
2008-10-07 13:28               ` Milan Kocian
2008-10-07 13:29                 ` Patrick McHardy
2008-10-07 14:06                 ` Stephen Hemminger

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=20081007124820.GG4606@ntm.vs.lam.cz \
    --to=milon@wq.cz \
    --cc=denys@visp.net.lb \
    --cc=greearb@candelatech.com \
    --cc=kaber@trash.net \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.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 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.