Summary: pppd when called in a normal command line shell with a long pppoe service name runs fine - but fails when it is run via the script in /lib/network/ppp.sh
Just posted this in response to a pppoe service name issue in the forum https://forum.openwrt.org/viewtopic.php?id=29821 Details ------------ I have a very long service name (about 60 chars) that can vary depending on what options the user choses. I modifed pppoe.sh to create that service name and then pass it to start_pppd (in /lib/network/ppp.sh) as one of the arguments. However pppd doesn't seem to start negotiations with that method. I also tried to use the service name directly within /lib/network/ppp.sh as a parameter in the pppd command and same result. The funny thing was that the pppd command line (in /proc/process_pid/cmdline ) looked OK. Also when the pppd command was run directly from a shell with all those service parameters it ran perfectly well provided the interface was brought up first. It also runs fine if the service name is written into /etc/ppp/options. However since the service name can vary depending on user choice and can vary depending on WAN interface used (multiple WAN interfaces on the box) - writing that into the options file every time pppoe is initiated is not a good use of flash In summary - pppd when called in a normal command line shell with all the pppoe service parameters runs fine - but fails when it is run via the script in /lib/network/ppp.sh Is there some limitation with command line lengths in a script which doesn't exist in normal shell ? Ashok _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
