Sponsored Content
Operating Systems Solaris Carrier Detection in Solaris 8 for Dial in and Null Modem Connections Post 302821297 by DGPickett on Friday 14th of June 2013 10:48:30 AM
Old 06-14-2013
Well, the loss of DSR or CTS or even effectively a break (long zero) might also be what is detected. An rs232 can be as little as three wires, SD, RD and ground, emulating a current loop connection. Does stty have other lead watchers you might turn on? Can you put a breakout box on and see what leads are live as senders or receivers, or just a volt-ohm-meter, as even receivers usually have voltage or resistance you can sense?
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Got connected with Modem but cannot dial Telephone no. to connect to host

Hello There, I configure my Modem as follow. Step1. # admintool & Then from Browse --> Serial Port i select tta port and Edit --> Modify From that i select Template : Modem:Dial Out Baud Rate: 9600 Ok Step 2 # tip /dev/cua/a connected (1 Reply)
Discussion started by: abidmalik
1 Replies

2. UNIX for Dummies Questions & Answers

Hyperterminal null modem connection to Solaris

I am new to Unix. I just got my SUN box from ebay with Solaris supposedly preloaded. The problem is I am unable to connect via Hyperterminal to Solaris, or more to the point, cannot tell if I have a successful connection and that solaris is the one not properly booted up. I hooked up a null... (3 Replies)
Discussion started by: seethams
3 Replies

3. UNIX for Dummies Questions & Answers

Dial-Up Modem

Im using Kinternet with a Lucent modem on Suse 9.0 Ive installed the ltmodem driver and suse says the device is ready and configured. Ive configured it at /dev/ttyS0 This is the log that Kinternet gives after trying to connect: SuSE Meta pppd (smpppd-ifcfg), Version 1.06 on linux. Status... (0 Replies)
Discussion started by: Synbios
0 Replies

4. SCO

Dial-Out & Dial-In Connections in OpenServer 5.0.6.

Friends, I am facing a problem in connecting two SCO Openserver 5.0.6 servers through Dial-Up connectivity as is done in the case of two Windows PCs. Please help me out with the following problems: (a) How to configure the modem? (b) How to setup a Dial-In connection? (c) How to... (1 Reply)
Discussion started by: thecobolguy
1 Replies

5. Solaris

null modem for testing

hi all.. sorry for repeating the same question many times, i just set up a null modem, i am using this as reference : DB25 DB9 -- - 2 TD ---- 2 RD 3 RD ---- 3 TD 4 RTS ---- 8 CTS 5 CTS ---- 7 RTS 7 GND ---- 5 GND 6 DSR -+ +--- 4 DTR 8... (0 Replies)
Discussion started by: waterbear
0 Replies

6. Solaris

help me!!!! how configure modem dial up with smc in solaris 10

Dear All, i have problem during install modem dial up with smc in solaris 10. i can't find "login" because it's stop in _receive started transmit started. thanks for your attention. this is the list during i dial to this number : altconn called Device Type ACU wanted... (0 Replies)
Discussion started by: mr.ridho
0 Replies

7. IP Networking

modem detection

How to get information that where is my modem configured in /dev. I have two modems configured in my device .. one is USB and other is PCI modem.. USB is detected as /dev/USB0. but how to see about PCI modem? (0 Replies)
Discussion started by: s123.radha
0 Replies

8. UNIX for Advanced & Expert Users

Modem (dial up) connecton to Unix machine

Hello to all, I have one problem and hope you'll be able to help me. It's about connecting Windows PC machine to Unix machine via dial up through Hyper terminal. Connection was working in the past. In the meantime, windows machine is replaced (win XP) and unix machine stayed as is. So nothing is... (1 Reply)
Discussion started by: Mick
1 Replies

9. BSD

Carrier Detection in FreeBSD

Regarding carrier detection on FreeBSD 9.1 being run within Virtual Box: I used a usb-serial dongle which shows up as ttyu0 on the BSD machine. Carrier detection appears to work. When I establish a null modem connection I receive a login prompt. If I login, and then unplug and plug back the... (2 Replies)
Discussion started by: rstor
2 Replies
WVDIAL.CONF(5)							File Formats Manual						    WVDIAL.CONF(5)

