Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Obihai install trouble

    Scheduled Pinned Locked Moved NAT
    34 Posts 3 Posters 12.3k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      darkmich
      last edited by

      I'm having trouble getting an Obi202 VoIP adapter to work on my network. If I plug it straight into the DSL modem, it works, but when plugged into the network, I can't get it to connect to the ObiTalk network.

      I've tried adding port forwarding rules for all their recommended ports:

      What ports should I keep open on my router/firewall?
      In order for your OBi to be able to send packets w/o interruption, please configure your router as follows:

      Allow Outgoing:
      TCP Ports: 6800, 5222, 5223
      UDP Ports: 5060, 5061, 10000 to 11000, 16600 to 16998, 19305
      Allow Incoming on UDP Port: 10000

      with no luck. I do have two other port forwards going without a problem. Has anyone set one of these up before?

      Thanks for any suggestions!

      1 Reply Last reply Reply Quote 0
      • K
        kejianshi
        last edited by

        Yeah - Obihai doesn't need anything special behind pfsense.

        I do have manual outbound NAT set up and I do have a rule on outbound that assigns static port on 5060.
        I also have uPNP runing on the interface that obihai is on.

        But, I'm pretty sure that obihai worked fine before any of that.
        My obihai worked just fun with only the default allow rule on LAN +DHCP.
        I did most of that other stuff to make SIP server behave.

        Are you running multiple IPs or multiple WAN interfaces or anything?
        Are you running snort or some other blocker of everything package?

        1 Reply Last reply Reply Quote 0
        • D
          darkmich
          last edited by

          No multiple IPs, no multiple WANs - one WAN, one LAN. The only package I'm running is freeradius2 for WPA2 Enterprise. The Obi is plugged into ethernet, not using wireless. I'll try setting up uPNP. I've assigned a static DHCP address to the Obi.

          1 Reply Last reply Reply Quote 0
          • K
            kejianshi
            last edited by

            Static IP is good all the time…

            Static Port might make a bigger difference for you.

            Just check for entries under "static port manual outbound NAT SIP" on google or this forum  ;)

            1 Reply Last reply Reply Quote 0
            • D
              darkmich
              last edited by

              OK, I set up a static port for all packets from the Obihai (192.168.1.250). I also set up port forwarding and uPNP. Screenshots of port forwarding, outbound NAT, uPNP, and the firewall rules are attached, as well as the Obihai status screen.

              I was wondering about a 1:1 NAT setup, but that seems really complicated, especially since my WAN address changes.

              port_forward.png
              port_forward.png_thumb
              static_port.png
              static_port.png_thumb
              uPNP.png
              uPNP.png_thumb
              obi_talk.png
              obi_talk.png_thumb
              FW_rules.png
              FW_rules.png_thumb

              1 Reply Last reply Reply Quote 0
              • D
                darkmich
                last edited by

                Also, I turned on syslog on the Obi, and get these:

                8/28/13 10:09:14.000 PM OBI[-1]: BASE:resolving root.pnn.obihai.com    (repeated multiple times)
                8/28/13 10:09:14.000 PM OBI[-1]: DNS: All servers are not responding!

                I've tried multiple different DNS servers with no luck. Normally I use pfSense as the DNS for the network, but I've also tried Google's (8.8.8.8) and another couple that I know of.

                1 Reply Last reply Reply Quote 0
                • D
                  darkmich
                  last edited by

                  I've even added the IP address of that server to the DNS forwarder on pfSense, and still no luck. I'm highly confused.

                  1 Reply Last reply Reply Quote 0
                  • K
                    kejianshi
                    last edited by

                    You keep talking about obhai static IP

                    I keep telling you to try to set up static port in manual outbound NAT.

                    Those two things are not same.

                    obhai doesn't need all this stuff you are doing at all.

                    It might need static port on 5060 on manual outbound NAT depending on how it connects.

                    1 Reply Last reply Reply Quote 0
                    • D
                      darkmich
                      last edited by

                      I've set all the ports on 192.168.1.250 (the Obi202) to be static under manual outbound NAT - see the second screenshot I posted. It didn't make a difference.

                      1 Reply Last reply Reply Quote 0
                      • K
                        kejianshi
                        last edited by

                        What is your obihai connecting too?  Google voice or some SIP server?

                        If its some SIP server, who's SIP server?  I have an idea what may be causing this.

                        1 Reply Last reply Reply Quote 0
                        • D
                          doktornotor Banned
                          last edited by

                          I have an idea as well. Since

                          If I plug it straight into the DSL modem, it works

                          the idea would be this all borkage is caused by the huge overengineering of the configuration. Once again, keep it simple! As in:

                          My obihai worked just fun with only the default allow rule on LAN +DHCP.

                          1 Reply Last reply Reply Quote 0
                          • K
                            kejianshi
                            last edited by

                            Yeah  - I'm thinking NAT (as in NAT on the SIP server side) is creating a problem where the obihai is only working if it runs against the public IP without NAT.  If not that, then maybe OP is double NATed and doesn't realize it.  obihai + pfsense is usually stupid simple.  No special care required.

                            I'm waiting to hear back who provides his SIP.  I run a SIP server here, and that is the only reason I am using manual outbound plus static port.  Obihai worked without that.  Asterisks didn't.

                            1 Reply Last reply Reply Quote 0
                            • D
                              darkmich
                              last edited by

                              I've tried to connect to Google Voice, but first I'm trying to get their echo test service to work with no success. It's trying to connect to root.pnn.obihai.com, which is their provisioning service.

                              I did try the Obihai with the defaults as well, with no success - that's why I started port forwarding, etc., which also hasn't worked.

                              From the syslogs from the Obihai, all it keeps doing is trying to resolve the DNS for root.pnn.obihai.com over and over. I've tried turning off DNS forwarding, as well as putting the IP address for root.pnn.obihai.com into the DNS forwarder static section. I've also tried using different DNS servers on the Obihai with no luck either. I've also tried an explicit firewall rule to allow (and log) DNS lookups, which shows requests to pfSense and then requests out to the network.

                              1 Reply Last reply Reply Quote 0
                              • D
                                doktornotor Banned
                                last edited by

                                Well, if DNS resolution does not work, then any messing with NAT/port forwards and uPNP sounds rather premature, to put it mildly?!

                                1 Reply Last reply Reply Quote 0
                                • K
                                  kejianshi
                                  last edited by

                                  Hmmmm…

                                  From a console on one of your computers, try:

                                  ping root.pnn.obihai.com

                                  Then, from pfsense console do the same.

                                  Please tell results.

                                  1 Reply Last reply Reply Quote 0
                                  • D
                                    darkmich
                                    last edited by

                                    dok: I didn't find out it was a DNS issue until after starting with port issues.

                                    Ping from my computer:
                                    PING root.pnn.obihai.com (54.241.160.4): 56 data bytes
                                    64 bytes from 54.241.160.4: icmp_seq=0 ttl=55 time=100.852 ms
                                    64 bytes from 54.241.160.4: icmp_seq=1 ttl=55 time=93.125 ms
                                    64 bytes from 54.241.160.4: icmp_seq=2 ttl=55 time=101.612 ms
                                    64 bytes from 54.241.160.4: icmp_seq=3 ttl=55 time=92.128 ms

                                    Ping from pfSense:
                                    PING root.pnn.obihai.com (54.241.160.4): 56 data bytes
                                    64 bytes from 54.241.160.4: icmp_seq=0 ttl=56 time=94.989 ms
                                    64 bytes from 54.241.160.4: icmp_seq=1 ttl=56 time=92.355 ms
                                    64 bytes from 54.241.160.4: icmp_seq=2 ttl=56 time=115.846 ms
                                    64 bytes from 54.241.160.4: icmp_seq=3 ttl=56 time=90.387 ms

                                    1 Reply Last reply Reply Quote 0
                                    • K
                                      kejianshi
                                      last edited by

                                      OK - So, you fixed the DNS settings?

                                      1 Reply Last reply Reply Quote 0
                                      • D
                                        darkmich
                                        last edited by

                                        I haven't touched the DNS settings - this is my problem. Every computer on my network except the Obihai can see that host. I can't figure out what else to try to get DNS through to the Obi. I think tonight I'm going to try putting the Obihai by itself on the OPT interface and log everything that goes in and out to see if I can figure out what's going on. I'm confused as all get out at this point.

                                        1 Reply Last reply Reply Quote 0
                                        • K
                                          kejianshi
                                          last edited by

                                          Are all the other computers automatically grabbing DNS via DHCP or is their DNS manually configured on each computer?

                                          1 Reply Last reply Reply Quote 0
                                          • D
                                            darkmich
                                            last edited by

                                            They all get it via DHCP. I've tried setting the Obihai to both DNS via DHCP (which gives out 192.168.1.254, the pfSense box) and setting it explicitly (8.8.8.8 and 8.8.4.4, Google's DNS servers).

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.