Pfsense and huawei ME909s-120



  • Hello all,
    i've got apu 2.C4 mainboard with Huawei ME909s-120 LTE module.

    I have problem with LTE stability and conneciton. When it's connected i see problems with dns resolution, for example when i pings google, 3 of 4 attempts fails and after that its working for some time, sometimes….

    My PC dns is pfsense, and my pfsense dns server are dns from LTE provider. When i configure google's dns i cannot ping nothing. But communication using IP's seems to be working.

    My second problem is when my LTE connection is broken or when I force disconnect, my pfsence cant connect second time to LTE provider and i got message in logs: The modem is not responding to "AT" at ModemCmd: label..

    Has anyone know solution for ME909s-120 to work with pfsense? It is possible?





  • Tkanks AndrewZ for reply.

    The init string: Z seems to solve almost all my problems. Now I can connect to LTE on demand or pfsense is now auto reconnecting when link is down.

    But I have still problems with DNS. When my PC has DNS set to pfsense i cannot resolve even microsoft.com, but from shell or web gui pfsense can resolve it!

    When my PC has external LTE provider DNS it seems to be ok, I can ping everything i think… - still testing.
    Logs from PPP:

    Mar 18 14:08:54 ppp [wan_link0] CHAP: Using authname "user"
    Mar 18 14:08:54 ppp [wan_link0] CHAP: sending RESPONSE #1 len: 25
    Mar 18 14:08:54 ppp [wan_link0] CHAP: rec'd SUCCESS #1 len: 13
    Mar 18 14:08:54 ppp [wan_link0] MESG: Welcome!!
    Mar 18 14:08:54 ppp [wan_link0] LCP: authorization successful
    Mar 18 14:08:54 ppp [wan_link0] Link: Matched action 'bundle "wan" ""'
    Mar 18 14:08:54 ppp [wan_link0] Link: Join bundle "wan"
    Mar 18 14:08:54 ppp [wan] Bundle: Status update: up 1 link, total bandwidth 150000000 bps
    Mar 18 14:08:54 ppp [wan] IPCP: Open event
    Mar 18 14:08:54 ppp [wan] IPCP: state change Initial –> Starting
    Mar 18 14:08:54 ppp [wan] IPCP: LayerStart
    Mar 18 14:08:54 ppp [wan] IPV6CP: Open event
    Mar 18 14:08:54 ppp [wan] IPV6CP: state change Initial –> Starting
    Mar 18 14:08:54 ppp [wan] IPV6CP: LayerStart
    Mar 18 14:08:54 ppp [wan] IPCP: Up event
    Mar 18 14:08:54 ppp [wan] IPCP: state change Starting –> Req-Sent
    Mar 18 14:08:54 ppp [wan] IPCP: SendConfigReq #1
    Mar 18 14:08:54 ppp [wan] IPADDR 0.0.0.0
    Mar 18 14:08:54 ppp [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Mar 18 14:08:54 ppp [wan] IPV6CP: Up event
    Mar 18 14:08:54 ppp [wan] IPV6CP: state change Starting –> Req-Sent
    Mar 18 14:08:54 ppp [wan] IPV6CP: SendConfigReq #1
    Mar 18 14:08:54 ppp [wan] IPCP: rec'd Configure Request #1 (Req-Sent)
    Mar 18 14:08:54 ppp [wan] IPCP: SendConfigAck #1
    Mar 18 14:08:54 ppp [wan] IPCP: state change Req-Sent –> Ack-Sent
    Mar 18 14:08:54 ppp [wan] IPCP: rec'd Configure Nak #1 (Ack-Sent)
    Mar 18 14:08:54 ppp [wan] IPCP: SendConfigReq #2
    Mar 18 14:08:54 ppp [wan] IPADDR 0.0.0.0
    Mar 18 14:08:54 ppp [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Mar 18 14:08:54 ppp [wan_link0] LCP: rec'd Protocol Reject #2 (Opened)
    Mar 18 14:08:54 ppp [wan_link0] LCP: protocol IPV6CP was rejected
    Mar 18 14:08:54 ppp [wan] IPV6CP: protocol was rejected by peer
    Mar 18 14:08:54 ppp [wan] IPV6CP: state change Req-Sent –> Stopped
    Mar 18 14:08:54 ppp [wan] IPV6CP: LayerFinish
    Mar 18 14:08:54 ppp [wan] IPCP: rec'd Configure Reject #2 (Ack-Sent)
    Mar 18 14:08:54 ppp [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Mar 18 14:08:54 ppp [wan] IPCP: SendConfigReq #3
    Mar 18 14:08:54 ppp [wan] IPADDR 0.0.0.0
    Mar 18 14:08:54 ppp [wan] IPCP: rec'd Configure Nak #3 (Ack-Sent)
    Mar 18 14:08:54 ppp [wan] IPADDR 10.151.169.208
    Mar 18 14:08:54 ppp [wan] 10.151.169.208 is OK
    Mar 18 14:08:54 ppp [wan] IPCP: SendConfigReq #4
    Mar 18 14:08:54 ppp [wan] IPADDR 10.151.169.208
    Mar 18 14:08:54 ppp [wan] IPCP: rec'd Configure Ack #4 (Ack-Sent)
    Mar 18 14:08:54 ppp [wan] IPADDR 10.151.169.208
    Mar 18 14:08:54 ppp [wan] IPCP: state change Ack-Sent –> Opened
    Mar 18 14:08:54 ppp [wan] IPCP: LayerUp
    Mar 18 14:08:54 ppp [wan] 10.151.169.208 -> 10.64.64.0
    Mar 18 14:08:54 ppp [wan] IFACE: Up event
    Mar 18 14:08:54 ppp [wan] IFACE: Rename interface ng0 to ppp0

    (on firewall was full of block entries)

    To resolve this problem I had disabled:

    Block private networks and loopback addresses
    Block bogon networks
    DNS Server Override
    IPV6

    and:
    Set external DNS of my LTE provider on pfsense
    Set pfsense IP address as my PC DNS

    But when i ping microsoft.com or something my DNS server cannot still resolve this.

    My IPv4 Address: 100.81.210.104
    Subnet mask IPv4: 255.255.255.255
    Gateway IPv4: 10.64.64.0
    DNS servers:
        1. 127.0.0.1
        2. 89.108.195.20
        3. 89.108.195.21
        4. 89.108.202.21
        5. 185.89.185.1
    MTU:1492

    Now my PPP logs are like below, and in firewall logs i see nothing special.

    Mar 18 14:25:07 ppp [wan_link0] CHAP: Using authname "user"
    Mar 18 14:25:07 ppp [wan_link0] CHAP: sending RESPONSE #1 len: 25
    Mar 18 14:25:07 ppp [wan_link0] CHAP: rec'd SUCCESS #1 len: 13
    Mar 18 14:25:07 ppp [wan_link0] MESG: Welcome!!
    Mar 18 14:25:07 ppp [wan_link0] LCP: authorization successful
    Mar 18 14:25:07 ppp [wan_link0] Link: Matched action 'bundle "wan" ""'
    Mar 18 14:25:07 ppp [wan_link0] Link: Join bundle "wan"
    Mar 18 14:25:07 ppp [wan] Bundle: Status update: up 1 link, total bandwidth 150000000 bps
    Mar 18 14:25:07 ppp [wan] IPCP: Open event
    Mar 18 14:25:07 ppp [wan] IPCP: state change Initial –> Starting
    Mar 18 14:25:07 ppp [wan] IPCP: LayerStart
    Mar 18 14:25:07 ppp [wan] IPV6CP: Open event
    Mar 18 14:25:07 ppp [wan] IPV6CP: state change Initial –> Starting
    Mar 18 14:25:07 ppp [wan] IPV6CP: LayerStart
    Mar 18 14:25:07 ppp [wan] IPCP: Up event
    Mar 18 14:25:07 ppp [wan] IPCP: state change Starting –> Req-Sent
    Mar 18 14:25:07 ppp [wan] IPCP: SendConfigReq #1
    Mar 18 14:25:07 ppp [wan] IPADDR 0.0.0.0
    Mar 18 14:25:07 ppp [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Mar 18 14:25:07 ppp [wan] IPV6CP: Up event
    Mar 18 14:25:07 ppp [wan] IPV6CP: state change Starting –> Req-Sent
    Mar 18 14:25:07 ppp [wan] IPV6CP: SendConfigReq #1
    Mar 18 14:25:07 ppp [wan] IPCP: rec'd Configure Request #1 (Req-Sent)
    Mar 18 14:25:07 ppp [wan] IPCP: SendConfigAck #1
    Mar 18 14:25:07 ppp [wan] IPCP: state change Req-Sent –> Ack-Sent
    Mar 18 14:25:07 ppp [wan] IPCP: rec'd Configure Nak #1 (Ack-Sent)
    Mar 18 14:25:07 ppp [wan] IPCP: SendConfigReq #2
    Mar 18 14:25:07 ppp [wan] IPADDR 0.0.0.0
    Mar 18 14:25:07 ppp [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Mar 18 14:25:07 ppp [wan_link0] LCP: rec'd Protocol Reject #2 (Opened)
    Mar 18 14:25:07 ppp [wan_link0] LCP: protocol IPV6CP was rejected
    Mar 18 14:25:07 ppp [wan] IPV6CP: protocol was rejected by peer
    Mar 18 14:25:07 ppp [wan] IPV6CP: state change Req-Sent –> Stopped
    Mar 18 14:25:07 ppp [wan] IPV6CP: LayerFinish
    Mar 18 14:25:07 ppp [wan] IPCP: rec'd Configure Reject #2 (Ack-Sent)
    Mar 18 14:25:07 ppp [wan] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
    Mar 18 14:25:07 ppp [wan] IPCP: SendConfigReq #3
    Mar 18 14:25:07 ppp [wan] IPADDR 0.0.0.0
    Mar 18 14:25:07 ppp [wan] IPCP: rec'd Configure Nak #3 (Ack-Sent)
    Mar 18 14:25:07 ppp [wan] IPADDR 100.81.210.104
    Mar 18 14:25:07 ppp [wan] 100.81.210.104 is OK
    Mar 18 14:25:07 ppp [wan] IPCP: SendConfigReq #4
    Mar 18 14:25:07 ppp [wan] IPADDR 100.81.210.104
    Mar 18 14:25:07 ppp [wan] IPCP: rec'd Configure Ack #4 (Ack-Sent)
    Mar 18 14:25:07 ppp [wan] IPADDR 100.81.210.104
    Mar 18 14:25:07 ppp [wan] IPCP: state change Ack-Sent –> Opened
    Mar 18 14:25:07 ppp [wan] IPCP: LayerUp
    Mar 18 14:25:07 ppp [wan] 100.81.210.104 -> 10.64.64.0
    Mar 18 14:25:07 ppp [wan] IFACE: Up event
    Mar 18 14:25:07 ppp [wan] IFACE: Rename interface ng0 to ppp0

    Any ideas?


  • Netgate Administrator

    If you're using the DNS resolver in pfSense it will always use the default route which may not be the PPP link.

    When you run the dns lookup in the GUI it will check all DNS sources including dynamically assigned WANs, that may be what you're seeing.

    You will probably have to setup DNS as you would for a multi-WAN setup; Use the DNS forwarder, or the Resolver in forwarding mode with DNS disabled, and assign DNS servers on all WANs in General setup.
    https://doc.pfsense.org/index.php/Multi-WAN#DNS_Considerations

    Steve



  • @AndrewZ:

    please check this post: https://forum.pfsense.org/index.php?topic=139534.msg790609#msg790609

    Hello again, after upgrade pfsense to 2.4.3 seems problem to back.

    When i start pfsense LTE connects but when works for 24h or I click disconnect and then again connect it gaves me error, and these logs:

    Apr 3 20:56:39 ppp [wan_link0] MODEM: chat script failed
    Apr 3 20:56:39 ppp [wan_link0] Link: DOWN event
    Apr 3 20:56:39 ppp [wan_link0] LCP: Down event
    Apr 3 20:56:39 ppp [wan_link0] Link: reconnection attempt 1 in 3 seconds
    Apr 3 20:56:42 ppp [wan_link0] Link: reconnection attempt 1
    Apr 3 20:56:55 ppp [wan_link0] CHAT: The modem is not responding to "AT" at ModemCmd: label.
    Apr 3 20:56:55 ppp [wan_link0] MODEM: chat script failed
    Apr 3 20:56:55 ppp [wan_link0] Link: DOWN event
    Apr 3 20:56:55 ppp [wan_link0] LCP: Down event
    Apr 3 20:56:55 ppp [wan_link0] Link: reconnection attempt 2 in 4 seconds
    Apr 3 20:56:59 ppp [wan_link0] Link: reconnection attempt 2
    Apr 3 20:57:00 ppp caught fatal signal TERM
    Apr 3 20:57:00 ppp [wan] IFACE: Close event
    Apr 3 20:57:00 ppp [wan] IPCP: Close event
    Apr 3 20:57:00 ppp [wan] IPV6CP: Close event
    Apr 3 20:57:02 ppp [wan] Bundle: Shutdown
    Apr 3 20:57:02 ppp [wan_link0] Link: Shutdown
    Apr 3 20:57:02 ppp process 13833 terminated
    Apr 3 20:57:03 ppp Multi-link PPP daemon for FreeBSD
    Apr 3 20:57:03 ppp process 75923 started, version 5.8 (nobody@pfSense_v2_4_3_amd64-pfSense_v2_4_3-job-08 16:18 16-Mar-2018)
    Apr 3 20:57:03 ppp web: web is not running
    Apr 3 20:57:03 ppp [wan] Bundle: Interface ng0 created
    Apr 3 20:57:03 ppp [wan_link0] Link: OPEN event
    Apr 3 20:57:03 ppp [wan_link0] LCP: Open event
    Apr 3 20:57:03 ppp [wan_link0] LCP: state change Initial –> Starting
    Apr 3 20:57:03 ppp [wan_link0] LCP: LayerStart
    Apr 3 20:57:17 ppp [wan_link0] CHAT: The modem is not responding to "AT" at ModemCmd: label.
    Apr 3 20:57:17 ppp [wan_link0] MODEM: chat script failed
    Apr 3 20:57:17 ppp [wan_link0] Link: DOWN event
    Apr 3 20:57:17 ppp [wan_link0] LCP: Down event
    Apr 3 20:57:17 ppp [wan_link0] Link: reconnection attempt 1 in 3 seconds
    Apr 3 20:57:20 ppp [wan_link0] Link: reconnection attempt 1
    Apr 3 20:57:27 ppp Multi-link PPP daemon for FreeBSD
    Apr 3 20:57:27 ppp process 38707 started, version 5.8 (nobody@pfSense_v2_4_3_amd64-pfSense_v2_4_3-job-08 16:18 16-Mar-2018)
    Apr 3 20:57:27 ppp waiting for process 75923 to die…
    Apr 3 20:57:27 ppp caught fatal signal TERM
    Apr 3 20:57:27 ppp [wan] IFACE: Close event
    Apr 3 20:57:27 ppp [wan] IPCP: Close event
    Apr 3 20:57:27 ppp [wan] IPV6CP: Close event
    Apr 3 20:57:28 ppp waiting for process 75923 to die…
    Apr 3 20:57:29 ppp [wan] Bundle: Shutdown
    Apr 3 20:57:29 ppp waiting for process 75923 to die…
    Apr 3 20:57:29 ppp [wan_link0] Link: Shutdown
    Apr 3 20:57:29 ppp process 75923 terminated
    Apr 3 20:57:30 ppp web: web is not running
    Apr 3 20:57:30 ppp [wan] Bundle: Interface ng0 created
    Apr 3 20:57:30 ppp [wan_link0] Link: OPEN event
    Apr 3 20:57:30 ppp [wan_link0] LCP: Open event
    Apr 3 20:57:30 ppp [wan_link0] LCP: state change Initial –> Starting
    Apr 3 20:57:30 ppp [wan_link0] LCP: LayerStart

    Any ideas?


  • Netgate Administrator

    How do you recover from that to reconnect?

    Apr 3 20:57:17    ppp       [wan_link0] CHAT: The modem is not responding to "AT" at ModemCmd: label.
    

    That implies the modem is not responding to AT commands so maybe it's busy or has crashed. Or maybe it's switched ports somehow. Anything in the system log to suggest that?

    Steve



  • Only way to again establish connection is reboot the pfsense..

    In Init script I have only "Z" command.

    It is rather not busy port because I can do cu -l.

    [2.4.3-RELEASE][admin@router]/root: cu -l /dev/cuaU0.0
    Connected

    I have no idea how to deal with it…


  • Netgate Administrator

    cuaU0.0 is the port used to connect but it's not being used?

    What if you edit the ppp setup and resave does it re-connect?

    Steve



  • Of course I can do cu command when LTE isn't connected or pfsense is trying to reconnect (moment when log screaming 'the modem is not responding to AT commands' then I can do cu on cuaU0.0).

    Edit or resave the ppp setup do nothing. Only solution is reboot pfsense… Very strange because a lot of people posts this config as working.

    Tommorow I will try downgrade pfsense to 3.5 version.

    Martin


Log in to reply