|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|
||||
First: it looks like some of the bits and pieces of "example" you found are apparently for Linux. OpenBSD doesn't have wlan0, /etc/network/devices, or use wpa_supplicant. Don't try to apply Linux management widgets to OpenBSD; the OSes may look similar but they have more differences than similarities.
Second, there's a man page for umsm(4). It contains some of the other bits and pieces from your example, and points you to other man pages, in particular, pppd(8) and ppp(4). The example configuration in the man page is also for the Cingular wireless ISP; your ISP, telcel, may have its own requirements and you should contact them regarding Point-to-Point provisioning. OpenBSD's FAQ 6 gives general network configuration guidance. However, it no longer covers Point-to-Point configurations specifically. |
|
||||
Here is a thread from the misc@ mailing list archives on provisioning a umsm device which may help.
http://marc.info/?t=142438133000007&r=1&w=2 |
|
||||
Ok, well thanks for the replies, I looked at the manual, and also here,:
http://www.openbsd.org/cgi-bin/man.c...th=OpenBSD-5.7 So I guess, but I am still completely confused, I need to either write or find scripts, Quote:
put in the scripts, once I have that I need to modify, all these files, ? So that all these scripts are in those files, ? Code:
FILES /var/run/pppn.pid Process-ID for pppd process on PPP interface unit n. /etc/ppp/pap-secrets Usernames, passwords and IP addresses for PAP authentication. This file should be owned by root and not readable or writable by any other user. pppd will log a warning if this is not the case. /etc/ppp/chap-secrets Names, secrets and IP addresses for CHAP authentication. As for /etc/ppp/pap-secrets, this file should be owned by root and not readable or writable by any other user. pppd will log a warning if this is not the case. /etc/ppp/options System default options for pppd, read before user default options or command-line options. ~/.ppprc User default options, read before /etc/ppp/options.ttyname. /etc/ppp/options.ttyname System default options for the serial port being used, read after ~/.ppprc. In forming the ttyname part of this filename, an initial /dev/ is stripped from the port name (if present), and any slashes in the remaining part are converted to dots. /etc/ppp/peers A directory containing options files which may contain privileged options, even if pppd was invoked by a user other than root. The system administrator can create options files in this directory to permit non-privileged users to dial out without requiring the peer to authenticate, but only to certain trusted peers. Last edited by PapaParrot; 14th August 2015 at 02:51 PM. |
|
||||
Garry,
I know, it's confusing. I'll try to net out how the pieces of the puzzle all fit together. As I don't have a PPP connection myself, some of the puzzle pieces may not be completely clear when I'm done. Please forgive me, also, if any of this is dull, useless review. --- The umsm(4) driver that appears in your dmesg is for serial modems that have a Qualcomm MSM chipset. These are found found in a variety of cellular devices, including yours. The umsm(4) man page warns that multiple devices may appear in your dmesg, and it is not always clear if it is device number 0 that is an active modem, or if it is one of the other device numbers. Your dmesg shows 4 different umsm devices, so some experimentation might be needed. PPP (Point-to-Point Protocol) is a way to exchange authentication (userid/pw) and IP address assignments over a serial connection, such as the umsm modem. The pppd(8) daemon is the tool that uses PPP to authenticate a connection, negotiate IP addressing and routing information, and maintain and manage the connection. The chat(8) command is used to script commands for serial modems. The ppp(4) driver is the network interface for PPP. The ifconfig(8) command is the provisioning and management tool for network interfaces. For example, a ppp(4) device can be created or destroyed by ifconfig. For other devices, such as Ethernet NICs, ifconfig may be used to set IP addresses, but for ppp(4) devices this is done with pppd(8). The hostname.if(5) files are used to configure network interfaces, used by netstart(8) at boot time. The example from the misc@ mailing list used "up" to create a ppp(4) device during boot. --- In the example scripts in the umsm(4) man page, we see a chat(8) script containing modem commands, a pppd(8) provisioning file, and a pppd(8) authentication file using CHAP -- Challenge Handshake Authentication Protocol -- the protocol required by Cingular Wireless when the example was written. (Cingular Wireless is now AT&T Mobility -- the example was written prior to 2007.) The first record in the example pppd file uses /dev/cuaU0, which would correspond with the first umsm device, umsm0. The second record is 115200 -- the speed of the modem being used. The third record enables debug, and from the fourth option downward ... are all settings needed for connection with Cingular, and for behavior of the connection: The ISP does not need to authenticate itself with the client. Hardware flow control is disabled. A recommended remote IP address was defined, which can be altered by the ISP, Cingular. The connection will be the default route to the Internet. The userid for this user at the ISP is defined. The connection will ignore NTP packets as a measure of demand or idle activity. Break the link after 10 minutes of idle activity. Remain running and re-establish the link if demand returns. Connect with the chat(8) script. The chat(8) script includes a blend of chat commands and modem commands. The chat commands are documented in the man page. The modem commands are not -- but they are the "AT" commands (or extensions) written for the Hayes modems in 1981, used by all modem manufacturers since the mid-1980s. --- As you can see, the specifics for PPP connections are partially under your control, and partially under the control of the ISP. This is why I recommended contacting your vendor. Only they can tell you what their requirements are. |
|
||||
While you are waiting for your ISP to answer your question, you can test your 4 umsm(4) devices with cu(1), and at least, find out which is the modem.
If your userid is in the dialer group you can issue these commands as a normal user. Otherwise, you'll need to be the superuser (sudo, su, etc.). $ cu -l /dev/cuaU0 -s 115200 can be used to initiate a conversation with a modem. If it is listening, and doing so at that baud rate. The ATZ command will issue a "reset" request, and if successful, the modem will reply with an OK message. To disconnect and return to the shell, in order to test /dev/cuaU1 through /dev/cuaU3, or to test with different baud rate, use a tilde and a period, "~." on a line by itself. If cu(1) fails to recognize it, you can use pkill(1) from another terminal window. |
|
||||
Thanks ,
Quote:
Quote:
A little off topic,but several years ago, when I first started useing this "telcel" and bought the modem, I had a lot of trouble getting it to work on linux, I tried contacting them, as soon as they realized I was using "linux", they said, "What is that ?", "It only works on windows" ,..end of story. However they were wrong, it works fine on linux, and I am sure it will on OpenBsd also, However, since it does work on my Debian system, and I am a little more familiar with where the various files are, I am pretty sure if I do some "digging", there, I can find the information I need. Since on Debian I use "network manager", I am pretty sure I can find the information I need in the files that network manger is using. Realizing, OpenBsd, is considerably different, but still the requirements of the ISP (vender) are the same, so all I need to do there is see what debian/network manager is using to meet those requirements. I have noticed, when I boot, it (openbsd) tries to establish a connection, it may be all it is missing is the "secrets" or password, if I can figure out where to put those. Thanks, for taking time on this, and no, don't feel it is useless, every little bit helps me get a better understanding of the entire process. ------------------------ A little off topic, but one reason I am having trouble using the manual, that is included in the OS, is my eyes are really bad, and even with glasses, it is very difficult to read,.. I have also been looking for a way, to increase the font size, in either the xterm, or just the shell, ideally both, on my debian, I am using a 24 pt, font in the bash shell, that is what it takes for me to be able to read it with glasses, with out the glasses, I still can't read it ! Similar, here, for the forum, I have the browser set to use very large fonts,..I did try a couple of things, but they didn't work, maybe this should be a priority, and I should have started a topic on that first,..these 2 things, the network, and the font size are really the only 2 problems I am having,.. -------------------------------------------------------------------------------------------------------------- Thanks |
|
||||
Quote:
Quote:
Quote:
Last edited by jggimi; 14th August 2015 at 06:31 PM. Reason: typos |
|
||||
A couple of years ago I considered switching over to one of these kind of Internet connections. At the end of the day, I didn't do it, but nevertheless spent some time investigating how/if it would work with Linux and BSD. That's possibly a bad combination to try to give help from, but there's an idea I wanted to add.
Quote:
If it's possible to access the cd-rom image, it might provide some clues. I don't know how to do that under OpenBSD. With Linux there is something called "usb_modeswitch" that is used. In order to get at these configuration files, it really doesn't matter what OS you use to do that, as long as you can find the files and extract some info from them. Since I didn't actually get such a modem, of course I never had a chance to experiment further. Possibly this idea might be helpful with a small part of the problem you're facing. Last edited by IdOp; 14th August 2015 at 11:37 PM. Reason: add an underscore |
|
||||
Good point. When I looked through misc@ archives, I did see some MSM devices presented logical CDs. And my Android phone will do that on command, if I tell it to "install PC software."
It's not obvious from the dmesg if "sd2" is a real USB storage device, or something presented by the cellular device. |
|
||||
Quote:
Something else I thought of , but just as I was leaving the house to do some errands, and I just now got back, I almost feel silly, I had not thought of it before, but since it does make a connection "automaticly" on the OpenBSD that I have on the VM, it seems like I should be able to find the files that have all the information, and maybe those will work as good examples or "templates" for me. Thanks , if anyone else does think of something more, it is welcome, and I will get back later, to let you all know what I find when I look at the settings,configurations that are on the OpenBsd,on the VM,..that seems like now, should have been the first thing to do, but I did not think of it until now. |
|
||||
Code:
but it is likely to be a virtual Ethernet NIC. If so, it won't have any PPP settings at all. A long time ago, I had something happen, and I had no desktop on the Debian system, so I didn't have the "network manager", GUI, icon, etc,...any way , I needed to establish a connection, in order to try to repair the system, so I used "nmcli", for the command line interface, for network manager, but I also needed to create a file on the ppp, I had found a example, somewhere, now I don't remember, but I did find the file I made, and when I used "nmcli" Code:
this worked: for usb broadband. nmcli nm wwan on nmcli con up uuid aed86e75-cb57-41b1-93a0-a493176d23af is not of much use, and at first it did not work, until I added this (below) to the PPP settings, or file I made, if I remember correctly, it is the "mobile_ppp", so anyway, it seems like if I can figure out where to put and how to "word" script or file, with the same, settings, and what to name the file, for OpenBsd to be able to use it,.. Code:
broadband-ppp.txt Description='Example PPP mobile connection' Interface=ttyUSB0 Connection=mobile_ppp # Use default route provided by the peer (default: true) DefaultRoute=true # Use DNS provided by the peer (default: true) UsePeerDNS=true # The user and password are not always required User='webgprs' Password='webgprs2002' # The access point name you are connecting to AccessPointName=internet.itelcel.com # If your device has a PIN code, set it here. Defaults to 'None' Pin=None # Mode can be one of 3Gpref, 3Gonly, GPRSpref, GPRSonly, None # These only work for Huawei USB modems; all other devices should use None Mode=3Gpref Code:
number (to dial) *99# user:webgprs APN: internet.itcel.com MCC:334 MNC:02 authentication protocal: PAP iterface: GSM (ttyUSB0) does not have that, also I am not positive of it is USB0 (zero) or USBO (the letter) they both look the same to me, my eyes are not helping me at all, ): Ok well for now that is about it, thanks from Garry |
|
|||
Quote:
__________________
Linux since 1999, & also a BSD user. |
|
||||
Each linux provisioning instruction will need to be adapted to OpenBSD. One at a time. Manually.
As an example, your question on whether it was "USB0" or "USBO" is moot. Neither would be used with this OS. Instead, the pppd(8) daemon will use one of four cua(4) calling units: /dev/cuaU0 through /dev/cuaU3, as I mentioned in post #5 and then further discussed in post #6, above. |
|
||||
Thanks,
Quote:
"notes" to follow, but was to tired to actually try much, things are making a little more sense to me though. Thanks |
|
||||
I use pppd and a USB modem to connect to the Internet. The main difference is that it's a conventional (POTS) one, rather than cellular like yours. A minor difference is that it's not on OpenBSD. As you work on this there may be places where I can help. pppd can seem daunting at first, but I think the things related to it should be doable in a fairly straightforward way, it just takes time and patience. I suspect the hardest part will be to find appropriate strings, for your ISP and modem, to place into your chat script. But you already seem to have some of this info, like the number to dial.
My advice at this point is to use the pppd(8) option call, which invokes a configuration file for a specific ISP that you've set up. See the man page, in particular the EXAMPLE section. Using call is probably the simplest way to get off the ground without having to write your own shell script to re-create this wheel. |
|
||||
Thanks,
I was able to access, Code:
cua(4) calling units: /dev/cuaU0 Quote:
when I ran the ATZ command, it did reply with OK, I have not looked at the other 3 yet, got interupted, Also have copied some things from the link to the pppd(8) manual, ( I don't have a printer), so, ...but any way, added some more things to my "notes" Quote:
|
|
||||
Ho-kay. I have attempted to build some possible configuration files. Possible, because I don't use PPP, and can't test them. I used information you provided, adapting the examples found in the umsm(4) man page.
Here is a peers file. You create the /etc/ppp/peers directory, then place a file like this one within it using any name you like, such as telcel, that you would use with the pppd daemon, with the call option shown in the umsm(4) man page, and Idop mentioned above. Example: # pppd call telcel I used your 'webgprs' userid and password. I set 5 minutes of idle time to disconnect with the ISP, rather than the 10 shown in the umsm(4) example, but you can change this as you need for your requirements. I've eliminated disabling of asynchronous flow control, which was in the example, because the modem default may work, whether that's enabled or disabled. The provisioning information you found on Debian didn't set it, so this might work without setting the option. Code:
# the calling unit in /dev: cuaU0 # baud rate 115200 # send debug information to /var/log/daemon debug # do not require the ISP to authenticate itself noauth # use this connection for the default route defaultroute # make this PPP connection when packets are outgoing, disconnect # when idle 5 minutes. If ntpd(8) is running, ignore its clock synchronization # packets for idle calculations. demand idle 600 active-filter 'not udp port 123' # don't shutdown if the connection goes idle persist # userid for PAP authentication user webgprs # modem commands to be sent when connecting connect "/usr/sbin/chat -v -f /etc/ppp/telcel-chat" Code:
# Secrets for authentication using PAP # client server secret IP addresses webgprs * webgprs2002 Code:
# time out if no responses after 10 seconds TIMEOUT 10 # report if connected REPORT CONNECT # terminate the script if the modem is busy, has no data link, or has an error ABORT BUSY ABORT 'NO CARRIER' ABORT ERROR # reset the modem, load factory defaults '' ATZ OK AT&F OK # define GPRS core network as the context, # see https://en.wikipedia.org/wiki/Hayes_command_set AT+CGDCONT=1,"IP","internet.itelcel.com" OK # dial ATD*99# CONNECT Last edited by jggimi; 15th August 2015 at 10:02 PM. Reason: typo. formatting. |
|
||||
Wow!, Thanks a bunch, I will try these, they look good, even if they do not work, (just now see this, so have not yet tried) but even if they don't work, it gives me something that now makes some sense, actually I have a feeling this will work, or at least I will be able to make any "adjustments" or changes if need be,..I will let you know how it goes later,...
This could be really useful to others as well in the future,.. thanks |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Plan 9 network configuration | gpatrick | Other OS | 1 | 27th January 2015 02:06 AM |
KVM Virtual Machine network configuration | J65nko | Other BSD and UNIX/UNIX-like | 3 | 2nd December 2014 06:00 AM |
Fedora 15 Changing The Network Device Naming Scheme | J65nko | News | 4 | 27th January 2011 12:30 PM |
Network Card Configuration | Freeco | FreeBSD Installation and Upgrading | 6 | 8th May 2010 11:11 AM |
Device-agnostic network interface | sean | OpenBSD General | 2 | 28th January 2010 06:24 PM |