Problems with Obi/GV once again....
The9000:
I performed the echo test and it works fine.
How do I backup the configuration on unit A (working unit) and load it into unit B? Likewise for the B into A?
RonR:
Quote from: The9000 on March 10, 2012, 03:04:07 pm
How do I backup the configuration on unit A (working unit) and load it into unit B? Likewise for the B into A?
System Management -> Device Update -> Backup Configuration
System Management -> Device Update -> Restore Configuration
The9000:
Thanks I will try that next.
I just tried an interesting experiment. I moved the suspect unit over to a different (4G wireless) network setup as OBI100 -> Router -> Modem. It worked fine. I moved it back to the standard network which is setup as OBI100 -> Switch -> Astaro Firewall -> Modem. Poking around in the DHCP setup in the Astaro, I noticed the suspect unit is always mapped to 192.168.1.253 via the MAC address and the working unit is assigned a random IP by the DHCP server (currently 192.168.1.254). I'm going to play with that.
RonR:
I always suspect the router in these cases.
The best test is to temporarily plug the OBi directly in the modem, bypassing the router. Power-cycle both the modem and the OBi after making the direct connection. Then make sure the OBi is connected to the Internet by calling the echo test at **9 222 222 222.
Next, see if the problem you're wrestling with is gone. If it is, the router is likely the source of the problem. If the problem is still present, then it's obviously not the router causing it.
The9000:
Update: it's working again.
I moved the suspect unit to a new IP mapping from the Astaro DHCP server to 192.168.1.209. I picked the IP at random and previously it was mapped to 192.168.1.253. I then created a new packet filter rule to allow all traffic into 1.209 and all traffic out of 1.209. It works.
When it was mapped to 1.253, I noticed I had a packet filter to allow all inbound traffic to 1.253 but not allow all traffic out of 1.253 to bypass the packet filter. It's been setup this way since September 2011 and hasn't caused a problem until now. The unit that has been working without a problem is mapped to 1.254.
Something has changed that's causing call traffic to get filtered out by the packet filter.
Navigation
[0] Message Index
[#] Next page
[*] Previous page