Bug#347958: Fails to establish pppoe connection

2006-07-24 Thread Gregory Colpart
On Mon, Jul 24, 2006 at 08:19:53AM +0200, Marco d'Itri wrote:
> 
> > Then, this pppoeconf bug will be closed (or reassign to ppp
> > package if you want) except you have new informations for

> Don't. This behaviour is a feature.

Don't reassign or don't close ?

Regards,
-- 
Gregory Colpart <[EMAIL PROTECTED]>  GnuPG:1024D/C1027A0E
Evolix - Informatique et Logiciels Libres http://www.evolix.fr/


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



Bug#347958: Fails to establish pppoe connection

2006-07-23 Thread Marco d'Itri
On Jul 24, Gregory Colpart <[EMAIL PROTECTED]> wrote:

> Then, this pppoeconf bug will be closed (or reassign to ppp
> package if you want) except you have new informations for
Don't. This behaviour is a feature.

-- 
ciao,
Marco


signature.asc
Description: Digital signature


Bug#347958: Fails to establish pppoe connection

2006-07-23 Thread Gregory Colpart
Hi,

>> Looks like you did not already configure your ethernet
>> connection and pppoeconf is not correctly configuring
>> /etc/network/interfaces to raise eth1 before starting the PPP
>> connections.  I have seen a similar bug in the pppoeconf
>> package in the latest Ubuntu release, but I do not know if
>> this is related. It mangled in some way the interfaces file
>> but I can't remember the details (maybe this was related to
>> eth0 using DHCP).

> auto isp
> iface dsl-provider inet ppp
>pre-up ip link set eth1 up
>provider dsl-provider

This behavior is in last releases of pppoeconf.
This line is added in /etc/network/interfaces :

/sbin/ifconfig $ifacenocomma up # line maintained by pppoeconf


Then, this pppoeconf bug will be closed (or reassign to ppp
package if you want) except you have new informations for
ppoeconf.


Regards,
-- 
Gregory Colpart <[EMAIL PROTECTED]>  GnuPG:1024D/C1027A0E
Evolix - Informatique et Logiciels Libres http://www.evolix.fr/


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



Bug#347958: Fails to establish pppoe connection

2006-01-30 Thread Andreas Tille

On Thu, 19 Jan 2006, Marco d'Itri wrote:


ping 193.175.81.44
---> failed

I do not know what your problem is, but the PPP session is successfully
negotiated and even DNS queries are exachanged. Your pings to
193.175.81.44 are rejected by 193.175.81.253 which is on the same
network, so the PPP link is working.


I tried to observe the problem for about one week now.  I noticed about
20% failures when trying pon to establish a connection.  This is definitely
a ppp problem and I wonder whether I should reassign this bug back because
of the log of our discussion or open a new one.

The real problem is that I can't prove this via tcpdump.  What happens?

   1) User calls "pon dsl-provider".  In about 80% this works fine, but
  in 20% this fails.  Some ppp[0-3] devices are created in addition
  to eth1.
   2) "ping www.debian.org" fails
   3) Try the same as root fails as well
   4) Start "tcpdump -i eth1" and do "pon dsl-provider" as root
  works fine.

So we have some quantum mechanics effect here: If you look at it it works
but if you are not looking it might fail.  Please tell me what I can do
more to track down the problem.

Kind regards

Andreas.

--
http://fam-tille.de


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



Bug#347958: Fails to establish pppoe connection

2006-01-19 Thread Andreas Tille

On Thu, 19 Jan 2006, Marco d'Itri wrote:


On Jan 16, Andreas Tille <[EMAIL PROTECTED]> wrote:


ping 193.175.81.44
---> failed

I do not know what your problem is, but the PPP session is successfully
negotiated and even DNS queries are exachanged. Your pings to
193.175.81.44 are rejected by 193.175.81.253 which is on the same
network, so the PPP link is working.


Well, I have no idea what might be the problem here.  It is a fact that
I can perfectly ping 193.175.81.44 when I'm using the old ppp package
but I can not when I'm using the new package.  Perhaps I should try
to ping www.debian.org - but I have to go to the box in question first.
It was just a random IP adress I'm regularly using ...

Kind regards

 Andreas.

--
http://fam-tille.de


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



Bug#347958: Fails to establish pppoe connection

2006-01-19 Thread Marco d'Itri
On Jan 16, Andreas Tille <[EMAIL PROTECTED]> wrote:

