Oleg's 1.9.2.7-7f and Internet connection via ppoe

[vert]

Hi There!

Today I changed from standard fw to Oleg's for my WL-500gP. Upload of the firmware went well and after that I reloaded my previously saved .cfg file.

Since then I'm unable to connect to the internet! The router is directly connected to the DSL Modem. With standard firmware this setup worked perfect for internet connection. I've found some posts mentioning this problem but didn't find a solution.

What I tried:
- manual configuration of DNS Server
- configuration of idle time
- switching on/off router
- switching on/off DSL Modem
- adding maxfail=0 to the options



Jan 1 01:00:03 syslogd started: BusyBox v1.1.3
Jan 1 01:00:03 kernel: pty: 256 Unix98 ptys configured
Jan 1 01:00:03 kernel: Serial driver version 5.05c (2001-07-08) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
Jan 1 01:00:03 kernel: ttyS00 at 0xb8000300 (irq = 3) is a 16550A
Jan 1 01:00:03 kernel: ttyS01 at 0xb8000400 (irq = 3) is a 16550A
Jan 1 01:00:03 kernel: HDLC line discipline: version $Revision$, maxframe=4096
Jan 1 01:00:03 kernel: N_HDLC line discipline registered.
Jan 1 01:00:03 kernel: loop: loaded (max 8 devices)
Jan 1 01:00:03 kernel: PPP generic driver version 2.4.2
Jan 1 01:00:03 kernel: PPP Deflate Compression module registered
Jan 1 01:00:03 kernel: PPP BSD Compression module registered
Jan 1 01:00:03 kernel: MPPE/MPPC encryption/compression module registered
Jan 1 01:00:03 kernel: Amd/Fujitsu Extended Query Table v1.3 at 0x0040
Jan 1 01:00:03 kernel: number of CFI chips: 1
Jan 1 01:00:03 kernel: Flash device: 0x800000 at 0x1c000000
Jan 1 01:00:03 kernel: Physically mapped flash: squashfs filesystem found at block 945
Jan 1 01:00:03 kernel: Creating 5 MTD partitions on "Physically mapped flash":
Jan 1 01:00:03 kernel: 0x00000000-0x00040000 : "pmon"
Jan 1 01:00:03 kernel: 0x00040000-0x007f0000 : "linux"
Jan 1 01:00:03 kernel: 0x000ec4e4-0x007f0000 : "rootfs"
Jan 1 01:00:03 kernel: 0x007f0000-0x00800000 : "nvram"
Jan 1 01:00:03 kernel: 0x003e0000-0x007f0000 : "flashfs"
Jan 1 01:00:03 kernel: sflash: found no supported devices
Jan 1 01:00:03 kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Jan 1 01:00:03 kernel: IP Protocols: ICMP, UDP, TCP
Jan 1 01:00:03 kernel: IP: routing cache hash table of 512 buckets, 4Kbytes
Jan 1 01:00:03 kernel: TCP: Hash tables configured (established 2048 bind 4096)
Jan 1 01:00:03 kernel: ip_conntrack version 2.1 (256 buckets, 2048 max) - 344 bytes per conntrack
Jan 1 01:00:03 kernel: ip_conntrack_pptp version 1.9 loaded
Jan 1 01:00:03 kernel: ip_nat_pptp version 1.5 loaded
Jan 1 01:00:03 kernel: ip_tables: (C) 2000-2002 Netfilter core team
Jan 1 01:00:03 kernel: ipt_time loading
Jan 1 01:00:03 kernel: NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Jan 1 01:00:03 kernel: IPv6 v0.8 for NET4.0
Jan 1 01:00:03 kernel: IPv6 over IPv4 tunneling driver
Jan 1 01:00:03 kernel: NET4: Ethernet Bridge 008 for NET4.0
Jan 1 01:00:03 kernel: 802.1Q VLAN Support v1.7 Ben Greear <greearb@candelatech.com>
Jan 1 01:00:03 kernel: All bugs added by David S. Miller <davem@redhat.com>
Jan 1 01:00:03 kernel: FAT: bogus logical sector size 2816
Jan 1 01:00:03 kernel: FAT: bogus logical sector size 2816
Jan 1 01:00:03 kernel: NTFS: Unable to set blocksize 512.
Jan 1 01:00:03 kernel: VFS: Mounted root (squashfs filesystem) readonly.
Jan 1 01:00:03 kernel: Mounted devfs on /dev
Jan 1 01:00:03 kernel: Freeing unused kernel memory: 72k freed
Jan 1 01:00:03 kernel: Algorithmics/MIPS FPU Emulator v1.5
Jan 1 01:00:03 kernel: eth0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.90.37.0
Jan 1 01:00:03 kernel: PCI: Enabling device 01:02.0 (0004 -> 0006)
Jan 1 01:00:03 kernel: eth1: Broadcom BCM4318 802.11 Wireless Controller 3.90.37.0
Jan 1 01:00:03 kernel: vlan0: add 33:33:00:00:00:01 mcast address to master interface
Jan 1 01:00:03 kernel: aster interface
Jan 1 01:00:03 kernel: vlan0: dev_set_promiscuity(master, 1)
Jan 1 01:00:03 kernel: device eth0 entered promiscuous mode
Jan 1 01:00:03 kernel: device vlan0 entered promiscuous mode
Jan 1 01:00:03 kernel: device eth1 entered promiscuous mode
Jan 1 01:00:03 kernel: br0: port 2(eth1) entering listening state
Jan 1 01:00:03 kernel: br0: port 1(vlan0) entering listening state
Jan 1 01:00:03 kernel: br0: port 2(eth1) entering learning state
Jan 1 01:00:03 kernel: br0: port 1(vlan0) entering learning state
Jan 1 01:00:03 kernel: br0: port 2(eth1) entering forwarding state
Jan 1 01:00:03 kernel: br0: topology change detected, propagating
Jan 1 01:00:03 kernel: br0: port 1(vlan0) entering forwarding state
Jan 1 01:00:03 kernel: br0: topology change detected, propagating
Jan 1 01:00:03 dnsmasq[66]: started, version 2.22 cachesize 150
Jan 1 01:00:03 dnsmasq[66]: DHCP, IP range 192.168.1.2 -- 192.168.1.254, lease time 24h
Jan 1 01:00:03 dnsmasq[66]: DHCP, /tmp/dnsmasq.log will be written every 8h
Jan 1 01:00:03 dnsmasq[66]: read /etc/hosts - 5 addresses
Jan 1 01:00:03 dnsmasq[66]: reading /tmp/resolv.conf
Jan 1 01:00:03 dnsmasq[66]: using nameserver 217.237.150.225#53
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-uhci.c: $Revision: 1.275 $ time 10:25:12 Jun 17 2006
Jan 1 01:00:03 kernel: usb-uhci.c: High bandwidth mode enabled
Jan 1 01:00:03 kernel: PCI: Enabling device 01:03.0 (0000 -> 0001)
Jan 1 01:00:03 kernel: ECHI PCI device 30381106 found.
Jan 1 01:00:03 kernel: UCHI reg 0x41 = 10
Jan 1 01:00:03 kernel: UCHI reg 0x41 changed to = 0
Jan 1 01:00:03 kernel: usb-uhci.c: USB UHCI at I/O 0x100, IRQ 2
Jan 1 01:00:03 kernel: usb-uhci.c: Detected 2 ports
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: PCI: Enabling device 01:03.1 (0000 -> 0001)
Jan 1 01:00:04 kernel: ECHI PCI device 30381106 found.
Jan 1 01:00:04 kernel: UCHI reg 0x41 = 10
Jan 1 01:00:04 kernel: UCHI reg 0x41 changed to = 0
Jan 1 01:00:04 kernel: usb-uhci.c: USB UHCI at I/O 0x120, IRQ 2
Jan 1 01:00:04 kernel: usb-uhci.c: Detected 2 ports
Jan 1 01:00:04 kernel: usb.c: new USB bus registered, assigned bus number 2
Jan 1 01:00:04 kernel: hub.c: USB hub found
Jan 1 01:00:04 kernel: hub.c: 2 ports detected
Jan 1 01:00:04 kernel: usb-uhci.c: v1.275:USB Universal Host Controller Interface driver
Jan 1 01:00:04 kernel: PCI: Enabling device 01:03.2 (0000 -> 0002)
Jan 1 01:00:04 kernel: ehci_hcd 01:03.2: PCI device 1106:3104
Jan 1 01:00:04 kernel: ehci_hcd 01:03.2: irq 2, pci mem c00a3000
Jan 1 01:00:04 kernel: usb.c: new USB bus registered, assigned bus number 3
Jan 1 01:00:04 kernel: ECHI PCI device 31041106 found.
Jan 1 01:00:04 kernel: ECHI reg 0x49 = 80010f20
Jan 1 01:00:04 kernel: ECHI reg 0x49 changed to = 80010f00
Jan 1 01:00:04 kernel: ECHI reg 0x4b = 80010f09
Jan 1 01:00:04 kernel: ECHI reg 0x4b changed to = 80010f29
Jan 1 01:00:04 kernel: PCI: 01:03.2 PCI cache line size set incorrectly (0 bytes) by BIOS/FW, correcting to 32
Jan 1 01:00:04 kernel: ehci_hcd 01:03.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
Jan 1 01:00:04 kernel: hub.c: USB hub found
Jan 1 01:00:04 kernel: hub.c: 4 ports detected
Jan 1 01:00:04 kernel: usb.c: registered new driver usblp
Jan 1 01:00:04 kernel: printer.c: v0.13: USB Printer Device Class driver
Jan 1 01:00:05 dnsmasq[66]: DHCPRELEASE(br0) 192.168.1.72 00:18:de:6c:fd:63 unknown lease
Jan 1 01:00:06 pppd[79]: Plugin rp-pppoe.so loaded.
Jan 1 01:00:06 pppd[79]: RP-PPPoE plugin version 3.3 compiled against pppd 2.4.2
Jan 1 01:00:06 pppd[80]: pppd 2.4.2 started by admin, uid 0
Jan 1 01:00:06 pppd[80]: Using interface ppp0
Jan 1 01:00:06 pppd[80]: local IP address 10.64.64.64
Jan 1 01:00:06 pppd[80]: remote IP address 10.112.112.112
Jan 1 01:00:07 dnsmasq[66]: DHCPDISCOVER(br0) 192.168.1.72 00:18:de:6c:fd:63
Jan 1 01:00:07 dnsmasq[66]: DHCPOFFER(br0) 192.168.1.72 00:18:de:6c:fd:63
Jan 1 01:00:07 dnsmasq[66]: DHCPREQUEST(br0) 192.168.1.72 00:18:de:6c:fd:63
Jan 1 01:00:07 dnsmasq[66]: DHCPACK(br0) 192.168.1.72 00:18:de:6c:fd:63 Turing
Jan 1 01:00:07 pppd[80]: Starting link
Jan 1 01:00:42 pppd[80]: Timeout waiting for PADO packets
Jan 1 01:00:42 pppd[80]: Unable to complete PPPoE Discovery
Jan 1 01:01:17 pppd[80]: Starting link
Jan 1 01:01:52 pppd[80]: Timeout waiting for PADO packets
Jan 1 01:01:52 pppd[80]: Unable to complete PPPoE Discovery

