Bob Proulx a écrit :
auto eth0
allow-hotplug eth0
iface eth0 inet static
address 192.168.1.42
netmask 255.255.255.0
gateway 192.168.1.1
up ip addr add 192.168.1.43/24 dev eth0 label eth0:0
down ip addr del 192.168.1.43/24 dev eth0 label eth0:0
Pascal Hambourg wrote:
Bob Proulx a écrit :
up ip addr add 192.168.1.43/24 dev eth0 label eth0:0
You don't even need to define a label, unless you want to display the
additional addresses with ifconfig (not needed with ip addr ls).
Right. But so many people use ifconfig that it is
Bob Proulx wrote:
And for the new way:
auto eth0
allow-hotplug eth0
iface eth0 inet static
address 192.168.1.42
netmask 255.255.255.0
gateway 192.168.1.1
iface eth0 inet static
address 192.168.1.43
netmask 255.255.255.0
iface eth0 inet
On Sat, Aug 24, 2013 at 1:34 PM, Bob Proulx b...@proulx.com wrote:
Bob Proulx wrote:
And for the new way:
auto eth0
allow-hotplug eth0
iface eth0 inet static
address 192.168.1.42
netmask 255.255.255.0
gateway 192.168.1.1
iface eth0 inet static
address
Mark Copper wrote:
Bob Proulx wrote:
I thought I would say that while researching my response I fired up a
VM running Wheezy 7 and tried the above. It worked perfectly fine for
me. So definitely the version in Stable Wheezy 7 handles this above
case fine.
I'd go easy on the
On Tue, 20 Aug 2013 18:17:11 -0600, Bob Proulx wrote:
Tom H wrote:
Mark Copper wrote:
Tom H wrote:
Mark Copper wrote:
Previously, my file followed this format for multiple IP addresses on
a single nic like this (cf
https://wiki.debian.org/NetworkConfiguration):
auto eth0 eth0:1
iface
Tom H wrote:
On Tue, 20 Aug 2013 18:17:11 -0600, Bob Proulx wrote:
Tom H wrote:
Mark Copper wrote:
Tom H wrote:
You have allow-hotplug eth0:0 without an iface eth0:0 ... line.
I think the problem was the other way around. It was allow-hotplug
eth0:0 when it should have been eth0:1.
I
On Wed, Aug 21, 2013 at 4:28 PM, Bob Proulx b...@proulx.com wrote:
Tom H wrote:
On Tue, 20 Aug 2013 18:17:11 -0600, Bob Proulx wrote:
Tom H wrote:
Mark Copper wrote:
Tom H wrote:
You have allow-hotplug eth0:0 without an iface eth0:0 ... line.
I think the problem was the other way
On 8/22/13, Mark Copper mcop...@straitcity.com wrote:
As an aside, right there in the networking chapter of the debian
manual under The basic syntax of /etc/network/interfaces is says in
no uncertain terms, **Warning** Do not define duplicates of the
iface stanza for a network interface in
On Mon, 19 Aug 2013 11:15:29 -0500, Mark Copper wrote:
On Mon, Aug 19, 2013 at 10:27 AM, Tom H tomh0...@gmail.com wrote:
On Sun, 18 Aug 2013 20:28:04 -0500, Mark Copper wrote:
With resolvconf package installed and configured for dynamic
generation of /etc/resolv.conf, I was *unable* to get
Mark Copper wrote:
Bob Proulx wrote:
Neither worked after a networking reload/restart.
Just to clarify. You are on the system console. You are not working
over the network to the machine, right? You can restart networking as
you need?
the machine is remote. remote hands are
Tom H wrote:
Mark Copper wrote:
Tom H wrote:
Mark Copper wrote:
Previously, my file followed this format for multiple IP addresses on
a single nic like this (cf
https://wiki.debian.org/NetworkConfiguration):
auto eth0 eth0:1
iface eth0 inet static
address 192.168.1.42
On Sun, 18 Aug 2013 20:28:04 -0500, Mark Copper wrote:
With resolvconf package installed and configured for dynamic
generation of /etc/resolv.conf, I was *unable* to get any non-local
nameservers written into /etc/resolv.conf.
Is /etc/resolv.conf a link?
I tried a dns-nameservers line in
On Sun, Aug 18, 2013 at 9:29 PM, Bob Proulx b...@proulx.com wrote:
Mark Copper wrote:
With resolvconf package installed and configured for dynamic
generation of /etc/resolv.conf, I was *unable* to get any non-local
nameservers written into /etc/resolv.conf.
Works for me. What version of
On Mon, Aug 19, 2013 at 10:27 AM, Tom H tomh0...@gmail.com wrote:
On Sun, 18 Aug 2013 20:28:04 -0500, Mark Copper wrote:
With resolvconf package installed and configured for dynamic
generation of /etc/resolv.conf, I was *unable* to get any non-local
nameservers written into /etc/resolv.conf.
With resolvconf package installed and configured for dynamic
generation of /etc/resolv.conf, I was *unable* to get any non-local
nameservers written into /etc/resolv.conf.
I tried a dns-nameservers line in the /etc/network/interfaces stanza
for the network interface card, and I tried nameserver
Mark Copper wrote:
With resolvconf package installed and configured for dynamic
generation of /etc/resolv.conf, I was *unable* to get any non-local
nameservers written into /etc/resolv.conf.
Works for me. What version of Debian are you using? Stable Wheezy 7?
Other? There have been recent
17 matches
Mail list logo
