Obi110 Flood The LAN and Bring My Network DOWN

<< < (4/4)

Everton:
ForObibi:

Could you try a couple of things to test to see what is going on?  Try these individually.


1.  Give the OBi110 a Static IP address outside of your DHCP range...let say 192.168.1.160 if the range is 192.168.1.2 - 192.168.1.150.  Also, set your DNS.  The setup would look something like this:


AddressingType = Static
IPAddress   = 192.168.1.160
SubnetMask = 255.255.255.0
DefaultGateway = 192.168.1.1

DNSServer1 = 8.8.4.4
DNSServer2 = 4.2.2.2

2. Disconnect all the other LAN devices and have only the OBi110 attached to your Router and then test by rebooting the Router with only the OBi110 attached to the LAN port.

3.  Attached the OBi110 to the Modem, then reboot the modem and test.

4.  Borrow another VOIP friendly Router from a friend or from Walmart (  ;D  ) and test to see if you get the same results.

Have you updated the OBi110 to the latest Firmware that was released a few days ago (1.3.0 (Build: 2824)?

Ad_Hominem:
It definitely DOES happen.  I own FOUR OBi 110s, in two different locations (800 miles away from each other), and all of them have experienced this problem at various times.  The problem is more common when the device is located near a Wifi or Cordless phone, but it just happened to me again today with a device that was nowhere near such devices...


Quote from: Shale on September 04, 2013, 10:06:29 am

It's hard to see how your OBi, even presuming a malfunction, could have flooded your LAN with traffic when it was set for 10Mb half duplex, unless your router runs everything at 10 Mb if any one device is 10 Mb.

In any case, you might try telling the router to always give the same IP to your OBi. Alternatively you could program your OBi to use a static address that is within your LAN subnet and not within the range of addresses handed by DHCP. Setting up static IP in the OBi could be tricky, but maybe not.

ericab:
you mentioned in an earlier reply that "[you] have advanced technical knowledge."

if that's the case, i would recommend sniffing the IP traffic with wireshark, and post a link to the log it captures here; that way we can get to the root cause of the packet flood.

Navigation

[0] Message Index

[*] Previous page