Obihai install trouble
-
I shouldn't be double-NATed - my network topology is:
Cable modem –- pfSense box --- unmanaged switch --- Ethernet devices (including Obihai)
I'll check what DNS server the ISP gives out and try that as well, but I've never had a problem using other nameservers on my other computers.
-
Is there a way to assign the Obihai the external IP address via DHCP, similar to how Linksys routers' DMZ function works? (It's a little different than everyone else's concept of DMZ, which makes things a little confusing.) I'm wondering if it's having a problem with NAT, and that's the only way I can think of testing it.
-
My obihai is not on any DMZ is and not getting any special treatment. Matter of fact its getting very un-special treatment. Its just plugged into a switch and NATed same as everything else.
Thats not the problem. Why don't you connect it straight to the modem, upgrade the firmware, then put it behind the pfsense again.
This isn't supposed to be so hard.Which version of pfsense are you running?
-
OK - I updated the firmware yesterday through the web interface.
SoftwareVersion 3.0.1 (Build: 4041)I'm running pfSense 2.1 beta -
2.1-RC1 (i386)
built on Thu Aug 22 23:23:56 EDT 2013
FreeBSD 8.3-RELEASE-p10I was looking for the Ramdisk support that was introduced in 2.1, which is why I'm running the beta instead of 2.0.3.
Can you do me a favor? What does your Obi list in the web interface for the Obitalk status? Specifically, what does it say under the ex-addr?
-
Lost me.
I can access obitalk online and look at the status of things there on the web or I can type in the IP address of my local device and see some statuses there.
Please tell me exactly which you want me to look at and exactly describe the menu in question.
-
Sorry - when you first log into the web interface of the Obi, I'm looking at the status page that comes up. The sublistings on that page are WAN status, product info, ObiBT dongle 1 and 2 status, SP1-4 status, OBITalk status, and OBiPlus service status. I'm interested in what it says for the OBiTalk status.
-
OBiTALK Service Status
Parameter Name Value
Status Normal (User Mode)
CallState 0 Active CallsI'm not sure how that would help you to know.
(Mine is an OBi100) -
Sorry - mine has an additional field listing "ex-addr", which I'm taking to be what the Obi thinks its address is. I was hoping yours would tell me if it was using the address from DHCP or if it actually found the address on the other side of the NAT.
-
And now, without changing anything, it's working on OPT1 but not on the main LAN subnet. I'm more confused than ever, but I'll take it! Thanks for all the help everyone!
-
You have probably inadvertantly broken something on the LAN firewall or NAT that you haven't broken on OPT1. Glad its working.