I will power cycle the switch tomorrow. It is an industrial DIN-rail
mount that is not managed.
Scott Lambert wrote:
On Sun, Aug 15, 2010 at 08:11:39PM -0400, Scott Reed wrote:
That all makes sense, but I think I have eliminated most of it. The
link from device A to device B is the primary link for this part of
the network to the Internet. It is carrying 2-way traffic just fine.
That would seem to indicate that all the hardware level stuff is OK.
I have looked at the interfaces, but I will do it again to be sure I
have not missed one, but since this plugs into a switch it should just
be the one port on the at fault unit and the switch.
The other part of the mystery is that this was working fine and then
just quit. As far as I know there were no changes to the network near
the time it quit finding neighbors.
The problem may be that the switch has failed to forward multicast
traffic from this port. Normal traffic would flow correctly. Have
you power cycled the switch? Is it a managed switch? Does it have
the ablility to permit or deny multicast traffic on a port by port
basis?
--
Scott Reed
Sr. Systems Engineer
GAB Midwest
1-800-363-1544 x2241
1-260-827-2241
Cell: 260-273-7239
--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
WISPA Wireless List: wireless@wispa.org
Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless
Archives: http://lists.wispa.org/pipermail/wireless/
