Quote:
Originally Posted by Qtx
If it as only happened since the update then I would assume it is either a bug in the firmware or a setting changed as the update wipes them all but... the fact you are plugged into a switch should mean the traffic isn't going through the superhub though, just between the port for your computer and PS3. Can see why it is puzzling.
Is the switch a managed one that you can go in to and delete any routing tables stored in case its something silly like that?
I can't see how with a switch you would have this problem unless the superhub was flooding traffic over the switch (unlikely with 100 port), it was sending a packet that disrupted the routing in some way or all traffic was routed through it due to a default gateway setting.
|
100 port? The superhub is gigabit and my switch is gigabit.
Argh...when I configured the main computer and PS3 to each have a separate static IP I did it like this:
Main Computer:
IP: 192.168.0.2
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1
PS3:
IP: 192.168.0.3
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1
My superhub is set to give out IPs as part of DHCP but in a different range like:
192.168.0.101 through to 120
with a default gateway of 192.168.0.100
Simply plugging this into one of the gigabit TPlink switch ports causes the issue to occur.
Quote:
Originally Posted by qasdfdsaq
As mentioned in the other thread where you posted the same question, the Superhub screws with ARPs.
I'd ping the Superhub from both devices to see which loses packets and to where.
|
OK. Might be difficult to ping the superhub from a PS3.
I can try it with another machine like a laptop I guess.