Re: VLAN over loopback interface
From: Christopher Fowler
Date: Mon Mar 03 2008 - 16:35:09 EST
What about using VLAN on the dummy network driver?
On Mon, 2008-03-03 at 16:14 -0500, Khoa Nguyen wrote:
> Hi,
>
> I notice 2.6.18 and 2.6.24 behave differently when I tried to
> configure a vlan interface over loopback (I know, it's silly to create
> a vlan over loopback, but our legacy app depends on it). But why under
> 2.6.24, a vlan over loopback assumes Ethernet encapsulation? And I
> can't assign IP address or bring this interface up under 2.6.24. What
> should I do to make sure it uses "Local Loopback" encapsulation?
>
> Thanks,
> Khoa
>
>
> 2.4.18.1 kernel:
> ===========
> [root@mss2 ~]# vconfig add lo 50
> Added VLAN with VID == 50 to IF -:lo:-
>
> [root@mss2 ~]# ifconfig lo.50 192.0.2.2 netmask 255.255.255.255 up
> [root@mss2 ~]# ifconfig lo.50
> lo.50 Link encap:Local Loopback
> inet addr:192.0.2.2 Mask:255.255.255.255
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
>
>
> 2.6.24 kernel
> =========
> vconfig add lo 50
> Added VLAN with VID == 50 to IF -:lo:-
> [root@mss2 os]# ifconfig lo.50
> lo.50 Link encap:Ethernet HWaddr 00:00:00:00:00:00
> LOOPBACK MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> [root@mss2 os]# ifconfig lo.50 192.0.2.2 netmask 255.255.255.255 up
> SIOCSIFFLAGS: Invalid argument
> SIOCSIFFLAGS: Invalid argument
> --
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html