I've been using ppp over a single serial line for several years now
with AT91RM9200 and AT91SAM9260 + buildroot + busybox.
Here's my relevant PPP kernel config - modules
CONFIG_PPP=m
# CONFIG_PPP_MULTILINK is not set
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
# CONFIG_PPP_SYNC_TTY is not set
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPP_MPPE=m
# CONFIG_PPPOE is not set
# CONFIG_PPPOL2TP is not set
# CONFIG_SLIP is not set
CONFIG_SLHC=m
ftp://ftp.samba.org/pub/ppp/
I'm using the same pppd/chat code (ppp-2.4.4.tar.gz)
ppp package cross compiles fine and is added into to the filesystem
image as it is compiled. When I run "pppd", the console terminal
will hang outputting nothing. I expect to see something similar to
this however:
~�}#�!}!}!} }4}"}&} } } } }%}&�.�O}'}"}(}"F�~
which would be authentication/handshaking attempts with a modem. If
I tell pppd to use Serial Port 2 "ttyS1" or any other serial port
than the currently connected consonole's port, the daemon immediatly
unloads.
Anyone have experience/insight into what could be going wrong?
Seems like you need some things in /etc/ppp
########### /etc/ppp/options #############
lock
local
nocrtscts
asyncmap 0
noauth
nodetach
persist
maxfail 9999999
lcp-echo-failure 6
lcp-echo-interval 5
lcp-max-failure 3
lcp-max-configure 3
connect 'exec chat -v -s -f /etc/ppp/winclient.chat'
########## /etc/ppp/winclient.chat ############
TIMEOUT 60
CLIENT-\p\c
CLIENTSERVER\c
Here's the command line:
pppd /dev/ttyS1 38400 10.0.0.2:10.0.0.1
I actually use an entry in /etc/inittab
null::respawn:/usr/sbin/pppd ttyS1 38400 10.0.0.2:10.0.0.1
Hope this helps
_______________________________________________
busybox mailing list
[email protected]
http://lists.busybox.net/mailman/listinfo/busybox
