Hello,
I tried to use a Huawei E1823 UMTS-Stick on a debian8-laptop with wvdial and pppd to connect to a nano3G for getting an IP/Internet-connection via UMTS/HSDPA. The setup is mainly as described on http://osmocom.org/projects/cellular-infrastructure/wiki/Getting_Started_wit....
When using an android-Smartphone with the same configuration of the ggsn and the other components the IP/Internet-connection is working.
After pppd is started from wvdial it receives his local IP-address from the "net 192.168.99.0/24" parameter of ggsn.conf and also the configured DNS-Server, but no remote-IP, so 10.64.64.64 is used by pppd as a default value:
... --> local IP address 192.168.99.5 --> pppd: �[7f] --> remote IP address 10.64.64.64 --> pppd: �[7f] --> primary DNS address 8.8.8.8 --> pppd: �[7f]
..which results in an unusable ppp0-device: ppp0 Link encap:Point-to-Point Protocol inet addr:192.168.99.5 P-t-P:10.64.64.64 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
Has anybody successfully used an UMTS-Stick with ggsn? How can I tell ggsn to send his IP-Adress, which can be used by pppd as "remote IP address"? Are there special options for pppd which I have to use?
thanks and greetings,
Andreas
Hi Andreas,
first of all congratulations to get the setup running and to reproduce the current status of the Osmocom 3G support.
On Mon, Apr 03, 2017 at 07:50:32AM +0200, Andreas Mueller wrote:
After pppd is started from wvdial it receives his local IP-address from the "net 192.168.99.0/24" parameter of ggsn.conf and also the configured DNS-Server, but no remote-IP, so 10.64.64.64 is used by pppd as a default value:
This is very odd. Please include a protocol trace of the Iuh interface.
On Mon, Apr 03, 2017 at 07:50:32AM +0200, Andreas Mueller wrote:
After pppd is started from wvdial it receives his local IP-address from the "net 192.168.99.0/24" parameter of ggsn.conf and also the configured DNS-Server, but no remote-IP, so 10.64.64.64 is used by pppd as a default value:
... --> local IP address 192.168.99.5 --> pppd: �[7f] --> remote IP address 10.64.64.64 --> pppd: �[7f] --> primary DNS address 8.8.8.8 --> pppd: �[7f]
I know a whole while back we tried unsuccessfully to use an UMTS "stick" to test data services, but never got it to work. We saw the same: smart phone works fine, UMTS stick fails to establish data.
You might be onto the reason there, would be great if you could help us resolve this!
Has anybody successfully used an UMTS-Stick with ggsn? How can I tell ggsn to send his IP-Adress, which can be used by pppd as "remote IP address"? Are there special options for pppd which I have to use?
I don't really know and would have to look into it in detail. It would be great if you could try to understand what's going on from traces and/or openggsn code and/or openbsc code...
Maybe we somehow send the wrong or incomplete configuration and maybe smart phones have some magic to work around it, which UMTS sticks don't?
~N
Hi Andreas,
Could you provide a pcap of the Create PDP Request and Response exchange between SGSN and GGSN?
Regards Andreas
----- On Apr 3, 2017, at 7:50 AM, Andreas Mueller andreas.mueller@criticallabs.org wrote:
Hello,
I tried to use a Huawei E1823 UMTS-Stick on a debian8-laptop with wvdial and pppd to connect to a nano3G for getting an IP/Internet-connection via UMTS/HSDPA. The setup is mainly as described on http://osmocom.org/projects/cellular-infrastructure/wiki/Getting_Started_wit....
When using an android-Smartphone with the same configuration of the ggsn and the other components the IP/Internet-connection is working.
After pppd is started from wvdial it receives his local IP-address from the "net 192.168.99.0/24" parameter of ggsn.conf and also the configured DNS-Server, but no remote-IP, so 10.64.64.64 is used by pppd as a default value:
... --> local IP address 192.168.99.5 --> pppd: �[7f] --> remote IP address 10.64.64.64 --> pppd: �[7f] --> primary DNS address 8.8.8.8 --> pppd: �[7f]
..which results in an unusable ppp0-device: ppp0 Link encap:Point-to-Point Protocol inet addr:192.168.99.5 P-t-P:10.64.64.64 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
Has anybody successfully used an UMTS-Stick with ggsn? How can I tell ggsn to send his IP-Adress, which can be used by pppd as "remote IP address"? Are there special options for pppd which I have to use?
thanks and greetings, Andreas
Hallo,
unfortunately I have very limited time during the next days, but I can do further testing on friday and will provide you with the pcap- and logfiles.
greetings,
Andreas
On Mon, Apr 03, 2017 at 03:29:56PM +0200, Andreas Schultz wrote:
Hi Andreas,
Could you provide a pcap of the Create PDP Request and Response exchange between SGSN and GGSN?
Regards Andreas
----- On Apr 3, 2017, at 7:50 AM, Andreas Mueller andreas.mueller@criticallabs.org wrote:
Hello,
I tried to use a Huawei E1823 UMTS-Stick on a debian8-laptop with wvdial and pppd to connect to a nano3G for getting an IP/Internet-connection via UMTS/HSDPA. The setup is mainly as described on http://osmocom.org/projects/cellular-infrastructure/wiki/Getting_Started_wit....
When using an android-Smartphone with the same configuration of the ggsn and the other components the IP/Internet-connection is working.
After pppd is started from wvdial it receives his local IP-address from the "net 192.168.99.0/24" parameter of ggsn.conf and also the configured DNS-Server, but no remote-IP, so 10.64.64.64 is used by pppd as a default value:
... --> local IP address 192.168.99.5 --> pppd: �[7f] --> remote IP address 10.64.64.64 --> pppd: �[7f] --> primary DNS address 8.8.8.8 --> pppd: �[7f]
..which results in an unusable ppp0-device: ppp0 Link encap:Point-to-Point Protocol inet addr:192.168.99.5 P-t-P:10.64.64.64 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
Has anybody successfully used an UMTS-Stick with ggsn? How can I tell ggsn to send his IP-Adress, which can be used by pppd as "remote IP address"? Are there special options for pppd which I have to use?
thanks and greetings, Andreas
Hello,
today the UMTS-USB-stick established a successfull IP-connection on the first attempt, but further attempts failed. When comparing packet-dumps of a successful and a failed connection-attempt and looking and the RANAP and GTP-packages I saw, that on the failed connection-attempts the UMTS-Stick is not authorized and on the successful attempt at first a location-update is made and then the authentification, which succeeds. Adding the command "AT+CREG" to wvdial.conf seems to solve the problem. Then I can see an "Routing Area Update Request" which is rejected then the authorization happens (Attach, Identity, Authentication) and the IP-connection is successfully established!
Here is a working wvdial.conf for the huawei E1823:
[Dialer Defaults] Init1 = AT^U2DIAG=0 Init2 = AT+CREG Init3 = ATZ Init4 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 Init5 = AT+CGDCONT=1,"IP","web.blubb.xy" Modem Type = Analog Modem Baud = 9600 New PPPD = yes Modem = /dev/ttyUSB0 Stupid mode = 1 ISDN = 0 Phone = *99# Password = none Username = none
It takes very long (>30 seconds) until ppp0 receives the IP-config but afterwards it is working with 6625 kBit/s down- and 580kBit/s upstream.
greetings,
Andreas
I won't have time for some days, but this looks like someone should verify this. I'm still wondering why a "Routing Area Update Request" is rejected, so some clarification could also be good...
And we should incorporate this information on our wiki; I see that it is mentioned on https://osmocom.org/projects/cellular-infrastructure/wiki/Accelerate3g5_--_a... but at least when this is verified/clarified we should incorporate it in https://osmocom.org/projects/cellular-infrastructure/wiki/Getting_Started_wi...
Many thanks so far, Andreas!
I also noticed from your Accelerate3g5 page that the getting started guide lacks the creation of the hlr.db. I added this to the main guide now (but used the new default db name of 'hlr.db').
~N
On Fri, Apr 07, 2017 at 07:52:15PM +0200, Andreas Mueller wrote:
Hello,
today the UMTS-USB-stick established a successfull IP-connection on the first attempt, but further attempts failed. When comparing packet-dumps of a successful and a failed connection-attempt and looking and the RANAP and GTP-packages I saw, that on the failed connection-attempts the UMTS-Stick is not authorized and on the successful attempt at first a location-update is made and then the authentification, which succeeds. Adding the command "AT+CREG" to wvdial.conf seems to solve the problem. Then I can see an "Routing Area Update Request" which is rejected then the authorization happens (Attach, Identity, Authentication) and the IP-connection is successfully established!
Here is a working wvdial.conf for the huawei E1823:
[Dialer Defaults] Init1 = AT^U2DIAG=0 Init2 = AT+CREG Init3 = ATZ Init4 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0 Init5 = AT+CGDCONT=1,"IP","web.blubb.xy" Modem Type = Analog Modem Baud = 9600 New PPPD = yes Modem = /dev/ttyUSB0 Stupid mode = 1 ISDN = 0 Phone = *99# Password = none Username = none
It takes very long (>30 seconds) until ppp0 receives the IP-config but afterwards it is working with 6625 kBit/s down- and 580kBit/s upstream.
greetings,
Andreas
-
Andreas Mueller -
Andreas Schultz -
Harald Welte -
Neels Hofmeyr