All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Simon <ciccio@kiosknet.com.br>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Nano.Txt with PPP
Date: Tue, 18 Dec 2001 20:43:55 +0000	[thread overview]
Message-ID: <marc-lartc-100870827802632@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100870317321113@msgid-missing>

On Tue, 18 Dec 2001 14:27:20 -0500 (EST)
mok2 <mok2@armageddonnet.com> wrote:

> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 166.50.32.1     0.0.0.0         255.255.255.255 UH    0      0        0 ppp0
> 176.30.3.192    0.0.0.0         255.255.255.192 U     0      0        0 eth2
> 10.2.2.0        0.0.0.0         255.255.255.0   U     0      0        0 eth0
> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
> 0.0.0.0         176.30.3.193    0.0.0.0         UG    0      0        0 eth2
> 
> eth2      Link encap:Ethernet  HWaddr 
>           inet addr:176.30.3.38  Bcast:176.30.3.255  Mask:255.255.255.192
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:98373 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:116675 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:1015 
>           RX bytes:76086367 (72.5 Mb)  TX bytes:97127829 (92.6 Mb)
> 
> ppp0      Link encap:Point-to-Point Protocol  
>           inet addr:166.50.33.32  P-t-P:166.50.32.1  Mask:255.255.255.255
>           UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
>           RX packets:4 errors:1 dropped:0 overruns:0 frame:0
>           TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 
>           RX bytes:40 (40.0 b)  TX bytes:61 (61.0 b)
> 
> the gw with the lowest metric determines which connection will work.. 
> i cannot add in both gw and make both connections work at the same time..
> 
> that is my problem.. 

If you try to access 166.50.32.1/32, ppp0 will be used. If you try to
access 10.2.2.0/24, eth0 will be used. In all other cases, eth2 will
be used. This should just work. What do you expect to work and
doesn't? BTW, normally there is no explicit route for lo; the kernel
does know how to deal with the loop back.

--
Christoph Simon
ciccio@kiosknet.com.br
---
^X^C
q
quit
:q
^C
end
x
exit
ZZ
^D
?
help
.

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/

  parent reply	other threads:[~2001-12-18 20:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-18 18:15 [LARTC] Nano.Txt with PPP mok2
2001-12-18 19:00 ` mok2
2001-12-18 19:27 ` mok2
2001-12-18 19:39 ` Christoph Simon
2001-12-18 20:06 ` mok2
2001-12-18 20:14 ` Christoph Simon
2001-12-18 20:21 ` mok2
2001-12-18 20:43 ` Christoph Simon [this message]
2001-12-18 21:20 ` Christoph Simon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-100870827802632@msgid-missing \
    --to=ciccio@kiosknet.com.br \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.