Hi Tony,
> Any chance of seeing /e/n/i?
>
> My thanks to everyone who helped resolve this question, especially Reco and
> Darjac, who set me on the right path to the solution.
>
> It turned out that indeed having two default routes was a killer, but having
> sorted that, restarting the netw
On 29/03/16 15:42, Darac Marjal wrote:
On Tue, Mar 29, 2016 at 02:10:08PM +0100, Tony van der Hoff wrote:
On 29/03/16 14:00, Brian wrote:
On Tue 29 Mar 2016 at 13:37:19 +0100, Tony van der Hoff wrote:
On 29/03/16 12:58, pedantsunited wrote:
On Tue 29 Mar 2016 at 11:14:56 +0100, Tony van der
On Tue, Mar 29, 2016 at 02:10:08PM +0100, Tony van der Hoff wrote:
On 29/03/16 14:00, Brian wrote:
On Tue 29 Mar 2016 at 13:37:19 +0100, Tony van der Hoff wrote:
On 29/03/16 12:58, pedantsunited wrote:
On Tue 29 Mar 2016 at 11:14:56 +0100, Tony van der Hoff wrote:
Any chance of seeing /e/n/i
On 29/03/16 18:13, Reco wrote:
On Tue, 29 Mar 2016 17:38:07 +0100
Tony van der Hoff wrote:
On 29/03/16 17:20, Reco wrote:
On Tue, 29 Mar 2016 17:08:01 +0100
Tony van der Hoff wrote:
On 29/03/16 16:25, Reco wrote:
Hi.
On Tue, 29 Mar 2016 15:44:16 +0100
Tony van der Hoff wrote:
A
On Tue, 29 Mar 2016 17:38:07 +0100
Tony van der Hoff wrote:
> On 29/03/16 17:20, Reco wrote:
> > On Tue, 29 Mar 2016 17:08:01 +0100
> > Tony van der Hoff wrote:
> >
> >> On 29/03/16 16:25, Reco wrote:
> >>> Hi.
> >>>
> >>> On Tue, 29 Mar 2016 15:44:16 +0100
> >>> Tony van der Hoff wrote:
> >>
2016-03-29 18:08 keltezéssel, Tony van der Hoff írta:
> I guess, if it never goes down, it can never come up
If you modified your /etc/network interfaces when the network was up and
running then you can face similar messages. If you want to modify your
network settings then the proper order is
-
On 29/03/16 17:20, Reco wrote:
On Tue, 29 Mar 2016 17:08:01 +0100
Tony van der Hoff wrote:
On 29/03/16 16:25, Reco wrote:
Hi.
On Tue, 29 Mar 2016 15:44:16 +0100
Tony van der Hoff wrote:
And - you have yet another default gateway for eth1.
No wonder that the kernel refuses to add th
On Tue, 29 Mar 2016 17:08:01 +0100
Tony van der Hoff wrote:
> On 29/03/16 16:25, Reco wrote:
> > Hi.
> >
> > On Tue, 29 Mar 2016 15:44:16 +0100
> > Tony van der Hoff wrote:
> >>> And - you have yet another default gateway for eth1.
> >>> No wonder that the kernel refuses to add the same rout
On 29/03/16 16:25, Reco wrote:
Hi.
On Tue, 29 Mar 2016 15:44:16 +0100
Tony van der Hoff wrote:
And - you have yet another default gateway for eth1.
No wonder that the kernel refuses to add the same route second time.
Reco
Thanks, Reco.
I've now commented out that line for eth1, but
Hi.
On Tue, 29 Mar 2016 15:44:16 +0100
Tony van der Hoff wrote:
> > And - you have yet another default gateway for eth1.
> > No wonder that the kernel refuses to add the same route second time.
> >
> > Reco
> >
>
> Thanks, Reco.
> I've now commented out that line for eth1, but I still ge
On 29/03/16 15:34, Reco wrote:
Hi.
On Tue, Mar 29, 2016 at 02:10:08PM +0100, Tony van der Hoff wrote:
Mar 29 10:15:06 tony-lx networking[21563]: Configuring network
interfaces...RTNETLINK answers: File exists
Mar 29 10:15:06 tony-lx networking[21563]: Failed to bring up eth1.
Mar 29 10
Hi.
On Tue, Mar 29, 2016 at 02:10:08PM +0100, Tony van der Hoff wrote:
>>Mar 29 10:15:06 tony-lx networking[21563]: Configuring network
>>interfaces...RTNETLINK answers: File exists
>>Mar 29 10:15:06 tony-lx networking[21563]: Failed to bring up eth1.
>>Mar 29 10:15:06 tony-lx networking[
On Tue, Mar 29, 2016 at 02:10:08PM +0100, Tony van der Hoff wrote:
> On 29/03/16 14:00, Brian wrote:
> >On Tue 29 Mar 2016 at 13:37:19 +0100, Tony van der Hoff wrote:
> >
> >>On 29/03/16 12:58, pedantsunited wrote:
> >>>On Tue 29 Mar 2016 at 11:14:56 +0100, Tony van der Hoff wrote:
> >>>
> >>>Any c
On 29/03/16 14:00, Brian wrote:
On Tue 29 Mar 2016 at 13:37:19 +0100, Tony van der Hoff wrote:
On 29/03/16 12:58, pedantsunited wrote:
On Tue 29 Mar 2016 at 11:14:56 +0100, Tony van der Hoff wrote:
Any chance of seeing /e/n/i?
Not until you explain what you're talking about
/etc/network/i
On Tue 29 Mar 2016 at 13:37:19 +0100, Tony van der Hoff wrote:
> On 29/03/16 12:58, pedantsunited wrote:
> >On Tue 29 Mar 2016 at 11:14:56 +0100, Tony van der Hoff wrote:
> >
> >Any chance of seeing /e/n/i?
> >
> Not until you explain what you're talking about
/etc/network/interfaces
On 29/03/16 12:58, pedantsunited wrote:
On Tue 29 Mar 2016 at 11:14:56 +0100, Tony van der Hoff wrote:
Any chance of seeing /e/n/i?
Not until you explain what you're talking about
--
Tony van der Hoff| mailto:t...@vanderhoff.org
Buckinghamshire, England |
On Tue 29 Mar 2016 at 11:14:56 +0100, Tony van der Hoff wrote:
> Thanks, everybody for your very helpful replies ;)
>
> It is quite correct that the "deprecated" message has appeared since long
> before systemd. It is also true to say that this message no longer appears
> in Jessie. However, mayb
Hi Tony,
> What is the recommended way of restarting network services after, say,
> changing the parameters in /etc/network/interfaces?
>
> service networking restart doesn't seem to do the job properly.
Although that is the "proper way" I have noticed that other services depending
on specific
On 28/03/16 10:49, Tony van der Hoff wrote:
What is the recommended way of restarting network services after, say,
changing the parameters in /etc/network/interfaces?
service networking restart doesn't seem to do the job properly.
Thanks, everybody for your very helpful replies ;)
It is quit
Debian has the very informative and advisable package debian-reference-en (also
available for some other languages). After installation its contents becomes
available via menu as "Debian reference". Chapter 5, "Network setup" has a lot
of answers dependent on the administrator's choices (which mean
Hi.
On Tue, 29 Mar 2016 08:21:12 +0100
Joe wrote:
> >
> > service networking restart
> >
> > or, if you are also running network-manager, possibly
> >
> > service network-manger restart
> >
> > Very similar to the syntax for /etc/init.d - you're restarting a
> > running service
> >
>
On Mon, 28 Mar 2016 22:01:09 +
"Andrew M.A. Cater" wrote:
> On Tue, Mar 29, 2016 at 08:23:42AM +1100, Andrew McGlashan wrote:
> >
> >
> > On 29/03/2016 12:34 AM, Brian wrote:
> > > On Mon 28 Mar 2016 at 10:49:14 +0100, Tony van der Hoff wrote:
> > >
> > >> What is the recommended way o
On Tue, Mar 29, 2016 at 08:23:42AM +1100, Andrew McGlashan wrote:
>
>
> On 29/03/2016 12:34 AM, Brian wrote:
> > On Mon 28 Mar 2016 at 10:49:14 +0100, Tony van der Hoff wrote:
> >
> >> What is the recommended way of restarting network services after, say,
> >> changing the parameters in /etc/net
On 29/03/2016 12:34 AM, Brian wrote:
> On Mon 28 Mar 2016 at 10:49:14 +0100, Tony van der Hoff wrote:
>
>> What is the recommended way of restarting network services after, say,
>> changing the parameters in /etc/network/interfaces?
>
> Guessing game number 1: No /e/n/i before; no /e/n/i after;
On Mon, 28 Mar 2016 20:07:05 +0100
Brian wrote:
> On Mon 28 Mar 2016 at 19:43:30 +0100, Joe wrote:
>
> > On Mon, 28 Mar 2016 14:34:50 +0100
> > Brian wrote:
> >
> > > On Mon 28 Mar 2016 at 10:49:14 +0100, Tony van der Hoff wrote:
> > >
> > > > What is the recommended way of restarting net
On Mon 28 Mar 2016 at 19:43:30 +0100, Joe wrote:
> On Mon, 28 Mar 2016 14:34:50 +0100
> Brian wrote:
>
> > On Mon 28 Mar 2016 at 10:49:14 +0100, Tony van der Hoff wrote:
> >
> > > What is the recommended way of restarting network services after,
> > > say, changing the parameters in /etc/networ
On Mon, 28 Mar 2016 14:34:50 +0100
Brian wrote:
> On Mon 28 Mar 2016 at 10:49:14 +0100, Tony van der Hoff wrote:
>
> > What is the recommended way of restarting network services after,
> > say, changing the parameters in /etc/network/interfaces?
>
> Guessing game number 1: No /e/n/i before; n
On Mon 28 Mar 2016 at 10:49:14 +0100, Tony van der Hoff wrote:
> What is the recommended way of restarting network services after, say,
> changing the parameters in /etc/network/interfaces?
Guessing game number 1: No /e/n/i before; no /e/n/i after; no indication
of which parameters.
> service ne
On 2011-07-09 16:29:55 +0100, Brian wrote:
> As a matter of observation I notice the booting process pauses when
> /e/n/i uses
>
>auto etho
>iface eth0 inet dhcp
>
> It may only be for 2 or 3 seconds while dhclient does what it has to do
> and outputs its actions to the screen, but it can
On Sat 09 Jul 2011 at 12:20:36 +0300, Andrei POPESCU wrote:
> On Vi, 08 iul 11, 19:25:59, Brian wrote:
> >
> > Booting is quicker with DHCP (especially if dhclient times out) than
> > with auto.
>
> Could you please expand on this? I don't understand what you mean.
As a matter of observation I
On Vi, 08 iul 11, 19:25:59, Brian wrote:
> On Fri 08 Jul 2011 at 11:47:46 +0200, Erwan David wrote:
>
> > Allow-hotplug could be interesting for a removable NIC (PCMCIA,
> > expresscard etc.) But what is the use for a fixed NIC ?
>
> Booting is quicker with DHCP (especially if dhclient times out)
On Fri 08 Jul 2011 at 11:47:46 +0200, Erwan David wrote:
> Allow-hotplug could be interesting for a removable NIC (PCMCIA,
> expresscard etc.) But what is the use for a fixed NIC ?
Booting is quicker with DHCP (especially if dhclient times out) than
with auto.
--
To UNSUBSCRIBE, email to debia
On 07/07/11 22:46, Brian wrote:
On Thu 07 Jul 2011 at 20:45:54 +0100, Joe wrote:
But presumably at boot, all interfaces, whether auto or not, are
successfully started, and presumably properly closed down on shutdown.
When booting, interfaces marked 'auto' are brought up by scripts in
/etc/ini
Le Thu 7/07/2011, Brian disait
> On Thu 07 Jul 2011 at 20:45:54 +0100, Joe wrote:
>
> > But presumably at boot, all interfaces, whether auto or not, are
> > successfully started, and presumably properly closed down on shutdown.
>
> When booting, interfaces marked 'auto' are brought up by scripts
On Thu, 7 Jul 2011 22:46:41 +0100
Brian wrote:
>
> ifup/ifdown will always do what their names imply. You would need to
> have knowledge of the interfaces on your machine to use the commands.
> A sticky-note might help. :)
>
>
> So - some lateral thinking. Mark every interface (apart from lo)
On Jul 7, 2011 4:02 PM, "William Hopkins" wrote:
>
> On 07/07/11 at 11:26am, Wayne Topa wrote:
> > On 07/07/2011 10:42 AM, Tony van der Hoff wrote:
> >
> > Um how about in wheezy or sid
> > service networking stop ; service networking start
>
> Always use && and not ';'; otherwise you may run sta
On Thu 07 Jul 2011 at 20:45:54 +0100, Joe wrote:
> But presumably at boot, all interfaces, whether auto or not, are
> successfully started, and presumably properly closed down on shutdown.
When booting, interfaces marked 'auto' are brought up by scripts in
/etc/init.d. However, interfaces marked
On 07/07/2011 04:02 PM, William Hopkins wrote:
> On 07/07/11 at 11:26am, Wayne Topa wrote:
>> On 07/07/2011 10:42 AM, Tony van der Hoff wrote:
>>> Having made some config changes to my network, I did:
>>>
>>> root@tony-lx:/home/tony# /etc/init.d/networking restart
>>>
>>> That results in:
>>>
>>> R
On 07/07/11 at 11:26am, Wayne Topa wrote:
> On 07/07/2011 10:42 AM, Tony van der Hoff wrote:
> > Having made some config changes to my network, I did:
> >
> > root@tony-lx:/home/tony# /etc/init.d/networking restart
> >
> > That results in:
> >
> > Running /etc/init.d/networking restart is deprec
On Thu, 7 Jul 2011 17:20:05 +0100
Brian wrote:
> On Thu 07 Jul 2011 at 15:42:14 +0100, Tony van der Hoff wrote:
>
> > Having made some config changes to my network, I did:
> >
> > root@tony-lx:/home/tony# /etc/init.d/networking restart
> >
> > That results in:
> >
> > Running /etc/init.d/network
Wayne Topa wrote:
On 07/07/2011 10:42 AM, Tony van der Hoff wrote:
Having made some config changes to my network, I did:
root@tony-lx:/home/tony# /etc/init.d/networking restart
That results in:
Running /etc/init.d/networking restart is deprecated because it may not
enable again some interfac
On Thu 07 Jul 2011 at 15:42:14 +0100, Tony van der Hoff wrote:
> Having made some config changes to my network, I did:
>
> root@tony-lx:/home/tony# /etc/init.d/networking restart
>
> That results in:
>
> Running /etc/init.d/networking restart is deprecated because it may not
> enable again some
On 07/07/2011 10:42 AM, Tony van der Hoff wrote:
> Having made some config changes to my network, I did:
>
> root@tony-lx:/home/tony# /etc/init.d/networking restart
>
> That results in:
>
> Running /etc/init.d/networking restart is deprecated because it may not
> enable again some interfaces ..
On 07/07/11 at 03:42pm, Tony van der Hoff wrote:
> Having made some config changes to my network, I did:
>
> root@tony-lx:/home/tony# /etc/init.d/networking restart
>
> That results in:
>
> Running /etc/init.d/networking restart is deprecated because it may
> not enable again some interfaces ...
On Thu, 07 Jul 2011 15:42:14 +0100, Tony van der Hoff wrote:
> Having made some config changes to my network, I did:
>
> root@tony-lx:/home/tony# /etc/init.d/networking restart
>
> That results in:
>
> Running /etc/init.d/networking restart is deprecated because it may not
> enable again some i
Hi,
On Thu, Jul 08, 2010 at 08:55:43AM +0200, Johann Spies wrote:
> On Wed, Jul 07, 2010 at 12:26:16PM -0600, Bob Proulx wrote:
> > Hint: In the old days interfaces were quite static on systems. But
> > with the coming of removable and hotplug devices such as PCMCIA or USB
> > network interface c
On Wed, Jul 07, 2010 at 12:26:16PM -0600, Bob Proulx wrote:
> Hint: In the old days interfaces were quite static on systems. But
> with the coming of removable and hotplug devices such as PCMCIA or USB
> network interface cards there was a need to move to a more dynamic
> system.
Thanks for you
Johann Spies wrote:
> And I cannot stop my network. The following does not work:
>
> /etc/init.d/networking stop
> service networking stop
I am surprised that /etc/init.d/networking stop doesn't stop the
network. But if you have brought your network up and then changed
your configuration it won'
On Tue, Jul 06, 2010 at 11:45:24PM -, Cameron Hutchison wrote:
> Johann Spies writes:
>
>
> One way is to stop using the long-deprecated interface aliases and
> instead add secondary addresses to the single interface:
>
> iface eth0 inet dhcp
> up ip addr add W.X.Y.Z/N dev $IFACE
>
On Tue, Jul 06, 2010 at 11:45:24PM -, Cameron Hutchison wrote:
> iface eth0 inet dhcp
> up ip addr add W.X.Y.Z/N dev $IFACE
> down ip addr del W.X.Y.Z/N dev $IFACE
>
> That way, you can let ifplugd start eth0, and the above commands will
> add/remove the additional IP address yo
On Tue, 2010-07-06 at 23:45 +, Cameron Hutchison wrote:
> iface eth0 inet dhcp
> up ip addr add W.X.Y.Z/N dev $IFACE
> down ip addr del W.X.Y.Z/N dev $IFACE
Cool - I hadn't realised the $IFACE variable was available there :-)
I see there are others too.
Thanks,
Richard
--
T
Johann Spies writes:
>Apparently '/etc/init.d/networking restart' is depricated. It is not
>doing the job any more on squeeze.
>'/etc/init.d/ifplugd restart' ignores virtual interfaces defined in
>/etc/network/interfaces.
>So how do I get my virtual interfaces active after a reboot or restart
On Tue, Jul 06, 2010 at 05:43:18PM +1000, CaT wrote:
> On Tue, Jul 06, 2010 at 09:15:35AM +0200, Johann Spies wrote:
> > Apparently '/etc/init.d/networking restart' is depricated. It is not
> > doing the job any more on squeeze.
> >
> > '/etc/init.d/ifplugd restart' ignores virtual interfaces de
On Tue, Jul 06, 2010 at 09:15:35AM +0200, Johann Spies wrote:
> Apparently '/etc/init.d/networking restart' is depricated. It is not
> doing the job any more on squeeze.
>
> '/etc/init.d/ifplugd restart' ignores virtual interfaces defined in
> /etc/network/interfaces.
>
> So how do I get my vir
On Tue, 10 Aug 2004 00:10:05 +0200, Paul Maser <[EMAIL PROTECTED]>
wrote:
>Besides rebooting, how do you restart the network connections
>after making changes to /etc/network/interfaces?
>Thanks;
Thanks everyone. Your help is always greatly appreciated.
Paul
--
To UNSUBSCRIBE, email to [EMAIL
David Purton said:
> On Mon, Aug 09, 2004 at 08:01:35PM -0400, Ralph Katz wrote:
>> On 08/09/04 18:10, Paul Maser wrote:
>> >Besides rebooting, how do you restart the network connections
>> >after making changes to /etc/network/interfaces?
>> >Thanks;
>> >
>>
>>
>> Hmm... unlike the other responde
On Mon, 9 Aug 2004, Ralph Katz wrote:
> Hmm... unlike the other responders, I've done this with /sbin/ifup, but
> I'm no expert, just a humble desktop user. Perhaps the experts can shed
> light on the different approaches?
update-rc.d - used to fix (enable/disable) your init servi
On Tue, Aug 10, 2004 at 12:18:04AM +0100, Thomas Adam wrote:
> On Mon, Aug 09, 2004 at 04:09:35PM -0700, Brian Nelson wrote:
>
> > /etc/init.d/networking restart
> >
> > It really only makes sense to use invoke-rc.d from maintainer scripts.
>
> We had this discussion a while back. Truth is, both
On Mon, Aug 09, 2004 at 08:01:35PM -0400, Ralph Katz wrote:
> On 08/09/04 18:10, Paul Maser wrote:
> >Besides rebooting, how do you restart the network connections
> >after making changes to /etc/network/interfaces?
> >Thanks;
> >
>
>
> Hmm... unlike the other responders, I've done this with /sbi
On Mon, Aug 09, 2004 at 08:01:35PM -0400, Ralph Katz wrote:
> Hmm... unlike the other responders, I've done this with /sbin/ifup, but
> I'm no expert, just a humble desktop user. Perhaps the experts can shed
> light on the different approaches?
The script calls if{up,down}.
-- Thomas Adam
--
"
On 08/09/04 18:10, Paul Maser wrote:
Besides rebooting, how do you restart the network connections
after making changes to /etc/network/interfaces?
Thanks;
Hmm... unlike the other responders, I've done this with /sbin/ifup, but
I'm no expert, just a humble desktop user. Perhaps the experts can s
On Mon, Aug 09, 2004 at 04:09:35PM -0700, Brian Nelson wrote:
> /etc/init.d/networking restart
>
> It really only makes sense to use invoke-rc.d from maintainer scripts.
We had this discussion a while back. Truth is, both work just fine.
-- Thomas Adam
--
"Frankly, Mr. Shankly, since you ask. Y
On Mon, Aug 09, 2004 at 04:08:29PM -0600, Monique Y. Mudama wrote:
> On 2004-08-09, Paul Maser penned:
> > Besides rebooting, how do you restart the network connections after
> > making changes to /etc/network/interfaces? Thanks;
>
> invoke-rc.d networking restart
/etc/init.d/networking restart
On 2004-08-09, Paul Maser penned:
> Besides rebooting, how do you restart the network connections after
> making changes to /etc/network/interfaces? Thanks;
invoke-rc.d networking restart
--
monique
Ask smart questions, get good answers:
http://www.catb.org/~esr/faqs/smart-questions.html
--
On Mon, Aug 09, 2004 at 01:35:03PM -0700, Paul Maser wrote:
> Besides rebooting, how do you restart the network connections
> after making changes to /etc/network/interfaces?
> Thanks;
/etc/init.d/networking restart
-- Thomas Adam
--
"Frankly, Mr. Shankly, since you ask. You are a flatulent pain
65 matches
Mail list logo
