* Re: [LARTC] Nano.Txt with PPP
2001-12-18 18:15 [LARTC] Nano.Txt with PPP mok2
@ 2001-12-18 19:00 ` mok2
2001-12-18 19:27 ` mok2
` (6 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: mok2 @ 2001-12-18 19:00 UTC (permalink / raw)
To: lartc
I am not tyring to route outbound traffice through ppp0 just recieve
traffic on that interface.
while still being connected to my cable provider..
and yes i have a dynamic ip on ppp0 and a static for my cable..
i think its duable..
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [LARTC] Nano.Txt with PPP
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
` (5 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: mok2 @ 2001-12-18 19:27 UTC (permalink / raw)
To: lartc
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..
On Tue, 18 Dec 2001, Christoph Simon wrote:
> On Tue, 18 Dec 2001 14:00:06 -0500 (EST)
> mok2 <mok2@armageddonnet.com> wrote:
>
> >
> > I am not tyring to route outbound traffice through ppp0 just recieve
> > traffic on that interface.
> > while still being connected to my cable provider..
> >
> > and yes i have a dynamic ip on ppp0 and a static for my cable..
>
> In that case, I'm not sure to understand your problem. You are not
> going to have any multipath route; it a standard setup.
>
> --
> 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/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [LARTC] Nano.Txt with PPP
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
` (4 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: Christoph Simon @ 2001-12-18 19:39 UTC (permalink / raw)
To: lartc
On Tue, 18 Dec 2001 13:15:45 -0500 (EST)
mok2 <mok2@armageddonnet.com> wrote:
> Abbreviations:
> IFI internal interface
> IPI IP address of internal interface
> NMI netmask for the internal interface
> IFE1, IFE2 external interfaces
> IPE1, IPE2 external IP address
> NWE1, NWE2 external network address
> NME1, NME2 mask for the external network (number of bits, like in /24)
> BRD1, BRD2 broadcast address for external network
> GWE1, GWE2 gateway for external interface
>
> I am tyring to setup a gw with a cable modem and a dialup connection.
> Following the nano.txt, i cant figure out how to define ppp0
>
> ppp0 Link encap:Point-to-Point Protocol
> inet addr:166.50.32.206 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:2 dropped:0 overruns:0 frame:0
> TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
> RX bytes:40 (40.0 b) TX bytes:92 (92.0 b)
>
> since there is no broadcast or network address that i can tell.
>
> what do i put for these variables..
Unfortunately, this isn't such an easy topic that you can just plug
and play, specially when your situation is so much different then mine
was when I wrote it. I mean, you'll have to bother about the setting
of the variables only when it comes to use them. For instance, in
iptables, you wouldn' use the SNAT but rather the MASQUERADE target,
which doesn't require any IP. On the other hand, if you have an
dynamic IP, you will also have to set the routings as soon as the IP
is known, i.e., yafter ou have connected and the provider told you
what's your IP for now. PPP doesn't imply necessarily a dynamic IP,
it's just point-to-point, so I'm not really sure if all this still
makes sense for you, because you'll have to reconfigure your network
anyway as soon as the connection drops. But if you have a static IP,
you do know all of those things. Also, be aware that the use of both
lines requires a big amount of traffic, which I was not able to
generate alone. I just can't imagine how you are going to route heavy
traffic through a dialup line.
--
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/
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [LARTC] Nano.Txt with PPP
2001-12-18 18:15 [LARTC] Nano.Txt with PPP mok2
` (2 preceding siblings ...)
2001-12-18 19:39 ` Christoph Simon
@ 2001-12-18 20:06 ` mok2
2001-12-18 20:14 ` Christoph Simon
` (3 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: mok2 @ 2001-12-18 20:06 UTC (permalink / raw)
To: lartc
On Tue, 18 Dec 2001, Christoph Simon wrote:
> 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.
>
i cannot access 166.50.33.32 from the outside
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [LARTC] Nano.Txt with PPP
2001-12-18 18:15 [LARTC] Nano.Txt with PPP mok2
` (3 preceding siblings ...)
2001-12-18 20:06 ` mok2
@ 2001-12-18 20:14 ` Christoph Simon
2001-12-18 20:21 ` mok2
` (2 subsequent siblings)
7 siblings, 0 replies; 9+ messages in thread
From: Christoph Simon @ 2001-12-18 20:14 UTC (permalink / raw)
To: lartc
On Tue, 18 Dec 2001 14:00:06 -0500 (EST)
mok2 <mok2@armageddonnet.com> wrote:
>
> I am not tyring to route outbound traffice through ppp0 just recieve
> traffic on that interface.
> while still being connected to my cable provider..
>
> and yes i have a dynamic ip on ppp0 and a static for my cable..
In that case, I'm not sure to understand your problem. You are not
going to have any multipath route; it a standard setup.
--
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/
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [LARTC] Nano.Txt with PPP
2001-12-18 18:15 [LARTC] Nano.Txt with PPP mok2
` (4 preceding siblings ...)
2001-12-18 20:14 ` Christoph Simon
@ 2001-12-18 20:21 ` mok2
2001-12-18 20:43 ` Christoph Simon
2001-12-18 21:20 ` Christoph Simon
7 siblings, 0 replies; 9+ messages in thread
From: mok2 @ 2001-12-18 20:21 UTC (permalink / raw)
To: lartc
if i change my default gw to the dialup isp
than it works...
but the cable gw now has a higher metric .. so it wont work now..
i can only use one of the connections at a time .. and the only one that
works with is the connection with the lowest metric..
On Tue, 18 Dec 2001, Christoph Simon wrote:
> On Tue, 18 Dec 2001 15:06:07 -0500 (EST)
> mok2 <mok2@armageddonnet.com> wrote:
>
> > i cannot access 166.50.33.32 from the outside
>
> If you can access it from inside, the problem is at the other end.
>
>
> --
> 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/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [LARTC] Nano.Txt with PPP
2001-12-18 18:15 [LARTC] Nano.Txt with PPP mok2
` (5 preceding siblings ...)
2001-12-18 20:21 ` mok2
@ 2001-12-18 20:43 ` Christoph Simon
2001-12-18 21:20 ` Christoph Simon
7 siblings, 0 replies; 9+ messages in thread
From: Christoph Simon @ 2001-12-18 20:43 UTC (permalink / raw)
To: lartc
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/
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [LARTC] Nano.Txt with PPP
2001-12-18 18:15 [LARTC] Nano.Txt with PPP mok2
` (6 preceding siblings ...)
2001-12-18 20:43 ` Christoph Simon
@ 2001-12-18 21:20 ` Christoph Simon
7 siblings, 0 replies; 9+ messages in thread
From: Christoph Simon @ 2001-12-18 21:20 UTC (permalink / raw)
To: lartc
On Tue, 18 Dec 2001 15:06:07 -0500 (EST)
mok2 <mok2@armageddonnet.com> wrote:
> i cannot access 166.50.33.32 from the outside
If you can access it from inside, the problem is at the other end.
--
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/
^ permalink raw reply [flat|nested] 9+ messages in thread