Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi,
My modem is external USB 2.0 Fax dial up modem, and use the chat script in debian squeeze to connect to my isp, the chat script can establish a connection successfully, i check the connection with:
Quote:
bash -c "tail -f /var/log/messages"
there are time to time these messages:
Quote:
Nov 22 11:41:58 user chat[4548]: alarm
Nov 22 11:41:58 user chat[4548]: send (AT^M)
Nov 22 11:41:58 user chat[4548]: expect (OK)
Nov 22 11:48:49 user chat[5097]: alarm
Nov 22 11:48:49 user chat[5097]: Failed
Nov 22 11:49:21 user chat[5173]: abort on (BUSY)
Nov 22 11:49:21 user chat[5173]: abort on (NO CARRIER)
Nov 22 11:49:21 user chat[5173]: abort on (VOICE)
Nov 22 11:49:21 user chat[5173]: abort on (NO DIALTONE)
Nov 22 11:49:21 user chat[5173]: abort on (NO DIAL TONE)
Nov 22 11:49:21 user chat[5173]: abort on (NO ANSWER)
Nov 22 11:49:21 user chat[5173]: abort on (DELAYED)
Nov 22 11:49:21 user chat[5173]: send (ATZ^M)
Nov 22 11:49:21 user chat[5173]: expect (OK)
Nov 22 11:50:06 user chat[5173]: alarm
Nov 22 11:50:06 user chat[5173]: send (AT^M)
i check the chat process with:
Quote:
ps aux | grep chat
root 5031 0.0 0.0 1796 504 pts/0 S 11:43 0:00 sh -c /usr/sbin/chat -v -f /etc/chatscripts/inse
root 5032 0.0 0.0 1732 428 pts/0 S 11:43 0:00 /usr/sbin/chat -v -f /etc/chatscripts/inse
Is it normal the chat script should run as a process or close after establish a connection, and what are above messages?
thanks for reply, i know these are commands to modem by chat script, but question is why after connection chat should send these commands to modem, and is chat should run after connection established or just should exit?
It's been a long time since I've had to deal with this, but, if I remember, every time you send or receive something across the modem connection, there has to be an accompanying command to the modem so it knows what to do with or in response to the data.
Back to your other question, one would not normally expect a chat session to close spontaneously after the connection is made, but *&^&^$0***$88&^%[NO CARRIER].
In other words, it can happen due to interference, faulty equipment, or other legitimate reasons.
Perhaps someone with more recent experience with AT commands will help us out here.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.