NAME
wvdial.conf - wvdial configuration file DESCRIPTION
When wvdial starts, it first loads its configuration from /etc/wvdial.conf, which contains basic information about the modem port, speed, and init string, along with information about your Internet Service Provider (ISP), such as the phone number, your username, and your pass- word. The configuration file /etc/wvdial.conf is in Windows "ini" file format, with sections named in square brackets and a number of variable = value pairs within each section. Here is a sample configuration file: [Dialer Defaults] Modem = /dev/ttyS2 Baud = 57600 Init = ATZ Init2 = AT S11=50 Phone = 555-4242 Username = apenwarr Password = my-password [Dialer phone2] Phone = 555-4243 [Dialer shh] Init3 = ATM0 [Dialer pulse] Dial Command = ATDP The sample configuration file above contains all of the options necessary to run the two sample command lines given above. Here is a com- plete list of settings that wvdial understands: Modem The location of the device that wvdial should use as your modem. The default is /dev/modem. Baud The speed at which wvdial will communicate with your modem. The default is 57600 baud. Init1 ... Init9 wvdial can use up to nine initialization strings to set up your modem. Before dialing, these strings are sent to the modem in numerical order. These are particularly useful when specifying multiple sections. See above for an example that uses Init3 to turn the modem's speaker off. The default is "ATZ" for Init1. Phone The phone number you want wvdial to dial. You can add up to 9 other phone numbers that wvdial will dial in order, by adding: Phone1 Phone2 Phone3 Phone4 Phone5 Phone6 Phone7 Phone8 Phone9 Dial Prefix wvdial will insert this string after the dial command and before the phone number. For example, to disable call waiting (in North America, anyway) set this to "*70,". Dial Command wvdial will use this string to tell the modem to dial. The default is "ATDT". Username You must set this to the username you use at your ISP. Login Prompt If your ISP has an unusual login procedure that wvdial is unable to figure out, you can use this option to specify a login prompt. When this prompt is received from your ISP, wvdial will send the Login string. Password You must set this to the password you use at your ISP. Ask Password By setting this option wvdial will prompt for your password on every dialin. Thus you don't have to save your password in /etc/wvdial.conf. (Option added by SuSE.) Password Prompt If your ISP has an unusual login procedure that wvdial is unable to figure out, you can use this option to specify a password prompt. When this prompt is received from you ISP, wvdial will send the Password string. PPPD Path If your system has pppd somewhere other than /usr/sbin/pppd, you will need to set this option. Auto DNS Try to get the Domain Nameserver (DNS) from the provider. This option is "on" by default. (Option added by SuSE.) Check DNS Check the Domain Nameserver (DNS) after the connection has been set up. This option is "on" by default. (Option added by SuSE.) DNS Test1 First DNS lookup for DNS check. (Option added by SuSE.) DNS Test2 Second DNS lookup for DNS check. (Option added by SuSE.) Check Def Route Check the default route after the connection has been set up. This option is "on" by default. (Option added by SuSE.) Force Address This option only applies if you have a static IP address at your ISP, and even then you probably don't need it. Some ISP's don't send the IP address as part of the PPP negotiation. This option forces pppd to use the address you give it. Remote Name If your ISP uses PAP or CHAP authentication, you might need to change this to your ISP's authentication name. In most cases, how- ever, it's safe to use the default value, "*". Carrier Check wvdial checks your modem during the connection process to ensure that it is actually online. If you have a weird modem that insists its carrier line is always down, you can disable the carrier check by setting this option to "no". Stupid Mode When wvdial is in Stupid Mode, it does not attempt to interpret any prompts from the terminal server. It starts pppd immediately after the modem connects. Apparently there are ISP's that actually give you a login prompt, but work only if you start PPP, rather than logging in. Go figure. Stupid Mode is (naturally) disabled by default. New PPPD You need this option if you have pppd version 2.3.0 or newer, to make wvdial create the file /etc/ppp/peers/wvdial. This option is enabled by default, thus if you have older pppd you need to set it to `no' (or upgrade pppd). Default Reply When wvdial detects a prompt, and it hasn't seen any clues that indicate what it should send as a response to the prompt, it defaults to sending "ppp". Sometimes this is inadequate. Use this option to override wvdial's default prompt response. Auto Reconnect If enabled, wvdial will attempt to automatically reestablish a connection if you are randomly disconnected by the other side. This option is "on" by default. Idle Seconds Set the hangup timeout in seconds. If there is inactivity for the given time the connection is shut down. A hangup timeout of 0 disables this feature. Abort on Busy If enabled, wvdial will not retry the connection if the modem says that the line is busy. This option is "off" by default. Abort on No Dialtone If enabled, wvdial will not retry the connection if the modem says that there is no dialtone. This option is "on" by default. Dial Attempts If value is set, wvdial will quit after that many tries .If set to 0, wvdial will happily keep dialling forever. Dial Timeout The maximum time in seconds that wvdial will wait for a connection to be made. Default value is 60 seconds. The wvdialconf(1) program can be used to detect your modem and fill in the Modem, Baud, and Init/Init2 options automatically. AUTHORS
Dave Coombs and Avery Pennarun for Net Integration Technologies Inc. Great contributions have been made by many people, including SuSE and RedHat. Thanks guys! SEE ALSO
wvdial(1), wvdialconf(1), pppd(8). WvDial December 2005 WVDIAL.CONF(5)
All times are GMT -4. The time now is 02:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy