Hello

On Wed, Apr 13, 2005 at 08:19:15PM +0200, Robert Kloibhofer wrote:
> Hello
> 
> > 
> > I must summarize what your problem is:
> > * You can connect the two peers.
> > * You can transmit pacakges.
> > * It may break and do not reconnect because a call manager is still
> >   there.
> That's exactly it :-)

Ok, then I have understood what the problem is at least. :)

> In cases i can not reconnect, there is a call manager process left, even
> if there is no other ppp or pptp process (according to 'ps -aux').
> It keeps up preventing new pptp-connections, as long as i don't kill it
> with 'kill -9'.
> according to
> > http://pptpclient.sourceforge.net/howto-diagnosis.phtml
> pptp-servers don't allow 2 connections from one IP. maybe the call
> manager keeps a connection open.

Yes that is true. You can only have one connection per ip.

> > Have you tried to remove the firewall rules, so they are not a problem?
> I'm going to try, next time i get the error.
> 
> > > I have a firewall running, but it is configured to only block
> > > unrequested packages coming in over ppp0.
> > And I assume that ppp0 is your pptp interface, right?
> 
> ppp0 is the connection to the internet.
Ahh! ppp0 is not the pptp ppp connection. We have some misunderstanding
here then.

> eth0 would be the connection to, let's call it, the "modem" (a zyxel
> prestige 600, connected over an ethernet card)
> looks like pptp connects via eth0, i'm not an expert though.
> maybe you can make use of this:
> 
> # route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 172.25.46.47    *               255.255.255.255 UH    0      0        0 ppp0
> 10.0.0.138      10.42.0.1       255.255.255.255 UGH   0      0        0 eth0
> wlan            *               255.255.255.0   U     0      0        0 wlan0
> home            *               255.255.255.0   U     0      0        0 eth1
> 10.42.0.0       *               255.255.0.0     U     0      0        0 eth0
> default         172.25.46.47    0.0.0.0         UG    0      0        0 ppp0
> # lsof -i | grep pptp
> pptp      10720        root    0u  IPv4 228288       TCP 
> 10.42.3.242:38473->10.0.0.138:1723 (ESTABLISHED)
> # ps aux | grep 10720
> root     10720  0.0  0.3  1556  588 ?        S    18:57   0:00 pptp: call 
> manager for 10.0.0.138        --loglevel 0

What do the pptp connection present itself as? ppp1 ?

> -------------
> 
> > Is the following a log where you can not reconnect?
> > 
> > > syslog:
> > > ...
> > > Apr  6 19:28:16 verleihnix pppd[5687]: rcvd [IPCP TermReq id=0x0]
> > > Apr  6 19:28:16 verleihnix pppd[5687]: IPCP terminated by peer
> > > Apr  6 19:28:16 verleihnix pppd[5687]: Connect time 5.0 minutes.
> > > Apr  6 19:28:16 verleihnix pppd[5687]: Sent 11093 bytes, received 16473 
> > > bytes.
> > > Apr  6 19:28:16 verleihnix pppd[5687]: Script /etc/ppp/ip-down started 
> > > (pid 25205)
> > > Apr  6 19:28:16 verleihnix pppd[5687]: sent [IPCP TermAck id=0x0]
> > > Apr  6 19:28:16 verleihnix pppd[5687]: rcvd [LCP TermReq id=0x0]
> > > Apr  6 19:28:16 verleihnix pppd[5687]: LCP terminated by peer
> > > Apr  6 19:28:16 verleihnix pppd[5687]: sent [LCP TermAck id=0x0]
> 
> Right.
> The Log i sent in my first mail was one, where i was NOT able to reconnect.
> Log-messages like this (starting with IPCP terminated by peer etc.) are the 
> only ones
> where this problem occurs.
> I don't know much (or hardly anything ;-) about ppp and pptp internals, but 
> is there some logic
> in it, when i assume that, in this case, the ppp-connection is ended, but
> the ppTp-connection (or whatever) isn't?
> 
> The Log in my second mail (no response etc.) was one example, where i was 
> able to reconnect.

Well I'm trying to scetch how I think it is configured.
You have a ethernet connection to your modem: eth0
You have a ppp connection to internet (ppp0) that is connected through eth0
You have an ethernet connection to your intranet.
You have a wlan connection to your wlan.
You also have a pptp tunnel over ppp (ppp1) that is connected to your ppp
connection (ppp0) that is connected to your eth0

  pptp-ppp1 <-> ppp0 <-> eth0 <-> Internet

The routing goes to ppp0 which is as it should as eth0 is just a "dummy"
ip to be able to configure it.
             
There are however a couple of things that I do not understand.
* Why do you have a gateway to eth0?
* Why don't you allow incoming packets from ppp0. I actually
  think that pptp can require that.

PPTP use two protocols. One udp based protocol for authentication
and one IP (not over udp or tcp, just raw ip) protocol. If you
disallow incoming packets to that you may end up with problems.

However I do not think that is the problem, but it may be.

The call manager should not be for ip 10.42... but I may be
mistaken. As ppp0 is your Internet connection it should be
for that. Maybe it becomes confused because of this.

What NAT rules do you have on this host?

I'm not sure if I can give you more help than this. Maybe the
people upstream can help you more. This may be a problem on a
too low level for me.

Regards,

// Ola

> best regards
> robert
> 
> 
> 

-- 
 --------------------- Ola Lundqvist ---------------------------
/  [EMAIL PROTECTED]                     Annebergsslingan 37      \
|  [EMAIL PROTECTED]                 654 65 KARLSTAD          |
|  +46 (0)54-10 14 30                  +46 (0)70-332 1551       |
|  http://www.opal.dhs.org             UIN/icq: 4912500         |
\  gpg/f.p.: 7090 A92B 18FE 7994 0C36  4FE4 18A1 B1CF 0FE5 3DD9 /
 ---------------------------------------------------------------


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to