Hi Darac
>> What I do NOT want is to have names like eth0.60 for vlan.60 incoming on
>> interface eth0.
>> Because if I decide it would be better to have vlan60 come in on eth1 I
>> would have to rename all (firewall, etc.) scripts that refer to that name.
>>
>> What I would like to have is names like eth0, eth1, eth2, vlan-staff,
>> vlan-internet, etc.
>>
>> Reading the wiki article it seems that configuring vlans is done after the
>> startup sequence
>> is pretty much done and somewhere in rc.local as it seems I have to issue a
>> modprobe 8021q first. Only then can I use 'ip link add ..' to add the vlan
>> interfaces.
>> But... That is way too late in the startup as it means all kinds of services
>> that need networking to work have to wait until rc.local is being processed.
>>
>> I am looking for a way to do all this with maybe udev via
>> /etc/udev/rules.d/70-persistent-net.rules and the /etc/network/interfaces
>> file
>> That way all will be running as soon as networking is up and anything after
>> that can run too. I use those two now to make sure all is up-and-running in
>> time for the rest to do their work.
>>
>> Or.... is there a better way?
>
> OK. You're asking "How do I name my interface vlan60 rather than eth0.60"?
That is ONE part of my question.
> I see two ways: Use a bridge device and have br0.60 (that way the .60
> packets/frames can come in on any physical interface) or see if ifrename will
> do what you need.
But can I use that inside the /etc/network/interfaces file or before that?
My idea was to go from:
iface eth0 inet static
address 192.168.178.10
netmask 255.255.255.0
gateway 192.168.178.1
up ip addr add 172.16.17.1/24 dev eth0
down ip addr del 172.16.17.1/24 dev eth0
pre-up /usr/local/bin/firewall.sh
to:
auto eth0
iface eth0 inet static
address 172.16.17.1
netmask 255.255.255.0
auto vlan 100
iface vlan100 inet static
vlan_raw_device eth0
address 192.168.178.10
netmask 255.255.255.0
gateway 192.168.178.1
pre-up /usr/local/bin/firewall.sh
and use eth0 and vlan100 in the firewall script. But even better would be if I
could use something (udev?) to change it to eth-staff and vlan-internet
This is just an example / test environment for me at home. At work this gets
more complicated with more interfaces and more vlans.
Bonno Bloksma
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/89d1798a7351d040b4e74e0a043c69d7352cc...@einexch-01.tio.nl
