A workaround I used successfully in the past was to assign the IPv6 address
as an “up” action on the IPv4 interface.
Something like:

    iface eth1.10 inet static
        vlan_raw_device eth1
        address 192.168.10.1
        netmask 255.255.255.0
        broadcast 192.168.10.255
        up ip -6 addr add 2001:db8:10::1/64 dev $IFACE

dMb

> On 10 Mar 2016, at 20:11, Andrew <ni...@seti.kr.ua> wrote:
> 
> It seems like vlan helper script tries to add/remove iface twice, once 
> per each iface record.
> 
> 10.03.2016 21:42, Sven Kirmess пишет:
>> I'm trying to configure an IPv6 and an IPv4 address on a VLAN interface.
>> 
>> When I configure it on a non-VLAN interface like this in
>> /etc/network/interfaces It works as expected, but when I put the same
>> configuration on a VLAN interface I get an error message on up and down. It
>> looks like it works anyway but is this the correct way to configure that?
>> 
>> firewall# cat /etc/network/interfaces
>> iface em0 inet static
>>         address 192.168.20.1
>>         netmask 255.255.255.0
>>         broadcast +
>> iface em0 inet6 static
>>         address 2001:db8:20::1
>>         netmask 64
>> 
>> iface em0.30 inet static
>>         address 192.168.30.1
>>         netmask 255.255.255.0
>>         broadcast +
>> iface em0.30 inet6 static
>>         address 2001:db8:30::1
>>         netmask 64
>> 
>> 
>> firewall# ifup em0
>> firewall# ifconfig em0
>> em0       Link encap:Ethernet  HWaddr 00:0D:B9:40:7F:EC
>>           inet addr:192.168.20.1  Bcast:192.168.20.255  Mask:255.255.255.0
>>           inet6 addr: 2001:db8:20::1/64 Scope:Global
>>           UP BROADCAST MULTICAST  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:1000
>>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>> 
>> firewall# ifdown em0
>> firewall# ifconfig em0
>> em0       Link encap:Ethernet  HWaddr 00:0D:B9:40:7F:EC
>>           BROADCAST MULTICAST  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:1000
>>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>> 
>> firewall#
>> 
>> 
>> 
>> firewall# ifup em0.30
>> vconfig: ioctl error for add: File exists
>> firewall# ifconfig em0.30
>> em0.30    Link encap:Ethernet  HWaddr 00:0D:B9:40:7F:EC
>>           inet addr:192.168.30.1  Bcast:192.168.30.255  Mask:255.255.255.0
>>           inet6 addr: 2001:db8:30::1/64 Scope:Global
>>           UP BROADCAST MULTICAST  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:1000
>>           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>> 
>> firewall# ifdown em0.30
>> Cannot find device "em0.30"
>> firewall# ifconfig em0.30
>> ifconfig: em0.30: error fetching interface information: Device not found
>> firewall#
>> ------------------------------------------------------------------------------
>> Transform Data into Opportunity.
>> Accelerate data analysis in your applications with
>> Intel Data Analytics Acceleration Library.
>> Click to learn more.
>> http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
>> ------------------------------------------------------------------------
>> leaf-user mailing list: leaf-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/leaf-user
>> Support Request -- http://leaf-project.org/
> 


------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
------------------------------------------------------------------------
leaf-user mailing list: leaf-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/

Reply via email to