VLAN configuration

From: Jean-Francois Stenuit (jfs_at_skynet.i8spam.be)
Date: 04/22/05


Date: Fri, 22 Apr 2005 18:28:39 +0200


Hi there,

A question that's on my mind for some time now.

I'd like to configure VLANs on a Debian Gnu/Linux box. I tried with
kernels in trains 2.4 and 2.6 but have the same symptoms all the time. I
must be missing something but I can't find out what.

Symptoms are clear : I configure my vlan using the "vconfig" command, then
I try to configure the virtual interface using "ifconfig" and this last
command freezes. In another window, I try to view the new interfaces using
"ifconfig -a" and this freezes as well.

Now the strangest thing : when I try to kill the frozen "ifconfig"'s, I
simply can't ! Even "kill -9" does not work.

Am I alone in this situation ?
Do I need to rebuild the ifconfig command ?

Thanks in advance for your enlightments.

-- 
Jean-Francois "Jef" Stenuit


Relevant Pages

  • Re: [SLE] 10.0: no net, now what, contd
    ... > When you're in Linux open a console shell issue the command ... > the ifconfig command, and place it at the beginning of that line, left ... > hardware problem. ... >> YaST from the desktop, and how to add its icon there.) ...
    (SuSE)
  • Re: Desired behaviour of "ifconfig -alias"
    ... ifconfig bce0 -alias ... It turns out that this command eliminated the primary IP for the ... are running in automated scripts, ... an interface are equal, just like hardlinks on a file. ...
    (freebsd-stable)
  • Re: ifconfig command shows only loopback device.
    ... unix syzadmin wrote: ... command shows 2 entries for Intel Corporation 82544EIGigbit Ethernet ... However the "ifconfig" shows only loopback device. ...
    (RedHat)
  • Re: [SLE] Adding a secondary IP onto NIC
    ... > You appear to have found a bug in the ifup script of SuSE 9.1. ... I don't see any bug in ifup script. ... But, ifup uses ip command, not ifconfig, to configure interfaces. ...
    (SuSE)
  • Re: networking: fixed ip address and dhcp
    ... "route -n" command) ... ifconfig eth1 XXX.YYY.ZZZ.WWW netmask 255.255.255.0 ... This does not work now - I can't ping out. ...
    (Debian-User)