Pantech UML290 on 4G drops link in 10-15 sec after PPP established (Linux)
ViktorP
Enthusiast - Level 2

I am trying to setup UML290 modem on the Linux server (no GUI) machine, I tried several ways but with the same result.

As first Modem itself works well under Windows 8 and Windows 7 using Verizon Manager software. So it is not HW issue with modem.

I tried 3 different PC with 3 different Linux distributives. Looks issue is not with Kernel or PC itself.

I tried "plain ppp" connection and WvDial  with the same result.

So problem is - ppp connection setup going well and actually setup connection. Computer even able to ping "big Internet" but then Verizon side send connection termination request. Could you help me?

syslog is below

Oct 14 23:25:31 beagle pppd[19953]: pppd 2.4.5 started by pva, uid 0

Oct 14 23:25:32 beagle chat[19955]: report (CONNECT)

Oct 14 23:25:32 beagle chat[19955]: abort on (BUSY)

Oct 14 23:25:32 beagle chat[19955]: abort on (VOICE)

Oct 14 23:25:32 beagle chat[19955]: abort on (NO CARRIER)

Oct 14 23:25:32 beagle chat[19955]: abort on (NO DIALTONE)

Oct 14 23:25:32 beagle chat[19955]: abort on (NO DIAL TONE)

Oct 14 23:25:32 beagle chat[19955]: send (ATZ^M)

Oct 14 23:25:32 beagle chat[19955]: expect (OK)

Oct 14 23:25:32 beagle chat[19955]: ^M

Oct 14 23:25:32 beagle chat[19955]: OK

Oct 14 23:25:32 beagle chat[19955]:  -- got it

Oct 14 23:25:32 beagle chat[19955]: send (ATE0v1&F&D2&C1&C2S0=0^M)

Oct 14 23:25:32 beagle chat[19955]: expect (OK)

Oct 14 23:25:32 beagle chat[19955]: ^M

Oct 14 23:25:32 beagle chat[19955]: ^M

Oct 14 23:25:32 beagle chat[19955]: OK

Oct 14 23:25:32 beagle chat[19955]:  -- got it

Oct 14 23:25:32 beagle chat[19955]: send (ATE0V1^M)

Oct 14 23:25:32 beagle chat[19955]: expect (OK)

Oct 14 23:25:32 beagle chat[19955]: ^M

Oct 14 23:25:32 beagle chat[19955]: ^M

Oct 14 23:25:32 beagle chat[19955]: OK

Oct 14 23:25:32 beagle chat[19955]:  -- got it

Oct 14 23:25:32 beagle chat[19955]: send (ATS7=60^M)

Oct 14 23:25:32 beagle chat[19955]: expect (OK)

Oct 14 23:25:32 beagle chat[19955]: ^M

Oct 14 23:25:32 beagle chat[19955]: ^M

Oct 14 23:25:32 beagle chat[19955]: OK

Oct 14 23:25:32 beagle chat[19955]:  -- got it

