<div dir="ltr"><div><div><div><div>So I was able to connect to both Verizon and Sprint using PPP and wvDial. I did this using Sprint's instructions from<br><a href="http://www4.sprint.com/pcsbusiness/downloads/Sprint_Mobile_Broadband_Setup_Guide.pdf">http://www4.sprint.com/pcsbusiness/downloads/Sprint_Mobile_Broadband_Setup_Guide.pdf</a>, which boiled down to<br> changing /etc/wvdial.conf to:<br><br>[Dialer Defaults]<br>Modem = /dev/ttyUSB0<br>Baud = 460800<br>Init1 = ATZ<br>Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0<br>ISDN = 0<br>Modem Type = USB Modem<br>Phone = #777<br> Username = ''<br>Password = ''<br>Carrier Check = no<br>Stupid Mode = 1<br><br></div>and then wvDialing....<br><br>[eric@linux-vn1z ~/modem]$ sudo wvdial<br>--> WvDial: Internet dialer version 1.61<br>--> Cannot get information for serial port.<br> --> Initializing modem.<br>--> Sending: ATZ<br>OK<br>--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0<br>ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0<br>OK<br>--> Modem initialized.<br>--> Sending: ATDT#777<br> --> Waiting for carrier.<br>ATDT#777<br>CONNECT<br>--> Carrier detected. Starting PPP immediately.<br>--> Starting pppd at Thu Mar 13 17:37:02 2014<br>--> Pid of pppd: 28332<br>--> Using interface ppp0<br> --> pppd: �[7f]<br>--> pppd: �[7f]<br>--> pppd: �[7f]<br>--> local IP address 184.232.199.246<br>--> pppd: �[7f]<br>--> remote IP address 66.1.12.193<br>--> pppd: �[7f]<br>--> primary DNS address 66.1.13.7<br> --> pppd: �[7f]<br>--> secondary DNS address 68.29.1.7<br>--> pppd: �[7f]<br>--> Script /etc/ppp/ip-up run successful<br>--> Default route Ok.<br>--> Nameserver (DNS) Ok.<br>--> Connected... Press Ctrl-C to disconnect<br> --> pppd: �[7f]<br><br>I am seeing 2 occasional issues, 1 minor, the other major:<br><br></div>1. Sometimes the DNS fails on PPP connection. I've set /etc/sysconfig/network/config<br></div>setting NETCONFIG_DNS_STATIC_SERVERS="8.8.8.8 4.4.4.4", to fall back on Google's DNS.<br> <br></div>[eric@linux-vn1z ~]$ sudo wvdial<br>--> WvDial: Internet dialer version 1.61<br>--> Initializing modem.<br>--> Sending: ATZ<br>OK<br>--> Sending: ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0<br>ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0<br> OK<br>--> Modem initialized.<br>--> Sending: ATDT#777<br>--> Waiting for carrier.<br>ATDT#777<br>CONNECT<br>--> Carrier detected. Starting PPP immediately.<br>--> Starting pppd at Fri Mar 14 16:12:18 2014<br> --> Pid of pppd: 1993<br>--> Using interface ppp0<br>--> pppd: p[7f]<br>--> pppd: p[7f]<br>--> local IP address 75.220.118.4<br>--> pppd: p[7f]<br>--> remote IP address 66.174.192.64<br>--> pppd: p[7f]<br> --> primary DNS address 198.224.160.135<br>--> pppd: p[7f]<br>--> secondary DNS address 198.224.164.135<br>--> pppd: p[7f]<br>--> Script /etc/ppp/ip-up run successful<br>--> Default route Ok.<br><b>--> warning, no nameserver found `/etc/resolv.conf`<br> --> Nameserver (DNS) failure, the connection may not work.</b><br>--> Connected... Press Ctrl-C to disconnect<br>--> pppd: p[7f]<br><div><div><div><br><br>2. "Modem not responding" error, it happens pretty often, maybe 30-40% of the time. If I retry 2-4 times it usually connects.<br> <br>[eric@linux-vn1z ~]$ sudo wvdial<br>--> WvDial: Internet dialer version 1.61<br>--> Initializing modem.<br>--> Sending: ATZ<br>--> Sending: ATQ0<br>--> Re-Sending: ATZ<br><b>--> Modem not responding.</b><br> <br></div><div>The "Modem not responding" error is much more important to me to fix, as I can always work around the DNS issue. Any insights are appreciated. Or if this is normal on these networks, that would be good to know too.<br> </div><div>Thanks!<br><br></div><div><br></div></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Mar 13, 2014 at 5:14 PM, Eric Johnson <span dir="ltr"><<a href="mailto:eric@minutekey.com" target="_blank">eric@minutekey.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Hi Aleksander,<br></div>Wow, that python script sounds awesome, if you have a chance to finish it. <br> <br>I'm going to try to get pppd going, next. Then Verizon and DHCP or static IP I'm guessing.<br> Thank!<span class="HOEnZb"><font color="#888888"><br></font></span></div><span class="HOEnZb"><font color="#888888">Eric<br></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote"> On Thu, Mar 13, 2014 at 4:31 PM, Aleksander Morgado <span dir="ltr"><<a href="mailto:aleksander@aleksander.es" target="_blank">aleksander@aleksander.es</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hey!<br> <div><div><br> On Thu, Mar 13, 2014 at 6:28 PM, Eric Johnson <<a href="mailto:eric@minutekey.com" target="_blank">eric@minutekey.com</a>> wrote:<br> > [eric@linux-vn1z ~]$ mmcli -b 0<br> > Bearer '/org/freedesktop/ModemManager1/Bearer/0'<br> > -------------------------<br> > Status | connected: 'yes'<br> > | suspended: 'no'<br> > | interface: 'ttyUSB0'<br> > | IP timeout: '20'<br> > -------------------------<br> > Properties | apn: 'none'<br> > | roaming: 'allowed'<br> > | IP type: 'none'<br> > | user: 'none'<br> > | password: 'none'<br> > | number: '#777'<br> > | Rm protocol: 'unknown'<br> > -------------------------<br> > IPv4 configuration | method: 'ppp'<br> > -------------------------<br> > IPv6 configuration | method: 'unknown'<br> ><br> > [eric@linux-vn1z ~]$ mmcli -m 0 --list-bearers<br> ><br> > Found 1 bearers:<br> ><br> > /org/freedesktop/ModemManager1/Bearer/0<br> ><br> > [eric@linux-vn1z ~]$ wvdialconf<br> > Editing `/etc/wvdial.conf'.<br> ><br> > Scanning your serial ports for a modem.<br> <br> </div></div>Everything went ok until this point. So, mmcli lets you get the port<br> in connected state; that's how far ModemManager goes. Still, there is<br> another step that needs to be done, which is the IP setup in the data<br> port (which would usually be done by e.g. NetworkManager). There<br> currently are three main cases, and what you need to look at is the<br> Bearer properties that you get when MM tells you you're connected<br> (i.e. the "mmcli -b 0" output):<br> <br> Case 1) tty port<br> If the bearer tells you to use a tty as data port and use PPP, you<br> need to launch pppd on that tty, passing APN auth details among other<br> things.<br> <br> Case 2) net port, dhcp<br> If the bearer tells you to use a net port as data port and use DHCP,<br> you need to bring the interface up and launch a DHCP client in that<br> interface.<br> <br> Case 3) net port, static<br> If the bearer tells you to use a net port as data port and 'static'<br> config, it will also give you what IP address configuration (IP,<br> netmask..) you need to configure in the net port. So you'll need to<br> bring the interface up, and then setup those details in the interface.<br> <br> Interestingly, I was bored last Monday and started to write a python<br> app (called it 'mm-online', I'm no good inventing new names) which<br> will do exactly all that (just not using mmcli); it will use<br> libmm-glib via GObject-introspection to call SimpleConnect() and then<br> (this not yet done) prepare the connection following the steps I said<br> earlier. This would allow a 'standalone' operation of ModemManager<br> (i.e. without a higher level connection manager like NetworkManager).<br> <span><font color="#888888"><br> <br> --<br> Aleksander<br> <a href="https://aleksander.es" target="_blank">https://aleksander.es</a><br> </font></span></blockquote></div><br></div> </div></div></blockquote></div><br></div>