Stephen, I can give you an example but it is for Vodafone UK and you will almost certainly need to alter the chat script to play out the interactions required by your service provider.
You should be able to find that data from the web if you search for an example of the scripts that wvdial uses to interact with your specific service provider and map the interactions into the Solaris chat script. The concepts used are similar, see: http://linux.about.com/od/commands/l/blcmdl5_wvdialc.htm My Vodaphone example follows. HTH -George The chat script for 3G dialout on Vodafone UK /etc/ppp/chat-vodafone ====================== ABORT BUSY ABORT 'NO CARRIER' ABORT ERROR REPORT CONNECT '' 'ATZ' SAY "Calling Vodafone n" 'OK' 'ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0' 'OK' 'AT+CGDCONT=1,"IP","internet"' 'OK' 'ATD*99#' CONNECT '' The pppd config file to call the chat script and associate it with the right device. /etc/ppp/peers/vodafone ======================= /dev/nokia 1382400 idle 7200 lock crtscts modem noauth defaultroute user "web" password 1 connect "/usr/bin/chat -Vv -t15 -f /etc/ppp/chat-vodafone" noipdefault usepeerdns novj nodetach noccp georges-home:/etc/ppp/peers % more /etc/ppp/chat-vodafone ABORT BUSY ABORT 'NO CARRIER' ABORT ERROR REPORT CONNECT '' 'ATZ' SAY "Calling Vodafone n" 'OK' 'ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0' 'OK' 'AT+CGDCONT=1,"IP","internet"' 'OK' 'ATD*99#' CONNECT '' In my case /dev/nokia is hand linked, your underlying term entry may well be different. Determine that by using the tip command to each term and trying the AT command set to see which of them give an OK in response, ie.. # tip /dev/term/3 connected AT OK ~. # Then create the link, mine looks like this. lrwxrwxrwx 1 root root 11 Dec 4 11:11 /dev/nokia -> /dev/term/3 Startup via a gnome launcher if you wish, specify this command in the launcher props. pfexec pppd call vodafone Stephen Nelson-Smith wrote: > I have a PCMCIA GPRS card which I use every day to connect to the 'net > while commuting. Under OpenSolaris (snv_101b) I see it appear as a > device when I plug it in: > > Apr 16 02:02:23 helium usba: [ID 691482 kern.warning] WARNING: > /pci at 0,0/pci8086,2448 at 1e/pci103c,3080 at 9/pci1931,a at 0 (ohci0): No > SOF > interrupts have been received, this USB OHCI hostcontroller is > unusable > Apr 16 02:02:23 helium genunix: [ID 936769 kern.info] ohci1 is > /pci at 0,0/pci8086,2448 at 1e/pci103c,3080 at 9/pci1931,b at 0,1 > Apr 16 02:02:23 helium genunix: [ID 408114 kern.info] > /pci at 0,0/pci8086,2448 at 1e/pci103c,3080 at 9/pci1931,b at 0,1 (ohci1) > online > Apr 16 02:02:23 helium usba: [ID 912658 kern.info] USB 1.10 device > (usbaf0,6300) operating at full speed (USB 1.x) on USB 1.10 root hub: > device at 1, usb_mid1 at bus address 2 > Apr 16 02:02:23 helium usba: [ID 349649 kern.info] Option N.V. Fusion > UMTS Quad-GPRS > Apr 16 02:02:23 helium genunix: [ID 936769 kern.info] usb_mid1 is > /pci at 0,0/pci8086,2448 at 1e/pci103c,3080 at 9/pci1931,b at 0,1/device at 1 > Apr 16 02:02:23 helium genunix: [ID 408114 kern.info] > /pci at 0,0/pci8086,2448 at 1e/pci103c,3080 at 9/pci1931,b at 0,1/device at 1 > (usb_mid1) online > > Under Linux, I use wvdial - I don't understand how it works - I just > developed a recipe that works by trial and error. Having googled, it > seems that wvdial isn't ported to OpenSolaris, but that the pppd > should just work, if I knew how to configure it. > > Where do I start? > > S. >
