News: This forum is now permanently frozen.
Pages: [1]
Topic: AT&T PPPoE appears unstable  (Read 1878 times)
« on: December 06, 2008, 16:32:04 »
hatrickwah *
Posts: 4

I've been running a m0n0wall router in my bar for sometime now, 3/4 years, and I recently built an all new system running m0n0wall 1.3b15.  I had an earlier version of 1.3 installed in June on an older system, but that one has apparently died.  I manage the site remotely since I'm in one state and the router is in another.  We just started running this new router on Monday, and yesterday the system appeared to lock up.  When I looked at the logs, everything was fine after the restart, but then a few hours later the logs looked as follows:

Dec 5 17:14:56    mpd: [pppoe] LCP: no reply to 1 echo request(s)
Dec 5 17:14:56    mpd: [pppoe] LCP: no reply to 2 echo request(s)
Dec 5 17:15:06    mpd: [pppoe] LCP: no reply to 3 echo request(s)
Dec 5 17:15:16    mpd: [pppoe] LCP: no reply to 4 echo request(s)
Dec 5 18:33:27    mpd: [pppoe] LCP: no reply to 1 echo request(s)
Dec 5 18:33:37    mpd: [pppoe] LCP: no reply to 2 echo request(s)
Dec 5 18:51:37    mpd: [pppoe] LCP: no reply to 1 echo request(s)
Dec 5 19:05:17    mpd: [pppoe] LCP: no reply to 1 echo request(s)
Dec 5 19:05:17    mpd: [pppoe] LCP: no reply to 2 echo request(s)
Dec 5 19:18:07    mpd: [pppoe] LCP: no reply to 1 echo request(s)
Dec 5 19:23:17    mpd: [pppoe] LCP: no reply to 1 echo request(s)
Dec 5 19:23:17    mpd: [pppoe] LCP: no reply to 2 echo request(s)
Dec 5 19:52:17    mpd: [pppoe] LCP: no reply to 1 echo request(s)
Dec 5 20:57:02    kernel: arplookup 169.254.177.21 failed: host is not on local network
Dec 5 21:08:47    mpd: [pppoe] LCP: no reply to 1 echo request(s)
Dec 5 21:08:47    mpd: [pppoe] LCP: no reply to 2 echo request(s)
Dec 5 21:08:57    mpd: [pppoe] LCP: no reply to 3 echo request(s)
Dec 5 21:09:07    mpd: [pppoe] LCP: no reply to 4 echo request(s)
Dec 5 21:13:17    mpd: [pppoe] LCP: no reply to 1 echo request(s)
Dec 5 21:13:27    mpd: [pppoe] LCP: no reply to 2 echo request(s)
Dec 5 21:13:37    mpd: [pppoe] LCP: no reply to 3 echo request(s)
Dec 5 22:22:28    mpd: [pppoe] LCP: no reply to 1 echo request(s)
Dec 5 22:22:38    mpd: [pppoe] LCP: no reply to 2 echo request(s)
Dec 5 22:22:48    mpd: [pppoe] LCP: no reply to 3 echo request(s)
Dec 5 22:24:18    mpd: [pppoe] LCP: no reply to 1 echo request(s)
Dec 5 22:56:48    mpd: [pppoe] LCP: no reply to 1 echo request(s)
Dec 5 22:56:58    mpd: [pppoe] LCP: no reply to 1 echo request(s)
Dec 5 22:56:58    mpd: [pppoe] LCP: no reply to 2 echo request(s)
Dec 5 22:57:08    mpd: [pppoe] LCP: no reply to 3 echo request(s)
Dec 5 23:16:08    mpd: [pppoe] LCP: no reply to 1 echo request(s)
Dec 6 00:25:19    mpd: [pppoe] LCP: no reply to 1 echo request(s)
Dec 6 00:25:19    mpd: [pppoe] LCP: no reply to 2 echo request(s)
Dec 6 00:25:29    mpd: [pppoe] LCP: no reply to 3 echo request(s)
Dec 6 00:26:19    mpd: [pppoe] LCP: no reply to 1 echo request(s)
Dec 6 01:38:39    kernel: re1: link state changed to DOWN
Dec 6 07:41:03    kernel: re1: link state changed to UP
Dec 6 07:41:16    kernel: re1: link state changed to DOWN
Dec 6 07:41:17    kernel: re1: link state changed to UP


re1 is my Lan and not the wan side also.  The router is serious overkill, running on a Jetway JC204-B-J7F4K1G5D barebone box with dual realtek nics, 2 gigs of ram, and Via 1.5ghz processor.  I highly doubt the hardware has anything to do with the problem since its all new (but stranger things have happened).  I don't have the system running off of a compact flash card either, instead I set it up on a Transcend flash drive designed to be just inserted in the ide port.  Last I recall the modem I setup for the DSL connection was just a standard AT&T (SBC at the time) issued modem. I have noticed one major difference from my 1.2 era router and the latest, that being the PPPoE box on the latest build doesn't ask for the keep alive instructions. It just asks for login and MTU info.  Anybody have any ideas as to what could be causing these problems, I could seriously use some help.
« Reply #1 on: December 06, 2008, 22:11:21 »
ChainSaw
Guest

I would suggest you swap out your current NICs for some Intel NICs.   Also, I would not use any CAT5 cables shorter than 5 feet.   Not sure if any of this will fix your problem but It's a minimum standard for me.

CS...
« Reply #2 on: December 06, 2008, 23:51:55 »
hatrickwah *
Posts: 4

Can't change any of the hardware.  All the hardware is onboard in a mini-itx unit.  As for the cables, pretty sure I ran 6 ft cables between the router and modem, and router and wifi router.  Nothing has been changed (that I'm aware of) where the router is hooked in, only thing changing is the m0n0wall box itself.
« Reply #3 on: January 01, 2009, 02:01:57 »
kdepasquale *
Posts: 13

Does the DSL modem support PPPoE login perchance?  That might help, although I'm running the most recent m0n0wall on AT&T's DSL and not having any issues.  (I also have a couple patch cables that are only a foot or two long, so I highly doubt that cable length is the issue - especially if the m0n0wall box is the only thing that has changed)
 
Pages: [1]
 
 
Powered by SMF 1.1.20 | SMF © 2013, Simple Machines