Oct 14 23:25:32 beagle chat[19955]: send (ATD*99***3#^M)

Oct 14 23:25:32 beagle chat[19955]: expect (CONNECT)

Oct 14 23:25:32 beagle chat[19955]: ^M

Oct 14 23:25:32 beagle chat[19955]: ^M

Oct 14 23:25:32 beagle chat[19955]: CONNECT

Oct 14 23:25:32 beagle chat[19955]:  -- got it

Oct 14 23:25:32 beagle chat[19955]: send (^M)

Oct 14 23:25:32 beagle pppd[19953]: Script /usr/sbin/chat -v -f /etc/chatscripts/3g -T *99***3# finished (pid 19954), status = 0x0

Oct 14 23:25:32 beagle pppd[19953]: Serial connection established.

Oct 14 23:25:33 beagle pppd[19953]: using channel 186

Oct 14 23:25:33 beagle pppd[19953]: Using interface ppp0

Oct 14 23:25:33 beagle pppd[19953]: Connect: ppp0 <--> /dev/ttyACM0

Oct 14 23:25:34 beagle pppd[19953]: sent [LCP ConfReq id=0x1 <asyncmap 0x0> <magic 0x2e570e2a> <pcomp> <accomp>]

Oct 14 23:25:34 beagle pppd[19953]: rcvd [LCP ConfReq id=0x66 <asyncmap 0x0> <auth chap MD5> <magic 0xdc081d87> <pcomp> <accomp>]

Oct 14 23:25:34 beagle pppd[19953]: sent [LCP ConfAck id=0x66 <asyncmap 0x0> <auth chap MD5> <magic 0xdc081d87> <pcomp> <accomp>]

Oct 14 23:25:34 beagle pppd[19953]: rcvd [LCP ConfAck id=0x1 <asyncmap 0x0> <magic 0x2e570e2a> <pcomp> <accomp>]

Oct 14 23:25:34 beagle pppd[19953]: sent [LCP EchoReq id=0x0 magic=0x2e570e2a]

Oct 14 23:25:34 beagle pppd[19953]: rcvd [LCP DiscReq id=0x67 magic=0xdc081d87]

Oct 14 23:25:34 beagle pppd[19953]: rcvd [CHAP Challenge id=0x1 <40cb33ef7051653164a9c5f2c060f48e>, name = "UMTS_CHAP_SRVR"]

Oct 14 23:25:34 beagle pppd[19953]: sent [CHAP Response id=0x1 <b2e99c088d9a46ff0a507f489b546a13>, name = "vzw4g"]

Oct 14 23:25:34 beagle pppd[19953]: rcvd [LCP EchoRep id=0x0 magic=0xdc081d87 2e 57 0e 2a]

Oct 14 23:25:34 beagle pppd[19953]: rcvd [CHAP Success id=0x1 ""]

Oct 14 23:25:34 beagle pppd[19953]: CHAP authentication succeeded

Oct 14 23:25:34 beagle pppd[19953]: CHAP authentication succeeded

Oct 14 23:25:34 beagle pppd[19953]: sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>]

Oct 14 23:25:34 beagle pppd[19953]: sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]

Oct 14 23:25:34 beagle pppd[19953]: rcvd [LCP ProtRej id=0x68 80 fd 01 01 00 0f 1a 04 78 00 18 04 78 00 15 03 2f]

Oct 14 23:25:34 beagle pppd[19953]: Protocol-Reject for 'Compression Control Protocol' (0x80fd) received

Oct 14 23:25:34 beagle pppd[19953]: rcvd [IPCP ConfReq id=0x24]

Oct 14 23:25:34 beagle pppd[19953]: sent [IPCP ConfNak id=0x24 <addr 0.0.0.0>]

Oct 14 23:25:34 beagle pppd[19953]: rcvd [IPCP ConfRej id=0x1 <compress VJ 0f 01>]

Oct 14 23:25:34 beagle pppd[19953]: sent [IPCP ConfReq id=0x2 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns2 0.0.0.0>]

Oct 14 23:25:34 beagle pppd[19953]: rcvd [IPCP ConfReq id=0x25]

Oct 14 23:25:34 beagle pppd[19953]: sent [IPCP ConfAck id=0x25]

Oct 14 23:25:34 beagle pppd[19953]: rcvd [IPCP ConfNak id=0x2 <addr 100.110.114.195> <ms-dns1 198.224.178.135> <ms-dns2 198.224.181.135>]

Oct 14 23:25:34 beagle pppd[19953]: sent [IPCP ConfReq id=0x3 <addr 100.110.114.195> <ms-dns1 198.224.178.135> <ms-dns2 198.224.181.135>]

Oct 14 23:25:34 beagle pppd[19953]: rcvd [IPCP ConfAck id=0x3 <addr 100.110.114.195> <ms-dns1 198.224.178.135> <ms-dns2 198.224.181.135>]