...



Is this the "WAN port dies" problem? (As my conncetion never worked, so how could it die?) Are there solutions out there? Do I really have to buy another modem?

Thanks in advance,
I really appreciate all the work you guys put into this,

vert

[Kasper]

I'm new to this, actialy flashed my WL-500gP for the first time earlier today, but I would think that loading your config file from the standard fw into the Oleg fw is a no go, that could create problems.

I would try to load the factory settings, and manualy change the settings.

[gstadler]

This is something similar to my problem, although to a much worse degree. My router (wl500gP) also connects to an ADSL modem, but after power on it can always connect successfully. However after an arbitrary amount of time, the router drops the connection and after that it cannot reconnect. (Timeout waiting for PADO packets). When I restart the router it has the same behaviour you just described. I tried it with two different ADSL modems (Askey and DLINK) and got the same problem.

Have you tried the manual 'connect' button in the Status & Log menu of the web interface? It used to help me to get the connection.

My theory is that there is something wrong going on in the pppd module, maybe it cannot re-initialize itself properly after dropping the connection. It would be useful to know how to enable a more detailed logging or a trace to get more information.

Can someone please advise on this one?

[Moody Blue]

My ADSL modem (ethernet connection) is parametrized in bridge mode and works great in ppoe, either in Oleg or in ASUS fw. It worked great with my previous router (an old Linksys), and at the time many people with that Linksys complained that the only way to have stable ppoe was to put the modem in bridge mode, and MTU=1492 both in the router and in the modem.

[gstadler]

Putting the modem in bridge mode is not always an option. In my opinion this is a router issue and should be solved somewhere in the firmware. I have read a tremendous amount of posts but until today:

* there isn't a clear explanation for PPPoE connection problems of the wl500gP
* there is no solution provided only hints which most of the time are releted to other problems (i.e: wan dies).

[Moody Blue]

In my opinion this is a router issue and should be solved somewhere in the firmware
It might as well be a problem with the modem firmware. And most probably is, my old Linksys never worked well with my actual modem, when the modem was parametrized like a router.

I'm not a NAT / router specialist, my experience of having the modem in router mode is that, when there is more than one computer active in the WLAN, the service seems to die. Probably bad parametrization, but having the modem in bridge mode works 100% sure, only precludes me from accessing its configuration page through the ASUS, but I still can access it through its usb port. In my case that's not a problem, of course if I had to give remote support it would be.

[gstadler]

After installing the new 1.9.2.7-7g firmware, the problem does not occur anymore.

[zwitter]

I had same problem with Speed Stream 5360 [i believe its Siemens modem]. I was able to set connection just after installation and that was it. After that nothing helped - modem reboot router reboot. Even if you set dns manually it wont help you.
But my problem was with g version :/