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

Subject: RE: suggestions, connecting 2 inconvenient hosts
From: SBNelson,AT,thermeon,DOT,com
Date: Tue, 2 Jul 2002 19:32:34 +0200

On my dial-up (similar situation as you) I use
        /etc/ppp/ip-up.local
and
        /etc/ppp/ip-down.local
to bring the CIPE link up and down.

When my CIPE link goes up, it tells the fixed IP system what my IP address
is.

In your case, 2 would tell 3 what it's IP address is, and everything should
be fine.

> -----Original Message-----
> From: Karl Kleinpaste [SMTP:karl,AT,charcoal,DOT,com
> Sent: Tuesday, July 02, 2002 9:36 AM
> To:   cipe-l,AT,inka,DOT,de
> Subject:      suggestions, connecting 2 inconvenient hosts
> 
> I have 3 machines in use:
> 1 - fixed IP addr, no firewall or gateway.
> 2 - dialup, random IP addr.
> 3 - fixed IP addr behind ipmasq gateway.
> 
> At this time, I connect both 1<->2 and 1<->3 such that 1 has "peer
> 0.0.0.0:port".  2 and 3 make the "active" side of establishing the
> connection, and the world is wonderful, and has been for months.  Fine
> so far.
> 
> Now I need to connect 2 and 3.  The problem is that, as a dialup, the
> line drops every 10 or 12 hours whether I like it or not -- the ISP
> just doesn't allow the line to remain permanently in use, though (as
> it happens) they don't mind the fact that I immediately reconnect and
> so am effectively connected 24x7.
> 
> The problem, of course, is that 2 cannot find 3 on its own at all, and
> the address of 2 changes with each new connection such that 3 will
> have to find it afresh whenever it disappears and comes back.  I use
> dyndns.org for 2, which at least means I can do a DNS query to find
> it.
> 
> What I fear I am stuck with is
> - 2 uses "peer 0.0.0.0:port" so that it is passive with regard to
> connection establishment, and
> - 3 must periodically have its ciped-cb for that link killed and
> restarted in order that a new IP addr be found, because ciped-cb does
> not have any provision for deciding that the remote "real" IP addr has
> changed underneath itself.
> 
> Might anyone have any other possible configuration suggestions?
> Managing kill/restart this way is a grotesque hack at very best.
> 
> --karl
> 
> --
> 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 | >> ]