Oct 14 23:25:34 beagle pppd[19953]: Could not determine remote IP address: defaulting to 10.64.64.64

Oct 14 23:25:34 beagle pppd[19953]: local  IP address 100.110.114.195

Oct 14 23:25:34 beagle pppd[19953]: remote IP address 10.64.64.64

Oct 14 23:25:34 beagle pppd[19953]: primary   DNS address 198.224.178.135

Oct 14 23:25:34 beagle pppd[19953]: secondary DNS address 198.224.181.135

Oct 14 23:25:34 beagle pppd[19953]: Script /etc/ppp/ip-up started (pid 19965)

Oct 14 23:25:35 beagle vnstatd[13096]: Interface "ppp0" enabled.

Oct 14 23:25:35 beagle vnstatd[13096]: Error: Unable create database backup "/var/lib/vnstat/.wlan0".

Oct 14 23:25:35 beagle vnstatd[13096]: Error: Unable to write database, continuing with cached data.

Oct 14 23:25:35 beagle vnstatd[13096]: Database write possible again.

Oct 14 23:25:35 beagle vnstatd[13096]: Error: Unable create database backup "/var/lib/vnstat/.eth0".

Oct 14 23:25:35 beagle vnstatd[13096]: Error: Unable to write database, continuing with cached data.

Oct 14 23:25:35 beagle vnstatd[13096]: Database write possible again.

Oct 14 23:25:35 beagle dnsmasq[947]: reading /var/run/dnsmasq/resolv.conf

Oct 14 23:25:35 beagle dnsmasq[947]: using nameserver 198.224.181.135#53

Oct 14 23:25:35 beagle dnsmasq[947]: using nameserver 198.224.178.135#53

Oct 14 23:25:35 beagle pppd[19953]: Script /etc/ppp/ip-up finished (pid 19965), status = 0x0

Oct 14 23:25:36 beagle ntpd[2363]: Listen normally on 57 ppp0 100.110.114.195 UDP 123

Oct 14 23:25:36 beagle ntpd[2363]: peers refreshed

Oct 14 23:25:36 beagle ntpd[2363]: new interface(s) found: waking up resolver

----------------------------------

root@beagle:~# ping 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

64 bytes from 8.8.8.8: icmp_seq=1 ttl=52 time=47.9 ms

64 bytes from 8.8.8.8: icmp_seq=2 ttl=52 time=46.9 ms

64 bytes from 8.8.8.8: icmp_seq=3 ttl=52 time=53.7 ms

64 bytes from 8.8.8.8: icmp_seq=4 ttl=52 time=43.8 ms

64 bytes from 8.8.8.8: icmp_seq=5 ttl=52 time=43.2 ms

64 bytes from 8.8.8.8: icmp_seq=6 ttl=52 time=41.3 ms

64 bytes from 8.8.8.8: icmp_seq=7 ttl=52 time=48.3 ms

64 bytes from 8.8.8.8: icmp_seq=8 ttl=52 time=46.8 ms

64 bytes from 8.8.8.8: icmp_seq=9 ttl=52 time=47.3 ms

64 bytes from 8.8.8.8: icmp_seq=10 ttl=52 time=44.2 ms

64 bytes from 8.8.8.8: icmp_seq=11 ttl=52 time=43.4 ms

64 bytes from 8.8.8.8: icmp_seq=12 ttl=52 time=51.4 ms

64 bytes from 8.8.8.8: icmp_seq=13 ttl=52 time=48.3 ms

64 bytes from 8.8.8.8: icmp_seq=14 ttl=52 time=44.3 ms

ping: sendmsg: Network is unreachable

ping: sendmsg: Network is unreachable

ping: sendmsg: Network is unreachable

--------------------------------

Oct 14 23:25:50 beagle pppd[19953]: rcvd [LCP TermReq id=0x69]

Oct 14 23:25:50 beagle pppd[19953]: LCP terminated by peer

Oct 14 23:25:50 beagle pppd[19953]: Connect time 0.3 minutes.