> ping 193.175.81.44
> ---> failed
I do not know what your problem is, but the PPP session is successfully
negotiated and even DNS queries are exachanged. Your pings to
193.175.81.44 are rejected by 193.175.81.253 which is on the same
network, so the PPP link is working.

-- 
ciao,
Marco


signature.asc
Description: Digital signature


Bug#347958: Fails to establish pppoe connection

2006-01-16 Thread Andreas Tille

On Sat, 14 Jan 2006, Marco d'Itri wrote:


The ppp_2.4.4 dump is not clear.
If you will open it in ethereal you will see a first successful PPP
connections, which is not terminated until later (packet 41-42), then
(starting from packet 30) an attempt to estabilish a new connection
which fails because the remote server is not sending back the PADS
packet (because it's already engaged in a PPP session with you?),


Well, that's easy to explain.  From the old modem days I'm using a
/usr/local/bin/pon that basically does

   while ! fping $host > /dev/null 2>/dev/null ; do
  sleep 2
  /usr/bin/pon dsl-provider
   done


and finally a new PPP session is almost estabilished but killed from
your side still in the LCP phase.
Your precedent syslog log shows that there are multiple PPP sessions
started a few seconds after each other, so it looks like something is
wrong with your system.


If this disturbs you I tried after a fresh reboot

# tcpdump -i eth1 -w ppp_2.4.4-2
tcpdump: bind: Network is down
# ifconfig eth1 up
# tcpdump -i eth1 -w ppp_2.4.4-2
tcpdump: WARNING: eth1: no IPv4 address assigned
tcpdump: listening on eth1, link-type EN10MB (Ethernet), capture size 96 bytes

... other xterm
# /usr/bin/pon dsl-provider
Plugin rp-pppoe.so loaded.

   (wait)
ping 193.175.81.44
---> failed

   (back to tcpdump console)

^C
62 packets captured
124 packets received by filter
0 packets dropped by kernel


I attached a tgz containing the tcpdump and ifconfig output.

Please tell me if I can clarify things by further information.  As I
said ppp 2.4.3 works if I just reinstall the old package.

Kind regards

Andreas.

--
http://fam-tille.de

tcpdump-2.tgz
Description: GNU Unix tar archive


Bug#347958: Fails to establish pppoe connection

2006-01-14 Thread Marco d'Itri
On Jan 14, Andreas Tille <[EMAIL PROTECTED]> wrote:

> Attached is the promissed tcpdump output.  Just ask me for further
> infromation.
The ppp_2.4.4 dump is not clear.
If you will open it in ethereal you will see a first successful PPP
connections, which is not terminated until later (packet 41-42), then
(starting from packet 30) an attempt to estabilish a new connection
which fails because the remote server is not sending back the PADS
packet (because it's already engaged in a PPP session with you?),
and finally a new PPP session is almost estabilished but killed from
your side still in the LCP phase.
Your precedent syslog log shows that there are multiple PPP sessions
started a few seconds after each other, so it looks like something is
wrong with your system.

-- 
ciao,
Marco


signature.asc
Description: Digital signature


Bug#347958: Fails to establish pppoe connection

2006-01-14 Thread Andreas Tille

On Sat, 14 Jan 2006, Marco d'Itri wrote:


A detailed log showing what does not work (tcpdump and ppp.log are a
good start).


Attached is the promissed tcpdump output.  Just ask me for further
infromation.

Kind regards

 Andreas.

--
http://fam-tille.de

tcpdump.tgz
Description: GNU Unix tar archive


Bug#347958: Fails to establish pppoe connection

2006-01-14 Thread Andreas Tille

On Sat, 14 Jan 2006, Marco d'Itri wrote:


What further information would you need?

A detailed log showing what does not work (tcpdump and ppp.log are a
good start).


Well, you got the ppp.log in one of my previous mails (from a working
and a non-working version).  I'll prepare tcpdump if this is helpful.

Kind regards

   Andreas.
--
http://fam-tille.de


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



Bug#347958: Fails to establish pppoe connection

2006-01-14 Thread Marco d'Itri
On Jan 14, Andreas Tille <[EMAIL PROTECTED]> wrote:

>2. I can not start pon with 2.4.4 at all
> 
> What further information would you need?
A detailed log showing what does not work (tcpdump and ppp.log are a
good start).

-- 
ciao,
Marco


signature.asc
Description: Digital signature


Bug#347958: Fails to establish pppoe connection

2006-01-14 Thread Andreas Tille

On Sat, 14 Jan 2006, Marco d'Itri wrote:


Well, do you think this is caused by a broken config file?

Yes.


I tried to investigate into it and have to admit that it was *not only*
a broken config file.


Well, my question is quite simple: How can I get a solid working
configuration?


auto isp
iface dsl-provider inet ppp
   pre-up ip link set eth1 up
   provider dsl-provider


Perhaps we have to split this bug, but may be we try to sort out the
situation a little bit first.  If I tell you: Well the situation has
not yet changed with your suggestion (which basically was commenting
out

  #auto eth1
  # iface eth1 inet manual

I observed no change at all:

   1. I have to
ifconfig eth1 up
  before I can start pon successfully using version 2.4.3
   2. I can not start pon with 2.4.4 at all

What further information would you need?

Kind regards

Andreas.
--
http://fam-tille.de


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



Bug#347958: Fails to establish pppoe connection

2006-01-14 Thread Marco d'Itri
On Jan 14, Andreas Tille <[EMAIL PROTECTED]> wrote:

> Well, do you think this is caused by a broken config file?
Yes.

> Well, my question is quite simple: How can I get a solid working
> configuration?

auto isp
iface dsl-provider inet ppp
pre-up ip link set eth1 up
provider dsl-provider

-- 
ciao,
Marco


signature.asc
Description: Digital signature


Bug#347958: Fails to establish pppoe connection

2006-01-14 Thread Andreas Tille

On Sat, 14 Jan 2006, Marco d'Itri wrote:


reassign 347958 pppoeconf


Well, do you think this is caused by a broken config file?


Looks like you did not already configure your ethernet connection and
pppoeconf is not correctly configuring /etc/network/interfaces to raise
eth1 before starting the PPP connections.
I have seen a similar bug in the pppoeconf package in the latest Ubuntu
release, but I do not know if this is related. It mangled in some way
the interfaces file but I can't remember the details (maybe this was
related to eth0 using DHCP).

(FYI, you do not need a second network card to use PPPoE, you can just
connect your modem to your switch.)


That means exactly what?

Well, my question is quite simple: How can I get a solid working
configuration?

I just attached my dsl-provider file to this mail.

I also attached a stripped /var/log/syslog file which contains a first
connection (using the "good old working" ppp package) and in the second
part a failed connection using the latest ppp package.  I would be happy
if you could tell me what might be the problem in pppoeconf that if
I understand you right created an unusable config file - at least unusable
with the latest ppp package.

Kind regards and thanks again for your quick response

   Andreas.

--
http://fam-tille.de# Configuration file for PPP, using PPP over Ethernet 
# to connect to a DSL provider.
#
# See the manual page pppd(8) for information on all the options.

##
# Section 1
#
# Stuff to configure...

# MUST CHANGE: Uncomment the following line, replacing the [EMAIL PROTECTED]
# by the DSL user name given to your by your DSL provider.
# (There should be a matching entry in /etc/ppp/pap-secrets with the password.)
#user [EMAIL PROTECTED]

# Use the pppoe program to send the ppp packets over the Ethernet link
# This line should work fine if this computer is the only one accessing
# the Internet through this DSL connection. This is the right line to use
# for most people.
#pty "/usr/sbin/pppoe -I eth1 -T 80 -m 1452"

# If the computer connected to the Internet using pppoe is not being used
# by other computers as a gateway to the Internet, you can try the following
# line instead, for a small gain in speed:
#pty "/usr/sbin/pppoe -I eth1 -T 80"

# An even more conservative version of the previous line, if things
# don't work using -m 1452... 
#pty "/usr/sbin/pppoe -I eth1 -T 80 -m 1412"


# The following two options should work fine for most DSL users.

# Assumes that your IP address is allocated dynamically
# by your DSL provider...
noipdefault
# Comment out if you already have the correct default route installed
defaultroute

##
# Section 2
#
# Uncomment if your DSL provider charges by minute connected
# and you want to use demand-dialing. 
#
# Disconnect after 300 seconds (5 minutes) of idle time.

#demand
#idle 300

##
# Section 3
#
# You shouldn't need to change these options...

hide-password
lcp-echo-interval 60
lcp-echo-failure 3
# Override any connect script that may have been set in /etc/ppp/options.
connect /bin/true
noauth
persist
mtu 1492


usepeerdns
plugin rp-pppoe.so eth1
user "[EMAIL PROTECTED]"
Jan 14 14:34:52 energija pppd[5181]: Plugin rp-pppoe.so loaded.
Jan 14 14:34:52 energija pppd[5184]: pppd 2.4.3 started by root, uid 0
Jan 14 14:34:52 energija pppd[5184]: Using interface ppp2
Jan 14 14:34:52 energija pppd[5184]: Couldn't increase MTU to 1500
Jan 14 14:34:52 energija pppd[5184]: Couldn't increase MRU to 1500
Jan 14 14:34:52 energija pppd[5184]: not replacing default route to ppp0 
[217.0.116.19]
Jan 14 14:34:52 energija pppd[5184]: Cannot determine ethernet address for 
proxy ARP
Jan 14 14:34:52 energija pppd[5184]: local  IP address 10.64.64.66
Jan 14 14:34:52 energija pppd[5184]: remote IP address 10.112.112.114
Jan 14 14:34:58 energija pppd[5149]: Terminating on signal 15
Jan 14 14:34:58 energija pppd[5149]: Connect time 0.2 minutes.
Jan 14 14:34:58 energija pppd[5149]: Sent 2188 bytes, received 3122 bytes.
Jan 14 14:34:58 energija pppd[5149]: Couldn't increase MTU to 1500
Jan 14 14:34:58 energija pppd[5149]: Couldn't increase MRU to 1500
Jan 14 14:34:58 energija pppd[5155]: Terminating on signal 15
Jan 14 14:34:58 energija pppd[5155]: Exit.
Jan 14 14:34:58 energija pppd[5184]: Terminating on signal 15
Jan 14 14:34:58 energija pppd[5184]: Exit.
Jan 14 14:34:58 energija pppd[5149]: Connection terminated.
Jan 14 14:34:58 energija pppd[5149]: Terminating on signal 15
Jan 14 14:34:58 energija pppd[5149]: Exit.

Jan 14 14:43:40 energija pppd[5995]: Plugin rp-pppoe.so loaded.
Jan 14 14:43:40 energija pppd[5998]: pppd 2.4.4b1 started by root, uid 0
Jan 14 14:43:40 energija pppd[5998]: Using interface ppp0
Jan 14 14:43:40 energija pppd[5998]: Cannot determine ethernet address for 
proxy ARP
Jan 14 14:43:40 energija pppd[5998]: local  IP address 10.64.64.64
Jan 14 14:43:40 energija pppd[5998]: remote IP address 10.112.112.112
Jan 14 14:43:40 energija pppd[5998]: Starting link
Jan 14 14:43:40 energija pppd[5

Bug#347958: Fails to establish pppoe connection

2006-01-14 Thread Marco d'Itri
reassign 347958 pppoeconf
thanks

On Jan 14, Andreas Tille <[EMAIL PROTECTED]> wrote:

> I was able to reduce the help of pppoeconf to the real necessary part.
> If I use
> 
>  ifconfig eth1 up
> 
> before the first
> 
>  pon dsl-provider
> 
> everything works fine.  This is the solution for ppp
> Version: 2.4.3-20050321+1, and is required after a reboot. If I
> stop the connection via poff and retry pon everything works fine.
> This was not necessary before I upgraded to latest testing in the
> beginning of this week - so please consider also an other package

Indeed, old versions of ppp which were in unstable before sarge was
released had a Debian-specific patch which automatically raised the
interface, but I removed this patch because it was an hack and the
upstream maintainer rejected it.

Looks like you did not already configure your ethernet connection and
pppoeconf is not correctly configuring /etc/network/interfaces to raise
eth1 before starting the PPP connections.
I have seen a similar bug in the pppoeconf package in the latest Ubuntu
release, but I do not know if this is related. It mangled in some way
the interfaces file but I can't remember the details (maybe this was
related to eth0 using DHCP).

(FYI, you do not need a second network card to use PPPoE, you can just
connect your modem to your switch.)

-- 
ciao,
Marco


signature.asc
Description: Digital signature


Bug#347958: Fails to establish pppoe connection

2006-01-14 Thread Andreas Tille

On Fri, 13 Jan 2006, Marco d'Itri wrote:


There is nothing I can do unless you can provide useful information


SUre - my problem was, that I was unable to decide what mit be useful.


about why and how pppd does not work (the log may be a good start)
*AND* remove pppoeconf out of the equation (IOW, you must be able to
start the connection with pon "dsl-provider").


I was able to reduce the help of pppoeconf to the real necessary part.
If I use

 ifconfig eth1 up

before the first

 pon dsl-provider

everything works fine.  This is the solution for ppp
Version: 2.4.3-20050321+1, and is required after a reboot. If I
stop the connection via poff and retry pon everything works fine.
This was not necessary before I upgraded to latest testing in the
beginning of this week - so please consider also an other package
that might cuase this problem.


Please also attach /etc/ppp/peers/dsl-provider


I try the new ppp now again whether this solution helps here as well
and come back with more observations.  Thanks for your quick response.

Kind regards

  Andreas.

--
http://fam-tille.de


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



Bug#347958: Fails to establish pppoe connection

2006-01-13 Thread Marco d'Itri
tag 347958 unreproducible moreinfo
unfound 347958 2.4.3-20050321+1
found 347958 2.4.4b1-1
thanks

On Jan 13, Andreas Tille <[EMAIL PROTECTED]> wrote:

> Even beeing a DD myself I have no idea about all this ppp stuff and I'm
> really in vain what to do here.  I'm completely clueless and really
> need some help.
There is nothing I can do unless you can provide useful information
about why and how pppd does not work (the log may be a good start)
*AND* remove pppoeconf out of the equation (IOW, you must be able to
start the connection with pon "dsl-provider").
Please also attach /etc/ppp/peers/dsl-provider

-- 
ciao,
Marco


signature.asc
Description: Digital signature


Bug#347958: Fails to establish pppoe connection

2006-01-13 Thread Andreas Tille
Package: ppp
Version: 2.4.3-20050321+1
Severity: important

Hi,

I'm very sorry hat I'm unable to send this bug report using the ppp
version in question but without a connection it is just hard to send
something.  So please read that this bug is concerned to version 2.4.4b1-1
of the ppp package.  I just grabbed the old package from snapshot.debian.net
to get my network back.

The problem: In the beginn of this week I updated to the latest testing which
included an update of ppp.  After I tried to establish the next pppoe
(ADSL) connection this failed.  I verified the logfiles
(grep ppp /var/log/syslog) and compared these with the output of the
old ppp version but found nor relevant difference here (except the
version number of the pppd daemon).

I tried to reconfigure my setup using pppoeconf which worked for the
first time - but failed immediately after a poff; pon dsl-provider
sequence.  I was not able to get a connection until I rebooted the
next day.  At this day I've got some kind of random connections:  I tried
pon several times and sometimes this worked.  When I switched back to the
old version (see version number in bug report) this also did not worked
out of the box - another pppoeconf was necessary.  I do not really
understand what this script really does.  I never changed my input to
the script and the /etc/ppp directory did not changed after a call.
But now I got my ppp working again - well mostly.  Even when I switched
back to the former ppp version the connection can not be established
relieably after every pon.  Mostly it works after a pppoeconf
(which is kind of annoing because of #334361).  So it might be that
the trouble was not caused by ppp itself but perhaps one of it
dependencies that was moved to testing together with ppp in the
beginning of this week

Even beeing a DD myself I have no idea about all this ppp stuff and I'm
really in vain what to do here.  I'm completely clueless and really
need some help.  I guess you will need some more information and I'm
willing to provide anything that might be necessary.  So feel free to
ask for further information.

Kind regards and thanks for maintaining ppp

   Andreas.

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (499, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.9
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: 
LC_ALL set to [EMAIL PROTECTED])

Versions of packages ppp depends on:
ii  libc6 2.3.5-8GNU C Library: Shared libraries an
ii  libpam-modules0.79-3 Pluggable Authentication Modules f
ii  libpam-runtime0.79-3 Runtime support for the PAM librar
ii  libpam0g  0.79-3 Pluggable Authentication Modules l
ii  libpcap0.70.7.2-7System interface for user-level pa
ii  makedev   2.3.1-79   creates device files in /dev
ii  netbase   4.24   Basic TCP/IP networking system
ii  procps1:3.2.5-1  /proc file system utilities
ii  zlib1g1:1.2.3-9  compression library - runtime

ppp recommends no packages.

-- debconf information:
  ppp/maxfail:


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