Packet capture hardware issue

<< < (2/2)

TrapDoor:
Progress - now the OBi talks with my hub! The OBi's default value of option #27 has been <1> which I understand sets the port speed to 100 Mbs. When I change the option to <0>, i.e. 10 Mbs, everything works. Reverting to 100 Mbs results in failure every time regardless of hub ports used, cabling, rebooting. The problem invariably follows the OBi. Whenever the OBi port speed is set to 100 Mbs, the associated hub port connection status LED is off.

Now the hub works everywhere else at 100 Mbs in my LAN so why not here? I'm up for any ideas!

TrapDoor

zapattack:
Confirmation!!! My DD-WRT router will NOT connect to the Obi at FDX, but my inexpensive TP-Link works perfectly using either 0 or 1 setting.
Things in common: the OBI!!

Shale:
Quote from: zapattack on March 19, 2013, 11:01:31 pm

Confirmation!!! My DD-WRT router will NOT connect to the Obi at FDX, but my inexpensive TP-Link works perfectly using either 0 or 1 setting.
Things in common: the OBI!!


Maybe you do have a defective port on your OBi. Maybe the DD-WRT firmware does not support some protocol (I am no ethernet expert, so I couldn't suggest what protocol). Wasn't your router and the DD-WRT firmware a thing in common for each of your tests?

Even the particular port on the router may have been common to each test. Maybe try plugging your OBi to a different port on your router.

zapattack:
Changing port for Obi makes no difference.
Note also the PC adapter will work at 10 or 100 FDX, or Auto Negotiate.
Also, Obi settings of 2,3,4,5,6,7,8,9 also work.
Only value 1 fails.

Navigation

[0] Message Index

[*] Previous page