Oct 14 23:25:50 beagle pppd[19953]: Sent 2758 bytes, received 2095 bytes.

Oct 14 23:25:50 beagle pppd[19953]: Script /etc/ppp/ip-down started (pid 20013)

Oct 14 23:25:50 beagle pppd[19953]: sent [LCP TermAck id=0x69]

Oct 14 23:25:50 beagle pppd[19953]: Script /etc/ppp/ip-down finished (pid 20013), status = 0x0

Oct 14 23:25:52 beagle ntpd[2363]: Deleting interface #57 ppp0, 100.110.114.195#123, interface stats: received=5, sent=5, dropped=0, active_time=16 secs

Oct 14 23:25:52 beagle ntpd[2363]: 69.50.219.51 interface 100.110.114.195 -> (none)

Oct 14 23:25:52 beagle ntpd[2363]: 168.235.71.66 interface 100.110.114.195 -> (none)

Oct 14 23:25:52 beagle ntpd[2363]: 129.6.15.29 interface 100.110.114.195 -> (none)

Oct 14 23:25:52 beagle ntpd[2363]: 67.18.187.111 interface 100.110.114.195 -> (none)

Oct 14 23:25:52 beagle ntpd[2363]: 91.189.94.4 interface 100.110.114.195 -> (none)

Oct 14 23:25:52 beagle ntpd[2363]: peers refreshed

Oct 14 23:25:53 beagle pppd[19953]: rcvd [LCP TermReq id=0x6a]

Oct 14 23:25:53 beagle pppd[19953]: sent [LCP TermAck id=0x6a]

Oct 14 23:25:53 beagle pppd[19953]: Connection terminated.

Oct 14 23:25:54 beagle pppd[19953]: Modem hangup

Oct 14 23:25:55 beagle vnstatd[13096]: Interface "ppp0" disabled.

Labels (1)
0 Likes
1 Solution

Correct answers
Re: Pantech UML290 on 4G drops link in 10-15 sec after PPP established (Linux)
ViktorP
Enthusiast - Level 2

Problem fixed, device works well under Linux.

To get it work you have to protect PPP link from garbage packets.

View solution in original post

0 Likes
Re: Pantech UML290 on 4G drops link in 10-15 sec after PPP established (Linux)
vzw_customer_support
Customer Service Rep

ViktorP,

Oh no! We are glad that you have reached out to us about this. We regret to see that you are having some issues with connecting. Has it ever connected to Linux before? From my end when I researched operating systems compatibility, Linux was not listed as a compatible system. Have you tested another device on a different Linux system to see if this has ever worked?

AliciaS_VZW
Follow us on Twitter @VZWSupport
If my response answered your question please click the �Correct Answer� button under my response. This ensures others can benefit from our conversation. Thanks in advance for your help with this!!

0 Likes
Re: Pantech UML290 on 4G drops link in 10-15 sec after PPP established (Linux)
ViktorP
Enthusiast - Level 2

No, It did not work before.

But it was updated on the Windows computer for the latest FW release, and word there excellent.

Unfortunately I have just one modem and it is UML290.

I have JetPack hotspot box it works well with the same SIM card , but it is another story..

I hate to have additional wifi link between computer and modem.

And based on my experience it looks like Verizon disconnects me intentionally.

rcvd [LCP TermReq id=0x69]

Do you have some special filters?

Does my computer should send something just after ppp link established (ping some address, send http request or so)?

as for me looks Verizon trying to proof something or have some additional authentication and disconnects link because timeout.

Please help me.

0 Likes
Re: Pantech UML290 on 4G drops link in 10-15 sec after PPP established (Linux)
ViktorP
Enthusiast - Level 2

Hello  People, looks I positionally fixed an issue.

I found that for some magic way my machine do not NAT some packets to the ppp interface and just forward them.

It means it sent packets with wrong IP addresses to verizon network and network dropped ppp link.

