mh i've had the same problem. I dont know if my way is really nice but

ifconfig tunX destroy

has done the job

On Apr 20, 2006, at 8:55 PM, Arnaud Bergeron wrote:

On 4/19/06, Brendan Grossman <[EMAIL PROTECTED]> wrote:
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Arnaud Bergeron
Sent: Wednesday, 19 April 2006 9:57 AM
To: misc@openbsd.org
Cc: Brendan Grossman
Subject: Re: pppoe

On Tue, Apr 18, 2006 at 11:52:47AM +0930, Brendan Grossman wrote:
Hi everyone

To bring up a pppoe connection, I use ppp -ddial provider

But how do I take it down?

Also how do I remove old tunx devices?

# ifconfig
tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1492
        inet 219.90.xxx.xxx --> 203.2.124.224 netmask 0xffffffff
        Opened by PID 71830
tun1: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
tun2: flags=8010<POINTOPOINT,MULTICAST> mtu 1500
        inet 219.90.xxx.xxx --> 219.90.174.215 netmask 0xffffffff

What the? How do I get rid of the others? tun0 seems to be
only in use
there.

It seems strange to me that you have this problem because I
once had a setup similar to yours (under 3.4-3.5-3.6) and
never had this problem.
 Maybe you did not do something right, maybe it's a bug but
without showing more info one can only guess.

The info required here would be the version you are running,
your ppp.conf file (sanitized to remove passwords, of course)
and your linkup and linkdown script if they contain anything.

On another topic, if you are running 3.7 or higher, you could
give the in-kernel pppoe a try, unless, of course, you have
already tried and some wierd thing your provider is doing
prevents it from working.

Hi Arnaud,

Running 3.8-stable

# linkup
MYADDR:
 ! sh -c "/sbin/pfctl -e -F all -f /etc/pf.conf"

No linkdown

# ppp.conf
default:
 set log Phase Chat IPCP CCP tun command

 set redial 15 0
 set reconnect 15 10000
This not needed when using -ddial mode.  Trust the defaults.

isp:
 set device "!/usr/sbin/pppoe -i bce0"
 disable acfcomp protocomp
 deny acfcomp
 set mtu max 1492
 set speed sync
This looks good.

 enable lqr
 set lqrperiod 5

 set cd 5
Why set the default explicitly?

 set dial
 set login
Those are not needed with pppoe.

 set timeout 0
This is useless with -ddial, it's ignored.

 set authname [EMAIL PROTECTED]
 set authkey xxxx
 add! default HISADDR
 #enable dns
 enable mssfixup

Cheers
Brendan

From what I know, it is probably set redial and set reconnect that is
causing ppp to attempt a reconnect before the previous connection is
completly closed.  Try removing these and it -MAY- work.  Also, simple
is better, trust the default and specify the minimum configuration
needed for it to work (see my comments above).

Just to nag you a bit more, since your are running 3.8, why don't you
try the in-kernel pppoe, it works great! (unless, you have tried it
and it doesn't or you absolutly want something ppp does)

Arnaud
--
"i think we should rewrite the kernel in java since it has good
support for threads." - Ted Unangst

  • Re: pppoe Karl-Ludwig Reinhard

Reply via email to