VLAN configuration

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

Jean-Francois Stenuit wrote:
> 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.
>

which ethernet adapter have you and which driver are you using

--
Weill Philippe - Administrateur Systeme et Reseaux

On Mon, 25 Apr 2005, Philippe WEILL wrote:

> Jean-Francois Stenuit wrote:
>
> > 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.
> >
>
> which ethernet adapter have you and which driver are you using

Hi Philippe,

Last test were done on this set-up :

0000:02:04.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
0000:02:04.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
0000:02:05.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
0000:02:05.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
0000:02:0a.0 Ethernet controller: Intel Corp. 82540EM Gigabit Ethernet Controller (rev 02)

i.e. Two Intel® PRO/1000 MT Dual Port Server Adapter and one on-board
controller.

Kernel 2.6.8.1 with e.a. options :
CONFIG_EXPERIMENTAL=y
CONFIG_VLAN_8021Q=y
CONFIG_E1000=y
CONFIG_E1000_NAPI=y

Similar tests were done in the past with Intel® PRO/100 S Server Adapter
/ CONFIG_EEPRO100=y and with 3Com® 3C905CX-TX-M / CONFIG_VORTEX=y.

Hope you can help.

--
Jean-Francois "Jef" Stenuit

Jean-Francois Stenuit wrote:
> On Mon, 25 Apr 2005, Philippe WEILL wrote:
>
>
>>Jean-Francois Stenuit wrote:
>>
>>
>>>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.
>>>
>>
>>which ethernet adapter have you and which driver are you using
>
>
> Hi Philippe,
>
> Last test were done on this set-up :
>
> 0000:02:04.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
> 0000:02:04.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
> 0000:02:05.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
> 0000:02:05.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet Controller (Copper) (rev 01)
> 0000:02:0a.0 Ethernet controller: Intel Corp. 82540EM Gigabit Ethernet Controller (rev 02)
>
> i.e. Two Intel® PRO/1000 MT Dual Port Server Adapter and one on-board
> controller.
>
> Kernel 2.6.8.1 with e.a. options :
> CONFIG_EXPERIMENTAL=y
> CONFIG_VLAN_8021Q=y
> CONFIG_E1000=y
> CONFIG_E1000_NAPI=y
>
> Similar tests were done in the past with Intel® PRO/100 S Server Adapter
> / CONFIG_EEPRO100=y and with 3Com® 3C905CX-TX-M / CONFIG_VORTEX=y.
>
> Hope you can help.
>

I never made test on 3com but i never had vlan problem with driver INTEL ( e100
and e1000 ) on 2.4 kernel ( no test on 2.6 )

more /etc/sysconfig/nic/ifcfg-eth0
DEVICE=eth0
ONBOOT=yes
MODULE="e100"
DHCP=no
IP=0.0.0.0
^^^^^^^^^^^ it's important

Linux xxx 2.4.27-grsec

vconfig add eth0 352
vconfig add eth0 2041

eth0 Link encap:Ethernet HWaddr 00:E0:81:52:60:01
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21362988 errors:0 dropped:0 overruns:0 frame:0
TX packets:21579255 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2577321298 (2.4 GiB) TX bytes:3167201492 (2.9 GiB)

vlan352 Link encap:Ethernet HWaddr 00:E0:81:52:60:01
inet addr:xxx.yyy.zzz.2 Bcast:xxx.yyy.zzz.15 Mask:255.255.255.240
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:21134008 errors:0 dropped:0 overruns:0 frame:0
TX packets:17954002 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2263935520 (2.1 GiB) TX bytes:2237536162 (2.0 GiB)

vlan2041 Link encap:Ethernet HWaddr 00:E0:81:52:60:01
inet addr:aaa.bbb.ccc.2 Bcast:aaa.bbb.ccc.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:229071 errors:0 dropped:0 overruns:0 frame:0
TX packets:3625367 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:14312337 (13.6 MiB) TX bytes:929688376 (886.6 MiB)


Hope this help
--
Weill Philippe - Administrateur Systeme et Reseaux