Bekijk de volledige versie : PPPoE fails after Wl500g restart...
Since yesterday i replaced the modem supplied by my ISP (Freebox) with a "Bewan ADSL2+ Combo" ethernet modem.
The modem works fine with the WL500, except that if i restart the WL500 after changing some settings i have to restart the modem too, otherwise PPPoE negotiation fails.
The log mentions something about PADO packets :confused:.
Any ideas ?
Update : The failure no longer occurs after restarting... Now it occurs after turning off/on the router. However, unpluging the network cable causes the router to initiate the PPPoE session....
I just upgraded to 7f firmware, let's see if this still happens with this firmware....
The problem came up yesterday evenning again...
The log says that the CHAP authentification failed.... Strange, when the connection succeeds the logs says that the PAP authetification succeeded. :confused:
Is there a way to force PPPd to use PAP instead of CHAP ?
Ok, this evenning the asus kept crashing after reboot... The pppoe connection fails, an then the unit runs out of memory and starts killing processes.
Here is the log i just managed to retrieve before the unit totally crashes :
Jan 1 01:00:02 syslogd started: BusyBox v1.1.3
Jan 1 01:00:02 kernel: 0x00040000-0x003f0000 : "linux"
Jan 1 01:00:02 kernel: 0x000ec4e4-0x003f0000 : "rootfs"
Jan 1 01:00:02 kernel: 0x003f0000-0x00400000 : "nvram"
Jan 1 01:00:02 kernel: 0x003e0000-0x003f0000 : "flashfs"
Jan 1 01:00:02 kernel: sflash: chipcommon not found
Jan 1 01:00:02 kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Jan 1 01:00:02 kernel: IP Protocols: ICMP, UDP, TCP
Jan 1 01:00:02 kernel: IP: routing cache hash table of 512 buckets, 4Kbytes
Jan 1 01:00:02 kernel: TCP: Hash tables configured (established 1024 bind 2048)
Jan 1 01:00:02 kernel: ip_conntrack version 2.1 (128 buckets, 1024 max) - 344 bytes per conntrack
Jan 1 01:00:02 kernel: ip_conntrack_pptp version 1.9 loaded
Jan 1 01:00:02 kernel: ip_nat_pptp version 1.5 loaded
Jan 1 01:00:02 kernel: ip_tables: (C) 2000-2002 Netfilter core team
Jan 1 01:00:02 kernel: ipt_time loading
Jan 1 01:00:02 kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Jan 1 01:00:02 kernel: IPv6 v0.8 for NET4.0
Jan 1 01:00:02 kernel: IPv6 over IPv4 tunneling driver
Jan 1 01:00:02 kernel: NET4: Ethernet Bridge 008 for NET4.0
Jan 1 01:00:02 kernel: 802.1Q VLAN Support v1.7 Ben Greear <greearb@candelatech.com>
Jan 1 01:00:02 kernel: All bugs added by David S. Miller <davem@redhat.com>
Jan 1 01:00:02 kernel: FAT: bogus logical sector size 56832
Jan 1 01:00:02 kernel: FAT: bogus logical sector size 56832
Jan 1 01:00:02 kernel: NTFS: Unable to set blocksize 512.
Jan 1 01:00:02 kernel: VFS: Mounted root (squashfs filesystem) readonly.
Jan 1 01:00:02 kernel: Mounted devfs on /dev
Jan 1 01:00:02 kernel: Freeing unused kernel memory: 72k freed
Jan 1 01:00:02 kernel: Warning: unable to open an initial console.
Jan 1 01:00:02 kernel: Algorithmics/MIPS FPU Emulator v1.5
Jan 1 01:00:02 kernel: eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.37.0
Jan 1 01:00:02 kernel: eth1: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.37.0
Jan 1 01:00:02 kernel: PCI: Enabling device 01:02.0 (0004 -> 0006)
Jan 1 01:00:02 kernel: eth2: Broadcom BCM4320 802.11 Wireless Controller 3.90.37.0
Jan 1 01:00:02 kernel: device eth0 entered promiscuous mode
Jan 1 01:00:02 kernel: device eth2 entered promiscuous mode
Jan 1 01:00:02 kernel: br0: port 2(eth2) entering listening state
Jan 1 01:00:02 kernel: br0: port 1(eth0) entering listening state
Jan 1 01:00:02 kernel: 6>br0: port 2(eth2) entering learning state
Jan 1 01:00:02 kernel: br0: port 1(eth0) entering learning state
Jan 1 01:00:02 kernel: br0: port 2(eth2) entering forwarding state
Jan 1 01:00:02 kernel: br0: topology change detected, propagating
Jan 1 01:00:02 kernel: br0: port 1(eth0) entering forwarding state
Jan 1 01:00:02 kernel: br0: topology change detected, propagating
Jan 1 01:00:03 kernel: usb.c: registered new driver usbdevfs
Jan 1 01:00:03 kernel: usb.c: registered new driver hub
Jan 1 01:00:03 kernel: usb-ohci.c: USB OHCI at membase 0xb8004000, IRQ 2
Jan 1 01:00:03 kernel: usb-ohci.c: usb-00:04.0, PCI device 14e4:4715
Jan 1 01:00:03 kernel: usb.c: new USB bus registered, assigned bus number 1
Jan 1 01:00:03 kernel: hub.c: USB hub found
Jan 1 01:00:03 kernel: hub.c: 2 ports detected
Jan 1 01:00:04 kernel: hub.c: new USB device 00:04.0-1, assigned address 2
Jan 1 01:00:04 kernel: usb.c: USB device 2 (vend/prod 0x471/0x310) is not claimed by any active driver.
Jan 1 01:00:04 USB webcam: attached
Jan 1 01:00:05 kernel: lp0: using parport0 (polling).
Jan 1 01:00:05 kernel: usb.c: registered new driver usblp
Jan 1 01:00:05 kernel: printer.c: v0.13: USB Printer Device Class driver
Jan 1 01:00:05 kernel: Linux video capture interface: v1.00
Jan 1 01:00:06 kernel: pwc Philips webcam module version 9.0.2 loaded.
Jan 1 01:00:06 kernel: pwc Supports Philips PCA645/646, PCVC675/680/690, PCVC720[40]/730/740/750 & PCVC830/840.
Jan 1 01:00:06 kernel: pwc Also supports the Askey VC010, various Logitech Quickcams, Samsung MPC-C10 and MPC-C30,
Jan 1 01:00:06 kernel: pwc the Creative WebCam 5 & Pro Ex, SOTEC Afina Eye and Visionite VCS-UC300 and VCS-UM100.
Jan 1 01:00:06 kernel: pwc Default image size set to vga [640x480].
Jan 1 01:00:06 kernel: usb.c: registered new driver Philips webcam
Jan 1 01:00:06 kernel: pwc Philips PCVC730K (ToUCam Fun)/PCVC830 (ToUCam II) USB webcam detected.
Jan 1 01:00:09 pppd[81]: Plugin rp-pppoe.so loaded.
Jan 1 01:00:09 pppd[81]: RP-PPPoE plugin version 3.3 compiled against pppd 2.4.2
Jan 1 01:00:09 pppd[82]: pppd 2.4.2 started by admin, uid 0
Jan 1 01:00:09 kernel: lp driver: get device ID
Jan 1 01:00:09 kernel: neg fail
Jan 1 01:00:10 dnsmasq[51]: DHCPREQUEST(br0) 172.16.0.2 00:0c:f6:10:39:9e
Jan 1 01:00:10 dnsmasq[51]: DHCPACK(br0) 172.16.0.2 00:0c:f6:10:39:9e stef
Jan 1 01:00:10 dropbear[94]: Running in background
Jan 1 01:00:10 kernel: lp driver: get device ID
Jan 1 01:00:10 kernel: neg fail
Jan 1 01:00:10 kernel: neg fail
Jan 1 01:00:11 kernel: usb_control/bulk_msg: timeout
Jan 1 01:00:11 kernel: usb.c: error getting string descriptor 0 (error=-145)
Jan 1 01:00:11 kernel: pwc Registered as /dev/video0.
Jan 1 01:00:11 kernel: pwc Philips webcam decompressor routines version 9.0-BETA-2
Jan 1 01:00:11 kernel: pwc Supports all cameras supported by the main module (pwc).
Jan 1 01:00:12 kernel: usb_control/bulk_msg: timeout
Jan 1 01:00:12 kernel: pwc Failed to set LED on/off time.
Jan 1 01:00:13 kernel: usb_control/bulk_msg: timeout
Jan 1 01:00:13 kernel: pwc Failed to set video mode VGA@10 fps; return code = -145
Jan 1 01:00:14 kernel: usb_control/bulk_msg: timeout
Jan 1 01:00:14 kernel: pwc Failed to set video mode QSIF@10 fps; return code = -145
Jan 1 01:00:30 kernel: usb_control/bulk_msg: timeout
Jan 1 01:00:30 kernel: pwc Failed to set LED on/off time.
Jan 1 01:00:31 kernel: usb_control/bulk_msg: timeout
Jan 1 01:00:31 kernel: pwc Failed to set video mode VGA@10 fps; return code = -145
Jan 1 01:00:32 kernel: usb_control/bulk_msg: timeout
Jan 1 01:00:32 kernel: pwc Failed to set video mode QSIF@10 fps; return code = -145
Jan 1 01:00:44 pppd[82]: Timeout waiting for PADO packets
Jan 1 01:00:44 pppd[82]: Unable to complete PPPoE Discovery
Jan 1 01:00:50 kernel: usb_control/bulk_msg: timeout
Jan 1 01:00:50 kernel: pwc Failed to set LED on/off time.
Jan 1 01:00:51 kernel: usb_control/bulk_msg: timeout
Jan 1 01:00:51 kernel: pwc Failed to set video mode VGA@10 fps; return code = -145
Jan 1 01:00:52 kernel: usb_control/bulk_msg: timeout
Jan 1 01:00:52 kernel: pwc Failed to set video mode QSIF@10 fps; return code = -145
Jan 1 01:01:10 kernel: usb_control/bulk_msg: timeout
Jan 1 01:01:10 kernel: pwc Failed to set LED on/off time.
Jan 1 01:01:11 kernel: usb_control/bulk_msg: timeout
Jan 1 01:01:11 kernel: pwc Failed to set video mode VGA@10 fps; return code = -145
Jan 1 01:01:13 kernel: usb_control/bulk_msg: timeout
Jan 1 01:01:13 kernel: pwc Failed to set video mode QSIF@10 fps; return code = -145
Jan 1 01:01:37 USB webcam: webcam capture no frame
Jan 1 01:01:50 pppd[82]: Timeout waiting for PADO packets
Jan 1 01:01:50 pppd[82]: Unable to complete PPPoE Discovery
Jan 1 01:01:55 kernel: usb_control/bulk_msg: timeout
Jan 1 01:02:01 kernel: Out of Memory: Killed process 51 (dnsmasq).
I'm currently connected with a Dell TrueMobile 2300, and the connection is just fine.... Could a reset to factory settings help ?
Ok i continue to talk with myself ! Maybe this could help someone facing the same issue.
Yesterday i kept on investigating and reseted my wl500 to factory settings. The problem arised again i.e.: connection fails, unit runs out of memory and restarts...
I also noticed that the problem only occurs after a soft reboot i.e. typing reboot in the console or rebooting through web interface.... Making a hard reboot gives me succes most of the time, but not always. Sometimes the wl500 is stating that the cable is not attached.... Unpluging and repluging the WAN cable solves the problem.
This morning while driving to work i was thinking it through and i remembered that my ADSL modem is providing a DHCP server on its ethernet interface. Can this interfer with the PPPoE protocol ?
As far as i know DHCP is working on the "MAC" level, does PPPoE work on this level to ?
Hi max2950 how are you doing ? Still having problems with your PPPoE ?
Seems like i'm still talking to myself :p :p
Yesterday i tried disabling the DHCP stuff from the modem, but had no success.
After rebooting, i noticed this sh*t in the log :
Jan 1 01:00:11 kernel: pwc Image is mirrored.
Jan 1 01:00:11 kernel: pwc Image is normal.
Jan 1 01:00:11 kernel: pwc Snapshot button pressed.
Jan 1 01:00:11 kernel: pwc Snapshot button released.
Jan 1 01:00:11 kernel: pwc Snapshot button pressed.
Jan 1 01:00:11 kernel: pwc Snapshot button released.
Jan 1 01:00:11 kernel: pwc Image is mirrored.
Jan 1 01:00:11 kernel: pwc Image is normal.
Jan 1 01:00:11 kernel: pwc Snapshot button pressed.
Jan 1 01:00:11 kernel: pwc Image is mirrored.
Jan 1 01:00:11 kernel: pwc Snapshot button released.
Jan 1 01:00:11 kernel: pwc Image is normal.
Jan 1 01:00:11 kernel: pwc Snapshot button pressed.
Jan 1 01:00:11 kernel: pwc Snapshot button released.
Jan 1 01:00:11 kernel: pwc Snapshot button pressed.
Jan 1 01:00:11 kernel: pwc Snapshot button released.
Jan 1 01:00:11 kernel: pwc Image is mirrored.
Jan 1 01:00:11 kernel: pwc Snapshot button pressed.
Jan 1 01:00:11 kernel: pwc Snapshot button released.
Jan 1 01:00:11 kernel: pwc Image is normal.
Jan 1 01:00:11 kernel: pwc Snapshot button pressed.
Jan 1 01:00:11 kernel: pwc Snapshot button released.
Jan 1 01:00:11 kernel: pwc Image is mirrored.
Jan 1 01:00:11 kernel: pwc Image is normal.
Jan 1 01:00:11 kernel: pwc Snapshot button pressed.
Jan 1 01:00:11 kernel: pwc Snapshot button released.
Jan 1 01:00:11 kernel: pwc Image is mirrored.
Jan 1 01:00:11 kernel: pwc Snapshot button pressed.
Jan 1 01:00:11 kernel: pwc Image is normal.
Jan 1 01:00:11 kernel: pwc Snapshot button released.
Jan 1 01:00:11 kernel: pwc Image is mirrored.
Jan 1 01:00:11 kernel: pwc Image is normal.
Jan 1 01:00:11 kernel: pwc Snapshot button pressed.
Jan 1 01:00:11 kernel: pwc Image is mirrored.
Jan 1 01:00:11 kernel: pwc Snapshot button released.
Jan 1 01:00:11 kernel: pwc Image is normal.
Jan 1 01:00:11 kernel: pwc Snapshot button pressed.
Jan 1 01:00:11 kernel: pwc Image is mirrored.
Jan 1 01:00:11 kernel: pwc Snapshot button released.
Jan 1 01:00:11 kernel: pwc Image is normal.
Jan 1 01:00:11 kernel: pwc Snapshot button pressed.
Jan 1 01:00:11 kernel: pwc Snapshot button released.
Jan 1 01:00:11 kernel: pwc Image is mirrored.
Jan 1 01:00:11 kernel: pwc Snapshot button pressed.
So i unplugged the camera and restarded the unit. Connection went up very fast, nothing about PADO packets or so.
I plugged the camera in and the router dropped the connection:confused: :confused: ...
I noticed that when i have problem connecting, i have error messages about the camera (like those above) or about USB
Jan 1 01:01:11 kernel: usb_control/bulk_msg: timeout
I do not have those messages if i just have my USB flash drive plugged in. i also tested with a self powered USB hub, but i still receive those bulk_msg timeout messages when plugging the camera...
Maybe the camera is dying, or their might be some conflict somewhere.:o