Edit: after rereading this, I thought I might add that: "AC" = Access Concentrator, or "PPPoE server"....
------------------------------------------
I don't know how much help I can be, since I never used Linux until about 3 days ago... 
What I discovered is this:
I cannot get the wireless interface to connect unless I use "wl ap 0" and "wl join xxxxx".... Putting the SSID and mode into the "wl0" nvram variables does nothing for me at all. I suppose there may be a script somewhere that uses those variables to initiate a connection, but since the documentation says almost nothing about scripts or startup procedure, I cannot find out how most of the system's configuration is being set. It seems there are many things happening at startup that I do not see reflected in any of the scripts that I can find under the /etc directory. This being the case, I have been forced to connect by placing the "wl" commands into a script in the init.d directory, along with the other settings that I needed made, but could not be done by setting NVRAM variables alone. After the scripts have executed at startup, my VLAN 2 interface has been created for the wireless interface, leaving VLAN1 for the WAN(int. ports 0 and 5) and VLAN0 for the other four ports. My wireless interface connecting to the AP is then the last thing scripted in the init.d directory. This leaves me after startup with 3 VLANs and a wireless connection to the AP, at which point the PPPoE client does start to connect. I should note that I used the "wifi_xxxx" NVRAM variables for the wireless, leaving the "wan_xxxx" variables to their original use. I changed the "S50pppoe" script to look at the "wifi_proto" variable instead of the "wan_proto" variable so the PPPoE client tries to connect on the correct interface.
Now that I have partially explained my configuration, you may see that by "parent interface misconfiguration", I meant that the wifi interface was not working properly, and this was causing my error. I am still getting the error, but not all of the time. When the unit boots up, the wireless connects to the AP as it is supposed to, and then the PPPoE starts to connect over the wifi interface, as it should. The error appears when I try to connect with PPPoE when there is no connection to the AC. This happened to me because of a problem with the wifi interface that I have not identified yet. My original problem was that the ifup wifi command was being issued in a script after the wireless had already connected to the AP. This, apparently, is a big issue for my installation, as executing a "ifup wifi" command after the interface is already connected literally kills the wireless connection, and this is where I was getting the PPPoE errors.
Here is what would happen:
The unit would boot up, and the wireless would automatically connect. This placed an entry in the access concentrator's (AP's) log that told me the client was connected. Somehow, immediately after the successful connection, the "ifup wifi" command was being executed again, essentially killing the wifi session. It is still a problem for me that once my initial wireless connection has been established, I cannot reconnect again without rebooting the router, and this is a huge issue..... When the second instance of the "ifup wifi" was executed, the wireless connection was killed, and this then caused the "ignored wan_proto=pppoe" error. As soon as I removed the second "ifup wifi" statement, the wireless would stay connected after startup, and then the PPPoE client would dial and connect(without encryption) properly. Unfortunately, as soon as the wireless link is gone, I am unable to re-establish it, and the PPPoE error appears again. Basically, the "ifup wifi" command is useless to me once it has already been executed at startup. I don't know if any of this will help you, or not, but in my case the problem is because the link I am trying to PPPoE over is invalid at the immediate time that it is attempting to connect.
I was also getting "eth1" invalid errors along with the "ignored wan_proto=pppoe" errors....
Does anyone reading this know any of the answers to any of the questions I asked above? Anyone know what scripts I am not seeing? At what point is this OS creating the VLAN0 and VLAN1 interfaces? I cannot find alot of things being done at startup.... I also see alot of packages installed that seem to be different versions of the same thing... How many PPP packages are there, and which one(s) is/are being used??? How can I tell this? What do I need to do to use the "kmod" packages? Is simply installing them all I have to do? All of the Linux documentation I have seen seems to be fairly consistant between between different distributions, but OpenWRT seems to be different from all of the others, with the differences not clearly stated anywhere.... For example, why is there no networking.sh file? Is a user just supposed to "know" what to do if things are not in the standard places? My installation has no S50pptp script, but I see others have it... How and where would that file be generated, and why do others have it when i don't(not that I need it)? MPPE.... Anyone... Anyone....
Sorry to have asked so many of my own questions... If there are anymore questions you have for me, cornelinux, feel free to ask....
Hitek
(Last edited by hitek146 on 18 Jul 2005, 21:40)
), but I still do not understand how you know which packages are needed or used.... Finding the one, single reference to the "logread" command helped greatly.....