On Tue, Jun 28, 2011 at 11:43:39AM +0300, Andrei POPESCU wrote:
...
> IMVHO the static routes part should be moved to ifupdown. How about a
> 'whishlist' bug?
Yah! With new maintainer team, it may be worth it.
But make sure to provide compatible patch. ifupdown package is a bit
involved one :-
On 06/28/11 at 11:43am, Andrei POPESCU wrote:
> On Du, 26 iun 11, 10:53:21, Magicloud Magiclouds wrote:
> $ apt-cache show ifupdown-extra
> ...
>- setup default static routes for interfaces.
> IMVHO the static routes part should be moved to ifupdown. How about a
> 'whishlist' bug?
Seconded.
On Ma, 28 iun 11, 13:16:42, owl...@gmail.com wrote:
[snip]
That's not what the OP was looking for...
Regards,
Andrei
--
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
signature.asc
Description: Digital signature
http://kindlund.wordpress.com/2007/11/19/configuring-multiple-default-routes-in-linux/
or use interfaces file like this
allow-hotplug eth1
iface eth1 inet static
address 192.168.0.2
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
post-up ip route ad
On Du, 26 iun 11, 10:53:21, Magicloud Magiclouds wrote:
> Hi,
> I used to use configuration like "up ip route add 0.0.0.0/0 via
> a.b.c.d dev eth0" in /etc/network/interfaces to do this.
> But today, in debian doc
> (http://www.debian.org/doc/manuals/reference/ch05.en.html 5.5.14), I
> found th
On 06/26/11 at 10:53am, Magicloud Magiclouds wrote:
> Hi,
> I used to use configuration like "up ip route add 0.0.0.0/0 via
> a.b.c.d dev eth0" in /etc/network/interfaces to do this.
I assume this was just an example, but if you really wanted a route to 0.0.0.0
you would use the 'gateway' parame
On Sun, 26 Jun 2011 10:53:21 +0800, Magicloud Magiclouds wrote:
> I used to use configuration like "up ip route add 0.0.0.0/0 via
> a.b.c.d dev eth0" in /etc/network/interfaces to do this.
Is that option not available anymore?
> But today, in debian doc
> (http://www.debian.org/doc/manuals/r
Hi,
I used to use configuration like "up ip route add 0.0.0.0/0 via
a.b.c.d dev eth0" in /etc/network/interfaces to do this.
But today, in debian doc
(http://www.debian.org/doc/manuals/reference/ch05.en.html 5.5.14), I
found that there is a /etc/network/routes to do this. Well, I cannot
find mo
Henry Hollenberg a écrit :
Hey gang,
I added some routes in /etc/network/interfaces:
auto eth0
iface eth0 inet static
address 10.x.y.z
netmask 255.255.255.0
broadcast 10.x.y.255
gateway 10.x.y.1
up /sbin/route add -net 10.a.b.0/16 gw 10.x.y.250
down /sbin/route del -net 10.a.b.0/16 gw 10.x.y.
Hey gang,
I added some routes in /etc/network/interfaces:
auto eth0
iface eth0 inet static
address 10.x.y.z
netmask 255.255.255.0
broadcast 10.x.y.255
gateway 10.x.y.1
up /sbin/route add -net 10.a.b.0/16 gw 10.x.y.250
down /sbin/route del -net 10.a.b.0/16 gw 10.x.y.250
which fails to add any
Kancha . a écrit :
>hi all
>
>
Hi,
>How can i add static route in debian sarge so that it
>is retained even after a reboot.
>
>
You can use the 'up' and 'down' directives in /etc/network/interfaces:
iface lan inet static
address ...
...
up r
hi all
How can i add static route in debian sarge so that it
is retained even after a reboot.
thanks,
kancha
__
Yahoo! Mail - PC Magazine Editors' Choice 2005
http://mail.yahoo.com
--
To UNSUBSCRIBE, email to [EMAIL PROT
> Hi,
>
> How do I configure a static route into the startup scripts / files
> so that the route is set at boot time? I dont think
> /etc/network/interfaces will work for this because none of the
> interfaces on the machine belong to the destination net. Here is
> th
On Fri, Feb 22, 2002 at 08:01:40AM -0600, Jor-el wrote:
> Hi,
>
> How do I configure a static route into the startup scripts / files
> so that the route is set at boot time? I dont think
> /etc/network/interfaces will work for this because none of the interfaces
> on the
Hi,
How do I configure a static route into the startup scripts / files
so that the route is set at boot time? I dont think
/etc/network/interfaces will work for this because none of the interfaces
on the machine belong to the destination net. Here is the config I am
working with :
eth0
15 matches
Mail list logo