[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipcop-user
Subject:    Re: [IPCop-user] Strange IPCOP and PPoe connection
From:       Ed Gurski <ed () gurski ! com>
Date:       2009-06-27 20:28:01
Message-ID: 1246134481.3105.4.camel () eagfd01p
[Download RAW message or body]


-  
Ed Gurski

Linux User 
# 458454  http://counter.li.org


On Sat, 2009-06-27 at 16:29 +0000,
ipcop-user-request@lists.sourceforge.net wrote:

> Date: Fri, 26 Jun 2009 23:14:06 +1000
> From: Glen Cunningham <glen@exemail.com.au>
> Subject: Re: [IPCop-user] Strange IPCOP and PPoe connection
> 	failure?????
> To: ipcop-user@lists.sourceforge.net
> Message-ID: <200906262314.07167.glen@exemail.com.au>
> Content-Type: text/plain;  charset="iso-8859-1"
> 
> G'day Ed,
> 
> On Friday 26 June 2009 20:47, Ed Gurski wrote:
> > I have been running IPCop for several years without problems.
> > Religiously apply updates when available, and was completely happy
> > until recently.
> >
> > The configuration: IPcop red connected to Cat5e in wall (Fiber optic
> > so no DSL modem). IPCop green connected to 8-port switch.
> >
> > The Problem:
> >
> > I noticed several weeks ago that I would loose my Red connection and
> > can see through the logs, that IPcop was trying to re-establish the
> > connection. This would occur around 8:30 PM every night until about
> > 11:55 PM, when my connection would be restored.
> >
> > I first thought that it was my ISP doing something strange, like
> > maintenance. So I kept a running diary.
> >
> > Log:
> > Jun 25 21:36:23 eagfw01s ipcop: Starting RED device eth1.
> > Jun 25 21:36:23 eagfw01s ipcop: Dialling ATMC.
> > Jun 25 21:36:23 eagfw01s pppd[6617]: Plugin rp-pppoe.so loaded.
> > Jun 25 21:36:23 eagfw01s pppd[6617]: RP-PPPoE plugin version 3.3
> > compiled against pppd 2.4.2
> > Jun 25 21:36:23 eagfw01s pppd[6618]: pppd 2.4.2 started by root, uid
> > 0 Jun 25 21:36:58 eagfw01s pppd[6618]: Timeout waiting for PADO
> > packets Jun 25 21:36:58 eagfw01s pppd[6618]: Unable to complete PPPoE
> > Discovery Jun 25 21:36:58 eagfw01s pppd[6618]: Exit.
> > Jun 25 21:36:58 eagfw01s red: Connectioncheck: RED fail to connect
> > .........
> > .....
> > .....
> >
> >
> > Now the problem started becoming less predictable, I could run for a
> > few days and then it would start again.
> >
> > Finally last Saturday, I could not keep a connection for more than 2
> > minutes, so I called my ISP. They were very understanding and
> > forwarded my request to their level 2 support. After talking with
> > them, and being assured that there was no maintenance going on, we
> > decided to wait for the next occurrence. At that point, I would
> > connect a Linksys router to determine if it had a problem connecting.
> > If it did, then the problem was on their side, if not then it was my
> > IPCop machine.
> >
> > Well it happened last night after 3 days of continuous connectivity.
> > So, I unplugged my IPCop from the wall, plugged in my Linksys router
> > and was able to connect immediately. Tried unplugging the Linksys
> > router and plugging the IPcop machine but could not connect.
> >
> > I've searched everywhere on my system and could not find anything,
> > searched Wiki for PPoe tweaks, etc.... but still the same problem...
> >
> > Has anyone seen this before or come up with suggestions?
> 
>    Yep, failing network card for RED interface.   Check in IPCop -
>  Status --> Network Status     Look for errors for eth1.  
> My 3Com card shows ....
> eth1      Link encap:Ethernet  HWaddr 00:50:04:6C:40:11  
>           inet addr:1.1.1.1  Bcast:1.1.1.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:4939879 errors:1 dropped:0 overruns:0 frame:1
> 						^----- 1 in 5M is not 
> 						perfect but it will do.
>           TX packets:3088603 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000 
>           RX bytes:1825873746 (1741.2 MB)  TX bytes:255265267 (243.4 MB)
>           Interrupt:10 Base address:0xec00 
> 
> Anyhow, a new RED card should do the trick.
> 
> Cheers
> Glen
> 
> 
> 
> -
Glenn:

Thanks for the info. That is the conclusion I came to after seeing lots
of errors on the NIC.

I could not replace the NIC since it is on-board. So I added another NIC
card and the problem went away. 

BTW: You will need to tell IPCop that your network has changed and in my
case tell it I was using red-green-orange so that it could pick up the
new NIC....

Thanks again



------------------------------------------------------------------------------
_______________________________________________
IPCop-user mailing list
IPCop-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ipcop-user

[prev in list] [next in list] [prev in thread] [next in thread]