Pppd porting and 3G Functions

 

 

1. Kernel configuration supports pppd Dialing:

Make menuconfig

Device Drivers->

-> Network device support->

<*> PPP (Point-to-Point Protocol) support [*] PPP Multilink support <*> PPP support for async serial ports <*> PPP support for sync tty ports <*> slip (Serial Line) Support

[*] Cslip compressed Headers

 

The first part of the kernel: in fact, this part should be accurate to the Kernel configuration, because to use pppoe, we must first support the kernel options. I use the Linux 2.6.16 kernel version. Select all PPP options in-> Device Drivers-> network device support-> PPP (Point-to-Point Protocol. In earlier versions of the kernel, you may need to add the universal tun/TAP Device Driver support option (similar to PPP ).

 

The second part of pppd: This part is relatively simple, just need to download any version of The ppp-2.4.1-ppp-2.4.4. Decompress the package, enter./configure in the terminal, and then execute make cc = arm-Linux-GCC. Go to the pppd directory and copy the compiled pppd file to the/usr/sbin directory of the Development Board's file system. Here is a judgment on whether pppd is correctly transplanted, enter pppd on the version to check whether there is any garbled code. If there is any garbled code, congratulations.

 

The third part is pppoe: for cross-compilation similar to pppd, download the RP-pppoe development kit first. It is best to use version 3.7 or 3.8. Go to the src directory and run. /configure, and then modify the MAKEFILE file generated under SRC, replace all GCC in makefile with arm-Linux-GCC, and AR with arm-Linux-ar, the makefile in the libevent directory under the src directory is also modified. After the two makefiles are modified, execute make, make install, all pppoe files (pppoe, pppoe-server, pppoe-sniff, pppoe-relay, pppoe-setup, pppoe-start, pppoe-stop, pppoe-status, pppoe-Connect) are copied to the/usr/sbin directory of the Development Board.

 

Development Board configuration: After the network cable is connected, enter pppoe-setup directly. The installation prompt is "Enter your information, you can temporarily select the server in DNS (this will enable IP address ping only for the next Ping, but not for the website address. If you know the DNS of your network's access provider, enter it ), I chose "0" and "OK" for the firewall. If pppoe-start is used to start the connection at this time, you will receive a prompt "timeout". What should we do? You need to create a PTS folder under the dev directory, enter pts, and create the node mknod 0 C 136 0; mknod 1 C 136 1. Every connection needs to be established, which is quite troublesome. So write these commands into the startup script. If you believe this, you will generally get a connect message.

 

 

Now, let's talk about the "accident" I encountered! In my accident, I did not mention the PTS folder or the hateful school broadband. the dormitory broadband uses pppoe, at least I think so (because pppoe was chosen when I created the connection), but in fact it is not. Indeed, dormitory broadband is not a DSL either, every day, I took the development board to the dormitory for debugging and got a lot of inexplicable errors, which could not be solved by Google Daxian. For example:

Connect: ppp0 <-->/dev/pts/0
Warning-secret file/etc/PPP/PAP-secrets has world and/or group accespppoe: Read (asyncreadfromppp): S
Warning-secret file/etc/PPP/PAP-secrets has world and/or group access
Remote message: limit users err
PAP authentication failed
Connection terminated.
Pppoe: Read (asyncreadfromppp): Session 11215: Input/Output Error

LCP: timeout sending config-Requests
Connection terminated.
I also waste more than N times in the lab and dormitory. The 35-degree Nanjing day is not a general depressing thing. Haha, it's best to make up your mind to build a pppoe server in the lab and build a pppoe server in succession. It turns out that my arm pppoe port has been okay, it's just the relationship between the school network that has made me think twice about a pseudo proposition that doesn't exist at all.

In fact, building a pppoe server is very simple. It is very suitable for environments where no ADSL dialing is available in the workplace. The next raspppoe software is enough. Paste the following steps:

1. Download raspppoe (version 0.99)

2. Install the raspppoe Protocol

Local connection --> properties --> General --> Installation --> protocol --> Add --> install from disk --> browse --> "find the winpppoe in the directory where your rasppoe is located. INF "--> open --> continue ............... You can.

3. Create a dial-in link

Create a connection wizard --> select Advanced connection --> accept incoming connections --> select your NIC (if pppoe is not installed, no Nic is displayed) --> Virtual Private connections are not allowed (it doesn't matter if you need to create a VPN Server) --> select the user that allows dial-in (this user list is the user list of the local machine. You can set it in management tools, Computer Management, users, and groups) --> select the Internet protocol in the network software step and set the specified IP address pool to assign IP addresses to the dial-in users.

4. if you have any conditions, you can test whether the pppoe dial-up is successful (create a new connection --> connect to the internet --> manually set my connections --> connect with a broadband connection that requires the user name and password --> You can continue the next step; after the connection is established, run the new connection. In the General tab of the property box, enter the IP address of the server. After confirming, use the user name and password that are allowed to dial in, then, use ipconfig in DOS-shell to view the IP address of the new connection)

Note: The pppor dialing for this verification is completed by the server and client in the same VLAN, because the pppoe request is a layer-2 broadcast.

 

Next, configure the file

There are three common methods on the Internet:
1. Use smart PPP dialing software wvdial:
Reference case: Using wvdial to start PPP dial-up Internet access
Http://blog.chinaunix.net/u2/76263/showart_1227064.html
2. Use three scripts: PPP-on, PPP-on-dialer, and PPP-off.
Reference: Linux-PPP-HOWTO (
Http://www.dcaccess.net/welcome/linux/PPP-HOWTO.html
), Howto hook up PPP (
Http://www.theory.physics.ubc.ca/ppp-linux.html
) And many successful online Cases

Note: The above two methods have their own advantages and disadvantages. The first method is intelligent and stable. He does not need a chat program. He uses the integrated wvdial toolkit to directly connect to the ISP, which is secure and stable and can be automatically retained.
Dial. The second method is to use the chat program, but many parameters need to be configured by yourself. Although it is flexible, if you encounter a dialing error, if you do not know the specific mechanism and
The meaning of the parameter, you will be very difficult, Maybe luck is good, your running environment is exactly consistent with the local mobile ISP configuration, congratulations, you can access the Internet, but you're sorry that you didn't learn anything.
If you are a friend of the PPP mechanism, you can try 2nd methods. If you are familiar with the PPP protocol, observe and think about the information in/var/log/messages.
3. Use the pppd call somescript command:
Reference cases:
Http://blog.csdn.net/bouillisy/archive/2005/07/27/436203.aspx
This method is used. The configuration files related to PPP dialing are listed and explained below;
Note
Purpose: The GPRS module I use is Huawei.
Gtm900a/B, the internal settings of different modules are different, so some parameter configurations in the configuration file are different. In addition, the environment and location of your PC or arm Development Board are also different.
These potential factors should be taken into account when problems arise. Troubleshooting is a boring process, but in turn, this process will gain a lot.

Mo
Set up the GPRS-connect-chat file in the/etc/PPP/directory as follows (each parameter is explained in detail in the PPP-howto. It is in the PPP
During the underlying session, each line of parameters for the chat process is a "expected/sent" combination sequence. When some classic errors such as "LCP: timeout sending
Config-requests "," Serial Line is not 8 bit clean... "," serial line is
Looped
Back, see the two documents mentioned in method 2, or Google. Note: The reason why the solution cannot be exactly given is that the same error message is printed, which I call a symptom,
The same phenomenon may be caused by many reasons. You need to perform troubleshooting on your own .)
#/Etc/PPP/GPRS-connect-chat
Timeout 15
Abort '/nbusy/R'
Abort '/Nno answer/R'
Abort '/nringing/R/n/R/nringing/R'
# ''At
# 'OK-++/C-OK' ATH0
Timeout 40
''/Rat
OK ats0 = 0 # These are standard AT commands. We recommend that you check the AT command manual of the module.
OK ate0v1
OK at + cgdcont = 1, "ip", "cmnet" # Set the ISP access gateway to China Mobile's cmnet. If you want more access resources
OK atdt * 99 *** 1 # China Mobile GPRS access number?
Connect''
++ ++ ++
The/etc/PPP/peers/GPRS file is created to provide configuration parameters for the pppd process. For details, see the output content of MAN 8 pppd, if a problem occurs, this is a very important reference page. The content is as follows:
#/Etc/PPP/peers/GPRS
# Usage: root> pppd call GPRS
/Dev/s3c2410_serial1 # change it to your own port name
115200 # change to the serial port baud rate
Nocrtscts
# Maybe your serial port needs crtscts and hardware throttling. This is determined by your serial port. Generally, the serial port of an embedded system does not contain hardware throttling, and nocrtscts is not required.
Modem # This parameter allows the pppd process to wait for the CD (carrier detect) signal sent back by the module, which is opposite to the local signal.
# Noauth
Debug # output the debugging information to/var/log/messages. After successful debugging, remove it to reduce the garbage generation.
Nodetach
# Hide-Password
Usepeerdns # The following three parameters are generally indispensable
Noipdefault
Defaultroute
User smsong # Set the access user name, which is used in chap-secrets or pap-secets.
0.0.0.0: 0.0.0.0 # Set the local IP address and the remote IP address to 0 so that the access ISP can assign a local IP address.
Ipcp-Accept-local # requires peer, that is, the ISP, to assign a dynamic IP address to itself.
# Ipcp-Accept-remote
# LCP-Echo-failure 12
# LCP-Echo-interval 3
Noccp # The compression control protocol is not required. It is possible that the Peer end does not need the protocol.
# Novj
# Novjccomp
Persist # ensure that you do not exit when the connection is disconnected and try to re-open the connection
Connect '/usr/sbin/chat-S-v-F/etc/PPP/GPRS-connect-chat'
# Pppd calls the chat session process to access the peer ISP, starts the peer pppd, and then cooperates with the peer pppd
# Negotiate network parameters and chap/PAP authentication. After successful authentication, IP addresses at the NCP layer are allocated.
++ ++ ++
#/Etc/PPP/chap-secets
# Secrets for authentication using chap
# Client server secret IP addresses
####### RedHat-config-network will overwrite this part !!! (BEGIN )##########
####### RedHat-config-network will overwrite this part !!! (End )############
Smsong x 123456 *
In some regions, GPRS may use pap authentication to access users. Therefore, in the same level directory, create the pap-secets file, similar to chap-secets, the content contains four items: 2nd and 4th, which are generally represented by an asterisk. You need to place these two files in/etc/PPP.
++ ++ ++
After the ppp0 connection is established, you can use Ctrl + C or the following script program PPP-off to disconnect the PPP connection.
#/Etc/PPP-off
#! /Bin/sh
######################################## ##############################
#
# Determine the device to be terminated.
#
If ["$1" = ""]; then
Device = ppp0
Else
Device = $1
Fi
######################################## ##############################
#
# If the ppp0 PID file is present then the program is running. Stop it.
If [-r/var/run/$ device. pid]; then
Kill-int 'cat/var/run/$ device. Pi'
#
# If the kill did not work then there is no process running for this
# PID. It may also mean that the lock file will be left. You may wish
# To delete the lock file at the same time.
If [! "$? "=" 0 "]; then
Rm-F/var/run/$ device. PID
Echo "error: removed stale PID file"
Exit 1
Fi
#
# Success. Let pppd clean up its own junk.
Echo "PPP link to $ device terminated ."
Exit 0
Fi
#
# The PPP process is not running for ppp0
Echo "error: PPP link is not active on $ device"
Exit 1
++ ++ ++
After completing the preceding configuration, enter the pppd call GPRS command. Note that if your GPRS file is not in the/etc/PPP/peers/directory, the path is indicated to pppd.
[Root @ localhost ppp_scripts] # pppd call GPRS
Timeout set to 15 seconds
Abort on (/nbusy/R)
Abort on (/Nno answer/R)
Abort on (/nringing/R/n/R/nringing/R)
Timeout set to 40 seconds
Send (^ mat ^ m)
CT (OK)
^ M
OK
-- Got it
Send (ats0 = 0 ^ m)
CT (OK)
^ M
At ^ m
OK
-- Got it
Send (ate0v1 ^ m)
CT (OK)
^ M
^ M
OK
-- Got it
Send (at + cgdcont = 1, "ip", "cmnet" ^ m)
CT (OK)
^ M
Ats0 = 0 ^ m
OK
-- Got it
Send (atdt * 99 *** 1 # ^ m)
Secondary CT (CONNECT)
^ M
^ M
OK ^ m
Ate0v1 ^ m
OK ^ m
^ M
OK ^ m
^ M
OK ^ m
^ M
OK ^ m
^ M
Connect
-- Got it
Send (^ m)
Serial Connection established.
Using Channel 20
Using interface ppp0
Connect: ppp0/dev/ttys0
Warning-secret file/etc/PPP/PAP-secrets has world and/or group access
Sent [LCP confreq id = 0x1]
Rcvd [LCP confrej id = 0x1]
Sent [LCP confreq id = 0x2]
Rcvd [LCP confack id = 0x2]
Rcvd [LCP confreq id = 0x1]
Sent [LCP confack id = 0x1]
Rcvd [chap challenge id = 0x1, name = ""]
Warning-secret file/etc/PPP/chap-secrets has world and/or group access
Sent [chap response id = 0x1, name = "smsong"]
Rcvd [chap success id = 0x1 ""]
CHAP authentication succeeded
CHAP authentication succeeded
Sent [CCP confreq id = 0x1]
Sent [ipcp confreq id = 0x1]
Rcvd [LCP protrej id = 0x1 80 FD 01 01 00 0C 1A 04 78 00 18 04 78 00]
Protocol-reject for 'Compression control Protocol' (0x80fd) unbound ed
Rcvd [ipcp confreq id = 0x1]
Sent [ipcp confnak id = 0x1]
Rcvd [ipcp confrej id = 0x1]
Sent [ipcp confreq id = 0x2]
Rcvd [ipcp confreq id = 0x2]
Sent [ipcp confack id = 0x2]
Rcvd [ipcp confnak id = 0x2]
Sent [ipcp confreq id = 0x3]
Rcvd [ipcp confack id = 0x3]
Cocould not determine remote IP Address: defaulting to 10.64.64.64
Local IP address 10.144.202.159
Remote IP address 10.64.64.64
Primary DNS address 211.138.200.69
Secondary DNS address 211.103.13.101
Script/etc/PPP/IP-up started (PID 4578)
Script/etc/PPP/IP-up finished (PID 4578), status = 0x0
CTRL + C can be used to disconnect the connection. In this case, it is generally not good to test whether the connection is established. (in case of development failure, the console only has one reason.) You can remove/etc/PPP.
The nodetach parameter in the/peers/GPRS file. To use Ping, you need to disable eth0, which is the network port. In this way, ping the port to find out the outer route through the ppp0 port.
Network.
++ ++ ++
Run the tail-F/var/log/messages command to view the log:
Mar 20 20:55:55 localhost pppd [4557]: pppd 2.4.4 started by root, UID 0
Mar 20 20:55:56 localhost chat [4558]: timeout set to 15 seconds
Mar 20 20:55:56 localhost chat [4558]: Abort on (/nbusy/R)
Mar 20 20:55:56 localhost chat [4558]: Abort on (/Nno answer/R)
Mar 20 20:55:56 localhost chat [4558]: Abort on (/nringing/R/n/R/nringing/R)
Mar 20 20:55:56 localhost chat [4558]: timeout set to 40 seconds
Mar 20 20:55:56 localhost chat [4558]: Send (^ mat ^ m)
Mar 20 20:55:56 localhost chat [4558]: Wrong CT (OK)
Mar 20 20:55:56 localhost chat [4558]: ^ m
Mar 20 20:55:56 localhost chat [4558]: OK
Mar 20 20:55:56 localhost chat [4558]: -- Got it
Mar 20 20:55:56 localhost chat [4558]: Send (ats0 = 0 ^ m)
Mar 20 20:55:56 localhost chat [4558]: Wrong CT (OK)
Mar 20 20:55:56 localhost chat [4558]: ^ m
Mar 20 20:55:56 localhost chat [4558]: At ^ m
Mar 20 20:55:56 localhost chat [4558]: OK
Mar 20 20:55:56 localhost chat [4558]: -- Got it
Mar 20 20:55:56 localhost chat [4558]: Send (ate0v1 ^ m)
Mar 20 20:55:56 localhost chat [4558]: Wrong CT (OK)
Mar 20 20:55:56 localhost chat [4558]: ^ m
Mar 20 20:55:56 localhost chat [4558]: ^ m
Mar 20 20:55:56 localhost chat [4558]: OK
Mar 20 20:55:56 localhost chat [4558]: -- Got it
Mar 20 20:55:56 localhost chat [4558]: Send (at + cgdcont = 1, "ip", "cmnet" ^ m)
Mar 20 20:55:57 localhost chat [4558]: Wrong CT (OK)
Mar 20 20:55:57 localhost chat [4558]: ^ m
Mar 20 20:55:57 localhost chat [4558]: ats0 = 0 ^ m
Mar 20 20:55:57 localhost chat [4558]: OK
Mar 20 20:55:57 localhost chat [4558]: -- Got it
Mar 20 20:55:57 localhost chat [4558]: Send (atdt * 99 *** 1 # ^ m)
Mar 20 20:55:57 localhost chat [4558]: Round CT (CONNECT)
Mar 20 20:55:57 localhost chat [4558]: ^ m
Mar 20 20:55:57 localhost chat [4558]: ^ m
Mar 20 20:55:57 localhost chat [4558]: OK ^ m
Mar 20 20:55:57 localhost chat [4558]: ate0v1 ^ m
Mar 20 20:55:57 localhost chat [4558]: OK ^ m
Mar 20 20:55:57 localhost chat [4558]: ^ m
Mar 20 20:55:57 localhost chat [4558]: OK ^ m
Mar 20 20:55:57 localhost chat [4558]: ^ m
Mar 20 20:55:57 localhost chat [4558]: OK ^ m
Mar 20 20:55:57 localhost chat [4558]: ^ m
Mar 20 20:55:57 localhost chat [4558]: OK ^ m
Mar 20 20:55:57 localhost chat [4558]: ^ m
Mar 20 20:55:57 localhost chat [4558]: connect
Mar 20 20:55:57 localhost chat [4558]: -- Got it
Mar 20 20:55:57 localhost chat [4558]: Send (^ m)
Mar 20 20:55:57 localhost pppd [4557]: Serial Connection established.
Mar 20 20:55:57 localhost pppd [4557]: Using interface ppp0
Mar 20 20:55:57 localhost pppd [4557]: CONNECT: ppp0/dev/ttys0
Mar 20 20:55:58 localhost pppd [4557]: Warning-secret file/etc/PPP/PAP-secrets has world and/or group access
Mar 20 20:56:00 localhost pppd [4557]: Warning-secret file/etc/PPP/chap-secrets has world and/or group access
Mar 20 20:56:00 localhost pppd [4557]: CHAP authentication succeeded
Mar 20 20:56:00 localhost pppd [4557]: CHAP authentication succeeded
Mar 20 20:56:01 localhost kernel: PPP deflate compression module registered
Mar 20 20:56:02 localhost pppd [4557]: cocould not determine remote IP Address: defaulting to 10.64.64.64
Mar 20 20:56:02 localhost pppd [4557]: local IP address 10.144.202.159
Mar 20 20:56:02 localhost pppd [4557]: remote IP address 10.64.64.64
Mar 20 20:56:02 localhost pppd [4557]: primary DNS address 211.138.200.69
Mar 20 20:56:02 localhost pppd [4557]: Secondary DNS address 211.103.13.101
++ ++ ++
[Root @ localhost ~] # Ifconfig
Eth0 link encap: Ethernet hwaddr 00: 0a: EB: 91: 3B: C4
Up broadcast multicast MTU: 1500 Metric: 1
RX packets: 0 errors: 0 dropped: 0 overruns: 0 frame: 0
TX packets: 0 errors: 0 dropped: 0 overruns: 0 carrier: 0
Collisions: 0 FIG: 1000
RX Bytes: 0 (0.0 B) TX Bytes: 0 (0.0 B)
Interrupt: 209 base address: 0X4000
Lo link encap: local loopback
Inet ADDR: 127.0.0.1 mask: 255.0.0.0
Inet6 ADDR: 1/128 scope: Host
Up loopback running MTU: 16436 Metric: 1
RX packets: 1240 errors: 0 dropped: 0 overruns: 0 frame: 0
TX packets: 1240 errors: 0 dropped: 0 overruns: 0 carrier: 0
Collisions: 0 txqueuelen: 0
RX Bytes: 2039094 (1.9 MIB) TX Bytes: 2039094 (1.9 MIB)
Ppp0 link encap: Point-to-Point Protocol
Inet ADDR: 10.144.202.159 p-t-P: 10.64.64.64 mask: 255.255.255.255
Up pointopoint running noarp multicast MTU: 1500 Metric: 1
RX packets: 5 errors: 0 dropped: 0 overruns: 0 frame: 0
TX packets: 6 errors: 0 dropped: 0 overruns: 0 carrier: 0
Collisions: 0 txqueuelen: 3
RX Bytes: 62 (62.0 B) TX Bytes: 98 (98.0 B)
[Root @ localhost ~] # Ifconfig eth0 down
Disable the Ethernet interface eth0 so that it does not conflict with the route used by the ppp0 Interface
[Root @ localhost ~] # Ping 211.136.0000203
Ping 211.136.0000203 (211.136.0000203) 56 (84) bytes of data.
64 bytes from 211.136.0000203: icmp_seq = 1 TTL = 247 time = 3379 MS
64 bytes from 211.136.0000203: icmp_seq = 2 TTL = 247 time = 2388 MS
64 bytes from 211.136.0000203: icmp_seq = 3 TTL = 247 time = 2892 MS
64 bytes from 211.136.0000203: icmp_seq = 4 TTL = 247 time = 1952 MS
64 bytes from 211.136.0000203: icmp_seq = 5 TTL = 247 time = 1692 MS
64 bytes from 211.136.0000203: icmp_seq = 6 TTL = 247 time = 2112 MS
64 bytes from 211.136.0000203: icmp_seq = 7 TTL = 247 time = 1492 MS
64 bytes from 211.136.0000203: icmp_seq = 8 TTL = 247 time = 1472 MS
--- 211.136.20.203 Ping statistics ---
9 packets transmitted, 8 received, 11% packet loss, time 7999 Ms
RTT min/AVG/max/mdev = 1472.094/2172.525/3379.568/638.150 MS, pipe 4
At this time, if you can only ping a pure IP address, but cannot resolve the domain name, you may need to/etc/PPP/resolv. conf (the content is newly obtained
DNS replace) copy the content to/etc/resolv. conf or create a link to/etc/resolv. conf. In this way, you can ping the domain name and
Open the webpage.

[Root @ localhost ~] # Ping
Www.baidu.com
Ping
Www.a.shifen.com
(202.108.22.5) 56 (84) bytes of data.
64 bytes from 202.108.22.5: icmp_seq = 1 TTL = 50 time = 3142 MS
64 bytes from 202.108.22.5: icmp_seq = 2 TTL = 50 time = 3348 MS
64 bytes from 202.108.22.5: icmp_seq = 3 TTL = 50 time = 2796 MS
64 bytes from 202.108.22.5: icmp_seq = 4 TTL = 50 time = 3632 MS
64 bytes from 202.108.22.5: icmp_seq = 5 TTL = 50 time = 1936 MS
64 bytes from 202.108.22.5: icmp_seq = 7 TTL = 50 time = 909 MS
64 bytes from 202.108.22.5: icmp_seq = 6 TTL = 50 time = 1951 MS
64 bytes from 202.108.22.5: icmp_seq = 8 TTL = 50 time = 2839 MS
64 bytes from 202.108.22.5: icmp_seq = 9 TTL = 50 time = 1984 MS
64 bytes from 202.108.22.5: icmp_seq = 10 TTL = 50 time = 2404 MS
64 bytes from 202.108.22.5: icmp_seq = 11 TTL = 50 time = 1417 MS
---
Www.a.shifen.com
Ping statistics ---
12 packets transmitted, 11 received, 8% packet loss, time 13806 Ms
RTT min/AVG/max/mdev = 909.082/2396.720/3632.981/803.194 MS, pipe 4
++ ++
Another
In addition, if you want to enable automatic dial-up for Internet access when you are on the machine, you only need to start the script on your own boot (My Development Board is/etc/init. d/RCs, which has several types on the PC, such as:/etc
/Rc. Local file for link to CD
/Etc/rcN. d, n select to see the running level), add the following statement, note that the executable program in this script must provide the correct path, because it is just starting, environment Change of the entire machine
The volume is not set yet. Also, do not add the new command after it becomes a background process. It will be executed cyclically and will cause errors!
The following shell statements are added:
/Etc/PPP/rmlock # simply identify and delete the lock file of an invalid serial port to ensure successful dialing
/Usr/bin/pppd call GPRS # automatic dialing
/Usr/bin/sleep 20 # Set the dialing time for 20 s to check whether your module is successfully dialed.
/Bin/qtopia & # This is in the original script, and it is arranged in this order to enable the QT interface # after it is activated, it is nice that GPRS dialing has already created a number, then you can access the Internet.
/Sbin/ifconfig eth0 down # disable eth0 network port by default
Note: rmlock File
#/Etc/PPP/rmlock File
#! /Bin/sh
If [-F/var/lock/LCK .. s3c2410_serial1]; then
/Bin/Rm-F/var/lock/LCK .. s3c2410_serial1
Fi
How to solve pppd running segment errors:
When you manually interrupt the PPP link too many times, a segment error may occur during pppd operation,
The suggestion from Debian bug report solves this problem. It is
Pretty straightforward: simply delete/var/run/pppd. TDB file (in my
System, it is/var/run/pppd2.tdb ).
Conclusion: One of the dial-up methods is selected based on your environment and preferences. When the wvdial method is transplanted to the arm Development Board, there are many errors during cross-compilation. You can try it.
However, other operations require the support of the wvstreams library, which occupies a large space. In 2nd, the method is the most commonly used, but the error is more likely because it is more flexible. In 3rd and 2nd, the method class
. When an error occurs, you can search for the same error on Google. Refer to and modify your own parameters, and try again. You only need to stick to the problem! At that time, you had no time or question.
To learn about the internal dialing mechanism of PPP, we recommend that you use Windows to encapsulate it well. Stable and reliable! Haha

Good luck to PPP & Linux dialing friends!