I'm happy someone answered and I'm not talking to myself. I finally had a 

1) How to get two ways communication to succeed with this or these devices? 
Overall, how any IoT usb modem is connected with static IP-address?

I have tried  ipfw forward and tcpdump to snoop the traffic from ue0. I have 
put ipfw to forward all incoming packets to httpd-server. Both http and https. 
I can not see any traffic coming in from the modem The forward 
rule is:

${fwcmd} add 100 fwd ${wwwip},80 tcp from any to 80 recv ${outif}
${fwcmd} add 100 fwd ${wwwip},443 tcp from any to 443 recv ${outif}

This works with the proxy.
This is not excactly NAT but no packets are found with ' tcpdump -n -i ue0 ' 
either. The modem has a www -admin page at I could not 
reach it's address from the Internet but sending to the public NAT address, 
finally the admin -page loaded to the web browser. Trying with google translate 
did not give results. Trying with another IP-connection did not reach the IP at 

1.1) Should I enable PPP -link over the connection somehow? PPP was the 
connection method with the previous usb-modems and the IP at tun0 interface was 
given from the service provider.

2) Does anyone know how to switch the E3372 modem to a state giving a device to 
use the AT-commands? With these commands, listing the available modes is 
possible and solving the possibilities to use the modem revealed.

Devices now are:
crw-------   1 root  operator  0xd1 Apr 17 21:26 pass3
crw-r-----   1 root  operator  0xd2 Apr 17 21:26 da0
lrwxr-xr-x   1 root  wheel        9 Apr 17 21:26 ugen4.2 -> usb/4.2.0
crw-rw-rw-   1 root  wheel     0xc6 Apr 17 22:46 dsp0.0
crw-------   1 root  wheel      0x4 Apr 18 00:07 console
crw-rw-rw-   1 root  wheel      0xd Apr 18 00:33 null

3) What is a correct IoT modem type? Is PPP ok with static IP-addresses or does 
it have to have NAT capabilities? Which ones have this?

Answear to the question: Sorry my inaccuracy. It just seems to me that the 
latency is higher from just using the web browser. I have so many tests going 
on that I just haven't tested more accurately. Today I have been using the link 
first time with an antenna. The results would have been inaccurate.  
Personnally I think it can be either block sizes or differences in locking the 
cdce versus the u3g cuaU. Really I do not know. Maby these are the usual? Is it 
better to leave the modem to an external device or use it with the web browsers 
and applications? By the way, I'm using only 2 cores. This one uses less power. 
Maby it can affect the results?Maby it's just the antenna. E3372 has two 
antenna links. A polarized antenna or two antennas far apart could give better 

This is the configuration:  <ue0> <--- cdce/usb ---> <modem interface>   <------ 
ISP 4G ------> <public IP>

It is not possible to add a NAT address to the Huawei modem because it does not 
have this kind of capability? At least not from the Admin-page. Or does it just 
send the packets destined to to network ? Tcpdump 
showed that nothing came back using the SSL-ports. With HTTP the public IP 
appeared many times until it was switched (maby with http redirect or similar?) 
back to the Admin page The URL was first<the public IP> .

Do I have to buy a new modem and what kind of a modem it should be?

br,   Jouni

On Sunday, April 17, 2016 9:56 PM, Adrian Chadd <adr...@freebsd.org> wrote:

>hi! this is cool to know! any ideas why the latency is higher?
>On 16 April 2016 at 13:44, Jouni Laakso via freebsd-wireless
><freebsd-wireless@freebsd.org> wrote:
>> Hello list,
>> I wanted to send this information to help others in their quest of 4G 
>> connectivity with FreeBSD here at Europes continent and in Finland. Huawei 
>> does not include a lot of information about their products. These 4G-network 
>> modems are usually provided by the subscriberline companies and with their 
>> own products. This one was from Sonera (Teliasonera, .se and .fi) here in 
>> Finland.
>> Huawei E3372 seems to be a CDCE device. /boot/loader.conf has to have a line 
>> if_cdce_load="YES". Only usb_modeswitch works with this one. Command:
>> /usr/local/sbin/usb_modeswitch --default-vendor 0x12d1 --default-product 
>> 0x1f01 -J
>> swithes to the CDCE mode. Device ue0 appears to be configured (with ifconfig 
>> -command). Using 'dhclient ue0' a network address is found and using the 
>> address and adding a default router the network interface is usable. An 
>> admin HTTP-page can be found from CDCE has two network 
>> interfaces at both ends of USB. Both ends can be configured with their own 
>> IP-address.
>> ID:s   idVendor = 0x12d1 idProduct = 0x1f01 are switched to ID:s idVendor = 
>> 0x12d1  idProduct = 0x14dc . This seems to be correct since the connection 
>> to the Internet succeeded with cdce.
>> Causes the modem to appear as a device id 0x1442 . Using this, only NTP port 
>> was listening. Maby this is a ntp mode. Using:U3G_DEV(HUAWEI, E3372_INIT, 
>> does not give any results. These are the current possibilities if compiling 
>> a new kernel every time is possible.
>> It would be easier if a device had only one identification code. Reading 
>> about the different codes from usb_modeswitch list, it is maby clear that 
>> the service provider can change the device ID:s. This is not very easy to 
>> the users. If the device was only a modem, it  would be usable without the 
>> flip-flop states of the modem-devices. ISO image is given with Windows and 
>> Linux drivers or software and after installing the software, the state 
>> becomes a modem state. Possibly with a HTTP-interface to connecto to the 
>> Internet.
>> Quick test with Linux shows that the latency time is less with Linux. 
>> Previously using PPP with these kind of wireless devices, FreeBSD has shown 
>> best latency times. This is an estimate. Using an external modem (propably 
>> Linux inside) caused more latency with PPP over the previous 3G link.
>> With best regards,
>> Jouni L.
>> _______________________________________________
>> freebsd-wireless@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-wireless
>> To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org
freebsd-wireless@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"

Reply via email to