When i fixed this "wrong packets" i have got more or less stable link. but it still be dropped from verizon side.

Could you inform me, what else could be reason for verizon network to drop the call?

Now I have drops every 1-10 mins

0 Likes
Re: Pantech UML290 on 4G drops link in 10-15 sec after PPP established (Linux)
vzw_customer_support
Customer Service Rep

ViktorP,

This is certainly disheartening to hear that you are having connection issues. Let’s take a deeper look into things. As I mentioned before, the Linux systems are not compatible with the UML290 device. At this point are you not able to use this device with another system that is compatible? I’m going to send you a Private Message to gather more detailed information. Please respond back to me in the Private Message.

AliciaS_VZW
Follow us on Twitter @VZWSupport
If my response answered your question please click the �Correct Answer� button under my response. This ensures others can benefit from our conversation. Thanks in advance for your help with this!!

0 Likes
Re: Pantech UML290 on 4G drops link in 10-15 sec after PPP established (Linux)
ViktorP
Enthusiast - Level 2

Problem fixed, device works well under Linux.

To get it work you have to protect PPP link from garbage packets.

0 Likes
Re: Pantech UML290 on 4G drops link in 10-15 sec after PPP established (Linux)
TN-tux
Newbie

Viktor, how exactly did you do that, to "protect PPP link from garbage packets"?  Just an iptables OUTPUT rule?

I'm having the same issue with a UML295.  At first I chased the red herring of thinking this was the cause:

Oct 29 16:09:33 tp pppd[19330]: Protocol-Reject for 'Compression Control Protocol' (0x80fd) received

But I get the modem hangup even with "noccp" in pppd options.

My device works fine (yes, Alicia, 100% of my account usage has been under Linux, regardless of what Verizon is willing to say they "support") using cdc-ether and DHCP, but I am wishing to switch to an internal modem which does not have the cdc-ether option.

Also, Viktor, if you can share that chat script it would be nice (but I guess it's all there in the logs you showed, I will play around with that.)  Thank you.

0 Likes
Re: Pantech UML290 on 4G drops link in 10-15 sec after PPP established (Linux)
ViktorP
Enthusiast - Level 2

just for your information, I have nothing fancy in configs, actually BOLD line in iptables is most important. to prevent infinite disconnects.

/etc/ppp/peers/verizon_um290

user a

password v

connect "/usr/sbin/chat -v -f /etc/ppp/peers/verizon_um290_chat"

defaultroute

usepeerdns

ttyACM0

100000000

local

usepeerdns

debug

-detach

/etc/ppp/peers/verizon_um290_chat

'' 'ATZ'

'OK' 'ATDT*99***3#'

'CONNECT' ''

/etc/iptables.conf

# Generated by iptables-save v1.4.21 on Mon Oct 19 23:37:25 2015

*nat

:PREROUTING ACCEPT [1316:120407]

:INPUT ACCEPT [47:9693]

:OUTPUT ACCEPT [185:15205]

:POSTROUTING ACCEPT [38:3228]

-A POSTROUTING -o ppp0 -j MASQUERADE

COMMIT

# Completed on Mon Oct 19 23:37:25 2015

# Generated by iptables-save v1.4.21 on Mon Oct 19 23:37:25 2015

*filter

:INPUT ACCEPT [577:125409]

:FORWARD ACCEPT [0:0]

:OUTPUT ACCEPT [611:149969]

:INET_IN - [0:0]

:INET_OUT - [0:0]

-A INPUT -i ppp0 -j ACCEPT

-A FORWARD -s 192.168.4.0/24 -p tcp -m state --state INVALID -j DROP

-A FORWARD -s 192.168.4.0/24 -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK SYN -j TCPMSS --set-mss 1356

-A FORWARD -s 192.168.4.0/24 -i eth0 -o ppp0 -j ACCEPT

-A FORWARD -i ppp0 -o eth0 -j ACCEPT

COMMIT

# Completed on Mon Oct 19 23:37:25 2015

0 Likes