Tom H wrote:
...
NM's only controversial because there are people who oppose change not
matter why it might be. ...
So are you lumping people who oppose having things break out from under
them, such as, say, someone installing a new release and finding that
standard Unix(?)/Linux networking com
Bob Proulx wrote:
Tom H wrote:
Dan B. wrote:
...
How does one take an interface down on squeeze?
The expected tool on a GNOME system would be by using the
NetworkManager GUI with the mouse or as Tom writes, 'nmcli' from the
command line. Something like this:
# nmcli conn down id 'Auto et
Tom H writes:
>> [main]
>> plugins=ifupdown,keyfile
>>
>> [ifupdown]
>> managed=false
>>
>> That does mean that ifupdown is not in charge .. right?
>
> No. It means that ifupdown is in charge rather than NM - as long as you
> have the interfaces listed in "/etc/network/interfaces". See my pre
On Mon, 07 Nov 2011 11:28:37 -0500, Tom H wrote:
(...)
> NM's only controversial because there are people who oppose change not
> matter why it might be. The NM developers haven't done themselves any
> favors by not providing server-type features like bonding...
(...)
Just a quick "okay, but...
>> NM's only controversial because there are people who oppose change not
>> matter why it might be. The NM developers haven't done themselves any
>> favors by not providing server-type features like bonding...
No, it's also controversial for other reasons. In my case, I have
issues with it becau
Tom H wrote:
> Bob Proulx wrote:
> > Tom H wrote:
> >> Dan B. wrote:
> >> > On a new installation of squeeze, ifdown no longer works as it used
> >> > to (on my old Debian system).
> >
> > This is because by default with a GNOME desktop installed Debian has
> > switched away from ifupdown and over
On Mon, Nov 7, 2011 at 6:54 AM, Harry Putnam wrote:
> Tom H writes:
>>
>> You can also use "nmcli" to take down and bring up your NIC.
>
> Can you show a usage of bringing up/down the network?
>
> With this in /etc/NetworkManager/NetworkManager.conf
>
> [main]
> plugins=ifupdown,keyfile
>
> [
On Mon, Nov 7, 2011 at 2:17 AM, Bob Proulx wrote:
> Tom H wrote:
>> Dan B. wrote:
>> > On a new installation of squeeze, ifdown no longer works as it used
>> > to (on my old Debian system).
>
> This is because by default with a GNOME desktop installed Debian has
> switched away from ifupdown and o
Tom H writes:
> You can also use "nmcli" to take down and bring up your NIC.
Can you show a usage of bringing up/down the network?
With this in /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false
That does mean that ifupdown is not in cha
Tom H wrote:
> Dan B. wrote:
> > On a new installation of squeeze, ifdown no longer works as it used
> > to (on my old Debian system).
This is because by default with a GNOME desktop installed Debian has
switched away from ifupdown and over to NetworkManager because GNOME
by default specifies Netw
On Sun, Nov 6, 2011 at 8:42 PM, Dan B. wrote:
>
> On a new installation of squeeze, ifdown no longer works as it used
> to (on my old Debian system).
>
> When ifconfig lists an interface "eth0", neither "ifdown eth0" nor
> "ifdown eth" takes the interface down. The attempts yield:
> "ifdown: int
On a new installation of squeeze, ifdown no longer works as it used
to (on my old Debian system).
When ifconfig lists an interface "eth0", neither "ifdown eth0" nor
"ifdown eth" takes the interface down. The attempts yield:
"ifdown: interface eth0 not configured" and
"ifdown: interface eth n
12 matches
Mail list logo
