Chris Davies wrote:
> Bonno Bloksma wrote:
> > I routinely add or remove ip addresses from an interface without having
> > to bring the physical interface up or down.
>
> Me too. (Well, not routinely, but quite comfortably. It's very convenient
> when needing to talk to a new device that's got a d
Bonno Bloksma wrote:
> I routinely add or remove ip addresses from an interface without having
> to bring the physical interface up or down.
Me too. (Well, not routinely, but quite comfortably. It's very convenient
when needing to talk to a new device that's got a default initial address
on a com
On Tue, Oct 22, 2013 at 12:28 PM, Bonno Bloksma wrote:
>
> allow-auto eth0.9
> iface eth0.9 inet static
> address 192.168.1.119
> netmask 255.255.255.0
> gateway 192.168.1.1
> post-up ip address add 192.168.1.199/24 dev eth0.9
>>>
>>> What I use is:
>>> -=-=-=-=
Hi Chris,
> Bob Proulx wrote:
>> Tom H wrote:
>>> I'm pretty sure that the last time (six months ago?) Bob linked to a
>>> Debian wiki page [...] that used multiple iface declarations for the
>>> same nic (I've also used multiple declarations).
>
>>
>> https://wiki.debian.org/NetworkConfigura
Hi,
allow-auto eth0.9
iface eth0.9 inet static
address 192.168.1.119
netmask 255.255.255.0
gateway 192.168.1.1
post-up ip address add 192.168.1.199/24 dev eth0.9
>>
>> What I use is:
>> -=-=-=-=-=-
>> auto eth0
>> iface eth0 inet static
>> address 172.
Bob Proulx wrote:
> Tom H wrote:
>> I'm pretty sure that the last time (six months ago?) Bob linked to a
>> Debian wiki page [...] that used multiple iface declarations for the
>> same nic (I've also used multiple declarations).
>
> https://wiki.debian.org/NetworkConfiguration#Multiple_IP_addre
On Mon, Oct 21, 2013 at 7:29 AM, Bonno Bloksma wrote:
>>>
>>> allow-auto eth0.9
>>> iface eth0.9 inet static
>>> address 192.168.1.119
>>> netmask 255.255.255.0
>>> gateway 192.168.1.1
>>> post-up ip address add 192.168.1.199/24 dev eth0.9
>
> What I use is:
> -=-=-=-=-=-
> auto eth0
> ifa
Hi Steffen,
>> allow-auto eth0.9
>> iface eth0.9 inet static
>> address 192.168.1.119
>> netmask 255.255.255.0
>> gateway 192.168.1.1
>> post-up ip address add 192.168.1.199/24 dev eth0.9
What I use is:
-=-=-=-=-=-
auto eth0
iface eth0 inet static
address 172.16.17.1
netma
On Fri, Oct 18, 2013 at 4:11 PM, Steffen Dettmer
wrote:
> On Fri, Oct 18, 2013 at 3:24 PM, Tom H wrote:
>>> allow-auto eth0.9
>>> iface eth0.9 inet static
>>> address 192.168.1.119
>>> netmask 255.255.255.0
>>> gateway 192.168.1.1
>>> post-up ip address add 192.168.1.199/24 dev eth0.9
>
On Fri, Oct 18, 2013 at 4:03 PM, Steffen Dettmer
wrote:
> On Fri, Oct 18, 2013 at 3:24 PM, Tom H wrote:
>>> I'm using Wheezy with ifup version 0.7.8, I think this is the
>>> latest officially released (aka "the best") one?
>>
>> Strange. I was under the impression that Debian 7's ifupdown is us
Tom H wrote:
> Chris Davies wrote:
> > Tom H wrote:
> >> iface eth3.77 inet static
> >> address 10.0.5.15
> >
> >> iface eth3.77 inet static
> >> address 10.0.5.16
> >
> > The Debian documentation at
> > http://www.debian.org/doc/manuals/debian-reference/ch05.en.html states
> > categorically, « Do
Steffen Dettmer wrote:
> Bob Proulx wrote:
> > However all of the docs I see just now suggest using a bridge.
>
> There are docs recommending to take the burden of kernel software
> briding to add an alias IP?!
But you were asking about VLANS not IP aliases!
Not wanting to distract from the disc
Miles Fidelman wrote:
> for what it's worth, my (working, for years) /etc/network/interfaces
> file looks like this:
In addition to what Tom said, you have redundant network and broadcast
statements. If you specify the netmask then the network and broadcast
will be calculated from the netmask.
B
Tom H wrote:
> Bob Proulx wrote:
> > Of course I know nothing about vlan configuration so I am likely wrong
> > here. I just know that visually it doesn't match. However all of the
> > docs I see just now suggest using a bridge. Perhaps something like this.
> >
> > auto eth0
> > allow-hotplu
On Fri, Oct 18, 2013 at 3:24 PM, Tom H wrote:
>> --->8===
>> auto lo
>> iface lo inet loopback
>>
>> allow-auto eth0.9
>> iface eth0.9 inet static
>> address 192.168.1.119
>> netmask 255.255.255.0
>> gateway 192.168.1.1
>>
Hi!
On Fri, Oct 18, 2013 at 3:24 PM, Tom H wrote:
>> I'm using Wheezy with ifup version 0.7.8, I think this is the
>> latest officially released (aka "the best") one?
>
> Strange. I was under the impression that Debian 7's ifupdown is using
> iproute but you had a vconfig error in an earlier emai
On Fri, Oct 18, 2013 at 2:30 PM, Miles Fidelman
wrote:
> Tom H wrote:
>> On Fri, Oct 18, 2013 at 12:35 PM, Miles Fidelman
>> wrote:
>>
>> eth0:1 is an alias.
>>
> ummm... no, eth0:1 is a virtual interface riding on top of a physical one
> (eth0 being the physical interface).
The OP's asking abou
Tom H wrote:
On Fri, Oct 18, 2013 at 12:35 PM, Miles Fidelman
wrote:
Steffen Dettmer wrote:
I'd like to configure multiple IP addresses to a VLAN tagged interface. I
tried
auto eth3.107
iface eth3.77 inet static
address 10.0.5.15
netmask 255.255.255.0
iface eth3.77 inet static
On Fri, Oct 18, 2013 at 12:35 PM, Miles Fidelman
wrote:
> Steffen Dettmer wrote:
>>
>> I'd like to configure multiple IP addresses to a VLAN tagged interface. I
>> tried
>>
>> auto eth3.107
>>iface eth3.77 inet static
>>address 10.0.5.15
>>netmask 255.255.255.0
>>iface eth3.77 inet
On Fri, Oct 18, 2013 at 11:36 AM, Chris Davies wrote:
> Tom H wrote:
>> iface eth3.77 inet static
>> address 10.0.5.15
>
>> iface eth3.77 inet static
>> address 10.0.5.16
>
> The Debian documentation at
> http://www.debian.org/doc/manuals/debian-reference/ch05.en.html states
> categorically, « Do
On Fri, Oct 18, 2013 at 12:05 PM, Steffen Dettmer
wrote:
> On Fri, Oct 18, 2013 at 1:18 PM, Tom H wrote:
> thanks again for your fast help.
You're welcome.
>> So Bob must be right about your ifupdown version not using iproute
>
> I'm using Wheezy with ifup version 0.7.8, I think this is the
Hi,
just in case someone still reading my boring DHCP client attempts, to
complete the topic here my findings about behavior at shutdown. Even
with simply /etc/network/interfaces configuration:
allow-hotplug eth3.77
iface eth3.77 inet dhcp
and manually starting "ifup eth3.77" after boot, on
Steffen Dettmer wrote:
Hi,
I'd like to configure multiple IP addresses to a VLAN tagged interface. I tried
auto eth3.107
iface eth3.77 inet static
address 10.0.5.15
netmask 255.255.255.0
iface eth3.77 inet static
address 10.0.5.16
netmask 255.255.255.0
but I get an error mess
Tom H wrote:
> iface eth3.77 inet static
> address 10.0.5.15
> iface eth3.77 inet static
> address 10.0.5.16
The Debian documentation at
http://www.debian.org/doc/manuals/debian-reference/ch05.en.html states
categorically, « Do not define duplicates of the "iface" stanza for a
network interface
On Fri, Oct 18, 2013 at 9:49 AM, Steffen Dettmer
wrote:
> On Fri, Oct 18, 2013 at 9:53 AM, Tom H wrote:
>>>
>>> auto eth0
>>> iface eth0 inet static
>>> address 10.0.5.16
>>> netmask 255.255.255.0
>>> iface eth0.77 inet manual
>>> auto br0.77
>>> iface br0.77 inet ma
Hi,
thanks again for your fast help.
On Fri, Oct 18, 2013 at 1:18 PM, Tom H wrote:
> So Bob must be right about your ifupdown version not using iproute
I'm using Wheezy with ifup version 0.7.8, I think this is the
latest officially released (aka "the best") one?
> and, as he suggested, you're
On Fri, Oct 18, 2013 at 5:33 AM, Steffen Dettmer
wrote:
> On Fri, Oct 18, 2013 at 9:40 AM, Tom H wrote:
>>
>> works for me in the form of
>>
>> allow-auto eth0.9
>>
>> iface eth0.9 inet static
>> address 192.168.1.119
>> netmask 255.255.255.0
>> gateway 192.168.1.1
>>
>> iface eth0.9 inet static
On Fri, Oct 18, 2013 at 9:53 AM, Tom H wrote:
>> auto eth0
>> iface eth0 inet static
>> address 10.0.5.16
>> netmask 255.255.255.0
>> iface eth0.77 inet manual
>> auto br0.77
>> iface br0.77 inet manual
>> bridge_ports eth0.77
>> bridge_fd 0
>>
Hi!
On Thu, Oct 17, 2013 at 11:39 PM, Bob Proulx wrote:
> Steffen Dettmer wrote:
> However all of the docs I see just now suggest using a bridge.
There are docs recommending to take the burden of kernel software
briding to add an alias IP?!
> Configuring multiple IP addresses on interfaces like
On Fri, Oct 18, 2013 at 9:40 AM, Tom H wrote:
> On Thu, Oct 17, 2013 at 12:57 PM, Steffen Dettmer
> wrote:
>> but I get an error message that ifup tries to configure the VLAN
>> interface twice, but the addresses are set.
> I assume that you mean "auto eth3.77" not "auto eth3.107".
Yes, of cours
On Thu, Oct 17, 2013 at 5:39 PM, Bob Proulx wrote:
> Steffen Dettmer wrote:
>>
>> I'd like to configure multiple IP addresses to a VLAN tagged
>> interface. I tried
>>
>> auto eth3.107
>> iface eth3.77 inet static
>> address 10.0.5.15
>> netmask 255.255.255.0
>> iface eth3.77 inet static
>
On Thu, Oct 17, 2013 at 12:57 PM, Steffen Dettmer
wrote:
>
> I'd like to configure multiple IP addresses to a VLAN tagged interface. I
> tried
>
> auto eth3.107
> iface eth3.77 inet static
> address 10.0.5.15
> netmask 255.255.255.0
> iface eth3.77 inet static
> address 10.0.5.16
> ne
Steffen Dettmer wrote:
> I'd like to configure multiple IP addresses to a VLAN tagged
> interface. I tried
I am not a vlan expert. But...
> auto eth3.107
> iface eth3.77 inet static
> address 10.0.5.15
> netmask 255.255.255.0
> iface eth3.77 inet static
> address 10.0.5.16
> netmask
33 matches
Mail list logo
