<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: RE: Cipe and dialup...
From: "Mark Smith" <mark.smith,AT,avcosystems,DOT,co,DOT,uk>
Date: Fri, 27 Sep 2002 10:57:13 +0200
In-reply-to: <20020927081039.GB15661@sv.lnf.it>

Best guess is that the link doesn't know what IP the other end is until it
sends some traffic.  On the end that you established the ssh connection
from, add

ping 30

to the CIPE config file, which will unfortunately maintain the ISDN link
permanently.  Until a packet arrives, the remote end doesn't know the
(perhaps new) IP address that your ISDN connection is now using.  However,
your ping should have done that.  Perhaps it's the other way around, and
your end doesn't know the address of the other end until it sends a packet
back as part of the ssh connection.

I'll admit to being a little confused by your description, but if the remote
is a static IP then you might be able to put something into the ifup script
that causes traffic to be sent over the link, or better, use this to
enable/disable the cipcb interface(s) as well.

Hope, in some way, this helps,

--
Mark Smith - Avco Systems Ltd
email: mark.smith,AT,avcosystems,DOT,co,DOT,uk
Tel: +44 (0)1784 430996 Fax: +44 (0)1784 431078

> -----Original Message-----
> From: owner-cipe-l,AT,inka,DOT,de [mailto:owner-cipe-l,AT,inka,DOT,de 
> Behalf Of
> Marco Gaiarin
> Sent: 27 September 2002 09:11
> To: cipe-l,AT,inka,DOT,de
> Subject: Cipe and dialup...
>
>
>
> I've setup a cipe link via a dialup ISDN linux box (debian).
>
> Note that in isdn linux way of life, isdn syncronous ppp interfaces
> to local provider are ever up, simply if receive some traffic they
> dialup and change ip/peer/defaultroute information.
>
> In this setup there's no way to tear up&down the cipe interfaces, they
> are ever up.
>
>
> But often traffic are destined to a cipe interfaces (say
> cipcb7), and i
> think this fire up key exchange algorithm, that clearly use the ippp0
> interfaces so ISDN goes up.
> But the time (some seconds) are too for key exchange, and the cipe
> interfaces does't work.
> Note that the peer receive some info, they print ``new peer:
> X.Y.Z.W:Q'', but interface does't work.
>
> Another thing.
>
> >From the fixed IP i say:
>
>   gaia:~# ping 10.254.4.10
>   PING 10.254.4.10 (10.254.4.10): 56 data bytes
>   --- 10.254.4.10 ping statistics ---
>   28 packets transmitted, 0 packets received, 100% packet loss
>
> but after ssh-ing into the IP of the last ``new peer'', i can do:
>
>  gaio@ulysses:~$ ping 10.254.10.4
>  PING 10.254.10.4 (10.254.10.4): 56 data bytes
>  64 bytes from 10.254.10.4: icmp_seq=0 ttl=255 time=749.6 ms
>  64 bytes from 10.254.10.4: icmp_seq=1 ttl=255 time=817.0 ms
>  64 bytes from 10.254.10.4: icmp_seq=2 ttl=255 time=1382.5 ms
>
> and then (more, at the same time ;) suddenly:
>
>  gaia:~# ping 10.254.4.10
>  PING 10.254.4.10 (10.254.4.10): 56 data bytes
>  64 bytes from 10.254.4.10: icmp_seq=15 ttl=64 time=757.0 ms
>  64 bytes from 10.254.4.10: icmp_seq=16 ttl=64 time=942.7 ms
>  64 bytes from 10.254.4.10: icmp_seq=17 ttl=64 time=906.5 ms
>  64 bytes from 10.254.4.10: icmp_seq=19 ttl=64 time=1016.9 ms
>  64 bytes from 10.254.4.10: icmp_seq=20 ttl=64 time=817.6 ms
>  64 bytes from 10.254.4.10: icmp_seq=21 ttl=64 time=461.9 ms
>
>
> so seems that in this configuration i can originate traffic (say
> better, i can originate key exchange) only from the dynip side.
>
>
> Can i fiddle with this or is a cipe protocol limitation?!
>
>
> Thanks.
>
> --
> dott. Marco Gaiarin                               GNUPG Key
> ID: 240A3D66
>   Associazione ``La Nostra Famiglia''
http://www.sv.lnf.it/
  Polo FVG  -  Via della Bontà, 7 - 33078  -  San Vito al Tagliamento (PN)
  gaio(at)sv.lnf.it             tel +39-0434-842711    fax +39-0434-842797

                        NO al super tributo alla SIAE!
 http://www.edisport.it/edisport/afdigitale/petizione.nsf/main?openframeset

--
Message sent by the cipe-l,AT,inka,DOT,de mailing list.
Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive:
<URL:http://sites.inka.de/~bigred/devel/cipe.html>





<< | Thread Index | >> ]    [ << | Date Index | >> ]