Processed: Re: Bug#347958: Fails to establish pppoe connection
Processing commands for [EMAIL PROTECTED]: > reassign 347958 pppoeconf Bug#347958: Fails to establish pppoe connection Bug reassigned from package `ppp' to `pppoeconf'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#347958: Fails to establish pppoe connection
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
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
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
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
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
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
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#332300: marked as done (menu entry in wrong location)
Your message dated Sat, 14 Jan 2006 14:02:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#332300: fixed in aee 2.2.15b-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 5 Oct 2005 17:43:50 + >From [EMAIL PROTECTED] Wed Oct 05 10:43:50 2005 Return-path: <[EMAIL PROTECTED]> Received: from darboux.math.univ-montp2.fr [162.38.126.4] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1ENDIz-iu-00; Wed, 05 Oct 2005 10:43:50 -0700 Received: from yellowpig.yi.org (prt-177.math.univ-montp2.fr [162.38.126.177]) by darboux.math.univ-montp2.fr (Postfix) with ESMTP id A0FEA25C102; Wed, 5 Oct 2005 19:43:18 +0200 (CEST) Received: from seventeen ([127.0.0.1] helo=yellowpig.yi.org ident=mail) by yellowpig.yi.org with smtp (Exim 3.35 #1 (Debian)) id 1ENDIT-0007bJ-00; Wed, 05 Oct 2005 19:43:17 +0200 Received: (nullmailer pid 29219 invoked by uid 1000); Wed, 05 Oct 2005 17:43:11 - Date: Wed, 5 Oct 2005 19:43:11 +0200 From: Bill Allombert <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: menu entry in wrong location Message-ID: <[EMAIL PROTECTED]> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Reportbug-Version: 3.17 User-Agent: Mutt/1.5.11 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 Package: aee Version: 2.2.15b-1 Severity: normal Hello Javier, aee menu entry is shipped as /usr/lib/menu/aee/menu. You might be interested to know that menu will ignore it completly, since it does not search for menu entries in subdirectories of /usr/lib/menu. The proper location for the menu entry is the file /usr/share/menu/aee. Please always check your menu entry work before uploading the package. Cheers, -- Bill. <[EMAIL PROTECTED]> Imagine a large red swirl here. --- Received: (at 332300-close) by bugs.debian.org; 14 Jan 2006 22:11:16 + >From [EMAIL PROTECTED] Sat Jan 14 14:11:16 2006 Return-path: <[EMAIL PROTECTED]> Received: from katie by spohr.debian.org with local (Exim 4.50) id 1ExtTP-df-Pj; Sat, 14 Jan 2006 14:02:11 -0800 From: Mario Iseli <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.65 $ Subject: Bug#332300: fixed in aee 2.2.15b-3 Message-Id: <[EMAIL PROTECTED]> Sender: Archive Administrator <[EMAIL PROTECTED]> Date: Sat, 14 Jan 2006 14:02:11 -0800 X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 Source: aee Source-Version: 2.2.15b-3 We believe that the bug you reported is fixed in the latest version of aee, which is due to be installed in the Debian FTP archive: aee_2.2.15b-3.diff.gz to pool/main/a/aee/aee_2.2.15b-3.diff.gz aee_2.2.15b-3.dsc to pool/main/a/aee/aee_2.2.15b-3.dsc aee_2.2.15b-3_i386.deb to pool/main/a/aee/aee_2.2.15b-3_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mario Iseli <[EMAIL PROTECTED]> (supplier of updated aee package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 14 Jan 2006 21:13:09 +0100 Source: aee Binary: aee Architecture: source i386 Version: 2.2.15b-3 Distribution: unstable Urgency: high Maintainer: Mario Iseli <[EMAIL PROTECTED]> Changed-By: Mario Iseli <[EMAIL PROTECTED]> Description: aee- An easy to use screen-based editor Closes: 87827 111812 111860 111871 153818 216271 217666 332300 332300 346612 346612 347736 Changes: aee (2.2.15b-3) unstable; urgency=low . * New Maintainer (Closes: #347736) * Policy-Update (3.6.2) * Complete new deb
Bug#346612: marked as done (aee: FTBFS: build-depends on removed xlibs-dev)
Your message dated Sat, 14 Jan 2006 14:02:11 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#346612: fixed in aee 2.2.15b-3 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at maintonly) by bugs.debian.org; 9 Jan 2006 01:38:02 + >From [EMAIL PROTECTED] Sun Jan 08 17:38:02 2006 Return-path: <[EMAIL PROTECTED]> Received: from 84-120-75-62.onocable.ono.com ([84.120.75.62] helo=chistera.yi.org) by spohr.debian.org with esmtp (Exim 4.50) id 1Evlyz-lI-NC for [EMAIL PROTECTED]; Sun, 08 Jan 2006 17:38:01 -0800 Received: from userid 1000 by chistera.yi.org with local (Exim 4.60) id 1Evlyy-0006iA-H5 for [EMAIL PROTECTED]; Mon, 09 Jan 2006 02:38:00 +0100 From: Adeodato =?utf-8?B?U2ltw7M=?= <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: aee: FTBFS: build-depends on removed xlibs-dev Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit Message-Id: <[EMAIL PROTECTED]> Date: Mon, 09 Jan 2006 02:38:00 +0100 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 Package: aee Version: 2.2.15b-1 Severity: serious Hello, This is a serious bug filed against your package because it build-depends on xlibs-dev, which as announced in [1] a while ago, is no longer available in sid. This makes your package fail to build from source. [1] http://lists.debian.org/debian-devel-announce/2005/11/msg00022.html To fix this bug, you need to update your build-dependencies and substitute xlibs-dev for the list of individual X development libraries that your package needs to be built. You can find detailed information about how to do that in the DependsXlibsDev wiki page [2]. [2] http://wiki.debian.org/DependsXlibsDev As indicated by the Release Team [3], the full transition from XFree86 to Xorg is a release blocker for Etch, which means that Etch will not be released until this bug is fixed (or your package removed from testing). So, please, try to fix in a timely manner. [3] http://lists.debian.org/debian-devel-announce/2005/10/msg4.html The number of affected packages by the xlibs-dev transition is huge, so if you feel like helping with patches or uploads, feel free to follow the instructions contained in the wiki page above. A list of affected packages can be found here [4]. [4] http://people.debian.org/~adeodato/release-usertag/transition-xlibs-dev Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your collaboration! -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org --- Received: (at 346612-close) by bugs.debian.org; 14 Jan 2006 22:11:31 + >From [EMAIL PROTECTED] Sat Jan 14 14:11:31 2006 Return-path: <[EMAIL PROTECTED]> Received: from katie by spohr.debian.org with local (Exim 4.50) id 1ExtTP-dh-Qh; Sat, 14 Jan 2006 14:02:11 -0800 From: Mario Iseli <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.65 $ Subject: Bug#346612: fixed in aee 2.2.15b-3 Message-Id: <[EMAIL PROTECTED]> Sender: Archive Administrator <[EMAIL PROTECTED]> Date: Sat, 14 Jan 2006 14:02:11 -0800 X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-CrossAssassin-Score: 2 Source: aee Source-Version: 2.2.15b-3 We believe that the bug you reported is fixed in the latest version of aee, which is due to be installed in the Debian FTP archive: aee_2.2.15b-3.diff.gz to pool/main/a/aee/aee_2.2.15b-3.diff.gz aee_2.2.15b-3.dsc to pool/main/a/aee/aee_2.2.15b-3.dsc aee_2.2.15b-3_i386.deb to pool/main/a/aee/aee_2.2.15b-3_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed.
Processed: your mail
Processing commands for [EMAIL PROTECTED]: > reassign 254373 dosemu Bug#254373: dosemu-freedos: need to include FreeCOM for cvs (and future) dosemu Bug reassigned from package `dosemu-freedos' to `dosemu'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: your mail
Processing commands for [EMAIL PROTECTED]: > reassign 274587 dosemu Bug#274587: dosemu-freedos: Add note about CDROM usage Bug reassigned from package `dosemu-freedos' to `dosemu'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
