Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 17 Feb 1999 13:40:12 -0500 (EST)
From:      tom@tomqnx.com (Tom Torrance at home)
To:        brian@Awfulhak.org (Brian Somers)
Cc:        tom@tomqnx.com, hackers@freebsd.org, brian@awfulhak.org
Subject:   Re: PPP Problem
Message-ID:  <m10DBtM-000I33C@TomQNX.tomqnx.com>
In-Reply-To: <199902170743.HAA37802@keep.lan.Awfulhak.org> from Brian Somers at "Feb 17, 1999  7:43:38 am"

next in thread | previous in thread | raw e-mail | index | archive | help

[-- Attachment #1 --]
I have not been able to duplicate the behaviour- perhaps that is true.

BUT there are several things I find do not work properly when using
ppp over TCP.  Perhaps you could set me straight, but... 

1)	I would expect that with enable lqr and accept lqr, if the
other side disappears (no response to 5 polls) I would expect the 
tunX connection to be torn down, and ppp.linkdown processed, and the
ppp job to terminate. NONE of this seems to happen.

2)	"ppp -direct loop-in" ignores a "kill -TERM xxx". This does
not seem correct. How can ppp.linkdown ever be processed?

3)	Granted that you can compensate in the routing table, the
netmask configuration for the tunnel device seems incorrect. It is
always set to the default for the IP. I would expect that if a
netmask is supplied in the "set ifaddr" command, that would be used
in setting up the tunnel configuration.

4)	After a connection is set up, the named running on the
client starts to cough:
named: bind(dfd=24, [10.0.1.1].53): Permission denied
named: deleting interface [10.0.1.1].53
This seems to be a harmless peculiarity of the new bind (The old 
one on the server doesn't do it) that I could eliminate by defining
the IPs in my zone (or live with it).

5)	Pinging the host side of the tunnel takes 5 times as long
as when I ping an ethernet interface. Setting up a route for that IP
to 127.0.0.1 fixes this. Would it not be a good idea for ppp to
set this up automatically?

Would you be kind enough to set me straight where required on the above?
The docs are full of helpful hints/examples, but a tad short on 
specification as to how it "should" work:-) 

Regards,
Tom

> You must have a ``delete 0'' (same as ``delete 0.0.0.0'' or ``delete 
> default'') somewhere.
> 
> > Running 2.2-stable with user-ppp.
> > 
> > I set up a test PPP link, tunneling PPP over TCP.
> > I do not run routed or gated. The PPP server (-direct) is located
> > on my LAN gateway machine, which has my ISPs router
> > defined as its gateway. There are no definitions in 
> > ppp.conf, ppp.linkup or ppp.linkdown that refer in any
> > way to the 0.0.0.0/0 default definition.
> > 
> > The client machine does have 0.0.0.0 as the 4th parameter to
> > its set ifaddr command, which may contribute to the symptoms
> > in some way. I'll try removing that next...
> > 
> > Shortly after or when the link is made, the ppp program removes
> > the default definition from the server's routing tables. So far
> > I tried removing all references to HISADDR, MYADDR and disabling
> > sroutes - nothing helped.
> > 
> > Regards,
> > Tom
> 
> -- 
> Brian <brian@Awfulhak.org> <brian@FreeBSD.org> <brian@OpenBSD.org>
>       <http://www.Awfulhak.org>;
> Don't _EVER_ lose your sense of humour !
> 
> 
> 


[-- Attachment #2 --]
default:
	set timeout 0
	set lqrperiod 10
	set log Phase Chat Connect LCP IPCP Command
	disable sroutes
	enable lqr
	accept lqr

loop:
	set device mailx:ppploop
	set dial
	set login
	set authname xxxx
	set authkey yyyyy
	set ifaddr 10.0.1.1/24 10.0.1.2/24 255.255.255.0 0.0.0.0

loop-in:
	enable chap
	allow mode direct
	set ifaddr 10.0.1.2 10.0.1.1 255.255.255.0 
	set server /var/tmp/patbsd "" 0177

dial-in:
	enable chap
	allow mode direct
	set ifaddr 10.0.2.2 10.0.2.1 255.255.255.0
	set server /var/tmp/dialppp "" 0177

sloop:
	load loop
	set device !/etc/ppp/secure




[-- Attachment #3 --]
10.0.1.1:
	add 10.0.1.0/24 10.0.1.2
#	add 205.150.43.0/24 10.0.1.2

10.0.1.2:
	add 10.0.1.0/24 10.0.1.1
	add 159.249.0.0/16 10.0.1.1

10.0.2.1:
	add 10.0.2.0/24 10.0.2.2
	add 205.150.43.0/24 10.0.2.2

10.0.2.2:
	add 10.0.2.0/24 10.0.2.1


[-- Attachment #4 --]
10.0.2.1:
#	delete 205.150.43.0/24

10.0.1.2:
	delete 10.0.1.0/24
	delete 159.249.0.0/16

10.0.2.1:
	delete 10.0.2.0/24
#	delete 205.150.43.0/24

10.0.2.2:
	delete 10.0.2.0/24


Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m10DBtM-000I33C>