Unstable connection PPP with Huawei E3372, E3272
-
Hi,
I have a problem with an unstable connection using modem E3372 or E3272. The connection is until it starts to generate more traffic. Pfasene stops provide internet even though the LED diode on modem indicates connection (still lit, does not blink). After restarting PfSesne (virtual machine) everything is back to normal. PPP connection is used as WAN. I am using default pFsense configuration, fresh installation.
My configuration:
Hardware: HP Microserver Gen8
Modem test 1: Huawei E3372h-153 switch to E3372 stick modem-mode
Modem test 2: Huawei E3272s-153 switch to E3272 stick modem-mode
Test on USB 2.0 and 3.0 port
OS Hypervisor: VMware ESXi 6.5 U1 (Build 7388607)
OS VM: FreeBSD 11.1-RELEASE-p6 + PfSense 2.4.2-RELEASE-p1 (instalation from iso appliance)
Installed Open VM Tools (installed package 10.1.0,1)Any idea to solve this problem?
Best Regards,
Robert -
What is the status of the ppp connection when it stops working? What does the ppp log show?
Can you test it on a non-virtualised install?
Steve
-
I suggest to focus on 3372. Make sure your USB port is capable to provide enough current, 3272 requires more than 3372.
In some cases those modems were working better when connected via relatively short (~15-20cm) extension cable instead of being plugged into the port directly.I'm +1 for testing on a non-virtualized install.
-
1. I attach the following logs:
Mar 20 19:55:03 ppp [wan] IPV6CP: state change Initial --> Starting Mar 20 19:55:03 ppp [wan] IPV6CP: LayerStart Mar 20 19:55:03 ppp [wan] IPCP: Up event Mar 20 19:55:03 ppp [wan] IPCP: state change Starting --> Req-Sent Mar 20 19:55:03 ppp [wan] IPCP: SendConfigReq #1 Mar 20 19:55:03 ppp [wan] IPADDR 0.0.0.0 Mar 20 19:55:03 ppp [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Mar 20 19:55:03 ppp [wan] PRIDNS 0.0.0.0 Mar 20 19:55:03 ppp [wan] SECDNS 0.0.0.0 Mar 20 19:55:03 ppp [wan] IPV6CP: Up event Mar 20 19:55:03 ppp [wan] IPV6CP: state change Starting --> Req-Sent Mar 20 19:55:03 ppp [wan] IPV6CP: SendConfigReq #1 Mar 20 19:55:03 ppp [wan] IPCP: rec'd Configure Request #1 (Req-Sent) Mar 20 19:55:03 ppp [wan] IPCP: SendConfigAck #1 Mar 20 19:55:03 ppp [wan] IPCP: state change Req-Sent --> Ack-Sent Mar 20 19:55:03 ppp [wan] IPCP: rec'd Configure Nak #1 (Ack-Sent) Mar 20 19:55:03 ppp [wan] IPCP: SendConfigReq #2 Mar 20 19:55:03 ppp [wan] IPADDR 0.0.0.0 Mar 20 19:55:03 ppp [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Mar 20 19:55:03 ppp [wan] PRIDNS 0.0.0.0 Mar 20 19:55:03 ppp [wan] SECDNS 0.0.0.0 Mar 20 19:55:03 ppp [wan_link0] LCP: rec'd Protocol Reject #2 (Opened) Mar 20 19:55:03 ppp [wan_link0] LCP: protocol IPV6CP was rejected Mar 20 19:55:03 ppp [wan] IPV6CP: protocol was rejected by peer Mar 20 19:55:03 ppp [wan] IPV6CP: state change Req-Sent --> Stopped Mar 20 19:55:03 ppp [wan] IPV6CP: LayerFinish Mar 20 19:55:03 ppp [wan] IPCP: rec'd Configure Reject #2 (Ack-Sent) Mar 20 19:55:03 ppp [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid Mar 20 19:55:03 ppp [wan] IPCP: SendConfigReq #3 Mar 20 19:55:03 ppp [wan] IPADDR 0.0.0.0 Mar 20 19:55:03 ppp [wan] PRIDNS 0.0.0.0 Mar 20 19:55:03 ppp [wan] SECDNS 0.0.0.0 Mar 20 19:55:03 ppp [wan] IPCP: rec'd Configure Nak #3 (Ack-Sent) Mar 20 19:55:03 ppp [wan] IPADDR 77.115.84.99 Mar 20 19:55:03 ppp [wan] 77.115.84.99 is OK Mar 20 19:55:03 ppp [wan] PRIDNS 212.2.96.51 Mar 20 19:55:03 ppp [wan] SECDNS 212.2.96.52 Mar 20 19:55:03 ppp [wan] IPCP: SendConfigReq #4 Mar 20 19:55:03 ppp [wan] IPADDR 77.115.84.99 Mar 20 19:55:03 ppp [wan] PRIDNS 212.2.96.51 Mar 20 19:55:03 ppp [wan] SECDNS 212.2.96.52 Mar 20 19:55:03 ppp [wan] IPCP: rec'd Configure Ack #4 (Ack-Sent) Mar 20 19:55:03 ppp [wan] IPADDR 77.115.84.99 Mar 20 19:55:03 ppp [wan] PRIDNS 212.2.96.51 Mar 20 19:55:03 ppp [wan] SECDNS 212.2.96.52 Mar 20 19:55:03 ppp [wan] IPCP: state change Ack-Sent --> Opened Mar 20 19:55:03 ppp [wan] IPCP: LayerUp Mar 20 19:55:03 ppp [wan] 77.115.84.99 -> 10.64.64.0 Mar 20 19:55:04 ppp [wan] IFACE: Up event Mar 20 19:55:04 ppp [wan] IFACE: Rename interface ng0 to ppp0
2. I tested on an active USB hub. Unfortunately, no changes.
3. I tested on a USB cable (0.5 m length). Unfortunately, no changes.
4. Attempt to install on a physical machine ends with an installer error. Error occurs before he is to boot into the installer menu (maybe because of the soft-raid controller).
Best Regards,
Robert -
Everything is working now. I changed processor to a more powerful with VT-d support. I added via VMDirectPath I/O passtrough USB 3.0 chip to virtual machine and connected modem.
-
Thanks for reporting back :)
-
Thanks for reporting back :)
You're welcome.
Thank you for help on the forum. PfSense is very cool :)
-
@robertw Hi Robert, Im a newbie to pfSense and Im trying to implement my own pfSense using Huawei E3372h-607 as in stick mode as well. And Im having trouble with dial PPP for the 3G modem. Here's my current configuration:
- Bus /dev/usb Device /dev/ugen1.3: ID 12d1:1c05 Huawei Technologies Co., Ltd. Broadband stick (modem on)
- ugen1.3: <HUAWEIMOBILE HUAWEIMOBILE> at usbus1
u3g0 on uhub1
u3g0: <HUAWEIMOBILE HUAWEIMOBILE, class 0/0, rev 2.10/1.02, addr 3> on usbus1
u3g0: Found 3 ports. (which are /dev/cuaU0.0, 0.1 and 0.2)*
Though I can't manage to get it to receive IP address
Any help is appreciated, thank you in advanced!
-
What have you tried so far? What was the result?
https://www.netgate.com/docs/pfsense/cellular/configuring-3g-modems.html
Steve
-
Hi Stephen, thank you for replying. So far I have flash the modem with firmware 21.x and connect it with pfSense 2.4.3 exactly like the document said. I even issued AT setport command with “FF; 10,12,16”. Still I can’t get pfSense to dial ppp correctly. I checked the log and sometimes see IPADDR 0.0.0.0 DNS 0.0.0.0 etc. I’ve been scratching my head for a few days with this problem.
-
Ok, so it is detected by pfSense and u3g attaches to it. And the 3 usb serial devices are created?
And at least one of them responds to AT commands?
But you can't actually dial out?I think we will need to see some log excerpts. It sounds like it's mostly working though, maybe some quirk with your provider.
Steve
-
@stephenw10 yeah, at least that's what I thought. I used the cuaU0.0 to dial AT command. I started to think there's a problem with the firmware version I flashed it with. And btw, I flashed another device and I get the error: cannot get device information. Any help is appreciated! Thank you so much Stephen
-
Did you try all three ports? It's not necessarily the first one that provides modem access.
Steve