lpx

  • Thread starter Thread starter ikzienietwathierstaat
  • Start date Start date
I

ikzienietwathierstaat

I have a sitecom wireless router (WL-018). I have purchased a netdisk
(nexstar LS) with ximeta software.
With a direct ethernet cable connection all is fine. However, when attached
to the wireless router the disk is not recognized (offline error 0000FF14).

The ximeta support desk has eliminated several options and has indicated the
it might be that my router can not handle the LPX protocol (or filters it).
Sitecom support has not answered.

Does anyone have a solution for the above problem
 
Previously ikzienietwathierstaat said:
I have a sitecom wireless router (WL-018). I have purchased a netdisk
(nexstar LS) with ximeta software.
With a direct ethernet cable connection all is fine. However, when attached
to the wireless router the disk is not recognized (offline error 0000FF14).
Click to expand...
The ximeta support desk has eliminated several options and has indicated the
it might be that my router can not handle the LPX protocol (or filters it).
Sitecom support has not answered.
Click to expand...
Does anyone have a solution for the above problem
Click to expand...

Forst, LPX is not an Internet protocol, so nobody is obliged to
offer any support for it. However passing through everything between
the dievices that should be able to communicate should work. Unless LPX
violates the current Internet standards. In that case it is possible that
these packes get thrown away as defective. Easiest solution is probably
tho get an addiditonal ethernet swicch and connect over that.

Arno
 
Arno said:
Forst, LPX is not an Internet protocol, so nobody is obliged to
offer any support for it. However passing through everything between
the dievices that should be able to communicate should work. Unless LPX
violates the current Internet standards. In that case it is possible that
these packes get thrown away as defective. Easiest solution is probably
tho get an addiditonal ethernet swicch and connect over that.

Arno
Click to expand...
My experience with LPX on a media server that I have is that it's very
susceptible to timeouts and congestion, on a clean Ethernet segment it
works just fine. My bet is that wireless connection is just not good
enough for LPX and the device is timing out.
 
Previously Nik Simpson said:
My experience with LPX on a media server that I have is that it's very
susceptible to timeouts and congestion, on a clean Ethernet segment it
works just fine. My bet is that wireless connection is just not good
enough for LPX and the device is timing out.
Click to expand...

Now that you mention it: Is this an Ethernet-level protocol? Then
it may not go past a router anyways, unless the router is configured
as Ethernet bridge (which usually does not make any sense at all...)

Arno
 
Arno said:
Now that you mention it: Is this an Ethernet-level protocol? Then
it may not go past a router anyways, unless the router is configured
as Ethernet bridge (which usually does not make any sense at all...)

Arno
Click to expand...
No, it's an IP or UDP protocol, so unless the wireless gateway is
blocking the ports it wants to use it shouldn't have trouble going
through the WAP. I found on my system that the connection became
unstable if the network was very busy which suggest that it just doesn't
like a congested or slow network.
 
I have done some more trail and error stuff.

Connecting the disk (direct ethernet cable) the router and also a pc with a
direct ethernet cable there is not a problem.

The problem occures when I try to connect the PC with a wireless connection
to the router. The disk can not be found (error 000014f and 000013f). Even
if I disable wep security, mac-control, virusscanner and firewall can the
disk not be found

For your information I am using a sirecom WL-018 wirless router (maximum
throughput 11M) with Windows XP professional.

Can it be that the LPX protocol does not function with a 11M wireless
enviroment

Any thoughts?
 
Previously ikzienietwathierstaat said:
I have done some more trail and error stuff.
Click to expand...
Connecting the disk (direct ethernet cable) the router and also a pc with a
direct ethernet cable there is not a problem.
Click to expand...
The problem occures when I try to connect the PC with a wireless connection
Aha!

to the router. The disk can not be found (error 000014f and 000013f). Even
if I disable wep security, mac-control, virusscanner and firewall can the
disk not be found
Click to expand...
For your information I am using a sirecom WL-018 wirless router (maximum
throughput 11M) with Windows XP professional.
Click to expand...
Can it be that the LPX protocol does not function with a 11M wireless
enviroment
Click to expand...
Any thoughts?
Click to expand...


Given the other information, I am inclined to believe the issue
is the slow wireless connection. Wireless is allways several orders
of magnitude slower with degard to delay. Throughput is also
a lot lower than vendors would have you believe. Typically
you get something like 30% of what the vendor states.

Arno
 
thnx, would upgrading to a higher throuput wireless network help, or would
you not recomend netdisk in wireless networks at all?
 
ikzienietwathierstaat said:
thnx, would upgrading to a higher throuput wireless network help, or would
you not recomend netdisk in wireless networks at all?
Click to expand...

Can't hurt, but not guaranteed to help either.
 
Previously ikzienietwathierstaat said:
thnx, would upgrading to a higher throuput wireless network help, or would
you not recomend netdisk in wireless networks at all?
Click to expand...

Maybe a really fast would help enopugh, but I doubt it.
It seems the designers of this protocol messed up badly
(a common thing in the industry) by failing to take
realistic networking conditions into account. I would advise
you to stay with cabled connections. They have far, far
superiour properties.

Arno
 
Arno said:
Maybe a really fast would help enopugh, but I doubt it.
It seems the designers of this protocol messed up badly
(a common thing in the industry) by failing to take
realistic networking conditions into account. I would advise
you to stay with cabled connections. They have far, far
superiour properties.
Click to expand...

To be fair to the designers, it's making the disk appear locally
attached so it has to live with the drive timeout limits of a locally
attached hard drive. It's not just LPX, have you tried running iSCSI
over a wireless network :-)
 
To be fair to the designers, it's making the disk appear locally
attached so it has to live with the drive timeout limits of a locally
attached hard drive. It's not just LPX, have you tried running iSCSI
over a wireless network :-)
Click to expand...

Hmm. I have not tried that or the ATA sockets Linux offers. But I have
used NFS extensively and it does have problems when done with UDP
over an unreliable networks. The newer implementations offer NFS
over TCP for exactly this reason. Maybe the art of accessing storage
over imperfect networks is not that developed after all...

Arno
 
Arno said:
Hmm. I have not tried that or the ATA sockets Linux offers. But I have
used NFS extensively and it does have problems when done with UDP
over an unreliable networks. The newer implementations offer NFS
over TCP for exactly this reason. Maybe the art of accessing storage
over imperfect networks is not that developed after all...
Click to expand...


Shared filesystems are completely different beast, what the LPX protocol
does is present the storage device as though it was locally attached,
i.e. the host it is presented to, sees it as a block device, not a
shared filesystem. So it has to beahve like a loccal hard disk, if a
local hard disk loses it's connection for even a relatively short period
of time the host OS sees a device timeout and marks the drive offline.
Network latency over a wireless connection is going to put it right on
the edge of timing out pretty much all the time.
 
Previously Nik Simpson said:
Shared filesystems are completely different beast, what the LPX protocol
does is present the storage device as though it was locally attached,
i.e. the host it is presented to, sees it as a block device, not a
shared filesystem. So it has to beahve like a loccal hard disk, if a
local hard disk loses it's connection for even a relatively short period
of time the host OS sees a device timeout and marks the drive offline.
Network latency over a wireless connection is going to put it right on
the edge of timing out pretty much all the time.
Click to expand...

But this is not necessary. Drive timouts are in the second-range.
Otherwise drives would be disabled by the OS all the time. I
think the implementers of this just failed to add a decoupling
layer, either because they did not want to invest the effort or
because they did not undertsand the problem they are solving.

Arno
 
I am not an expert on this stuff. Would this solve the problem. If so where
can I find it (to download).

I am running Windows XP SP 1
 
ikzienietwathierstaat said:
I am not an expert on this stuff. Would this solve the problem. If so where
can I find it (to download).
Click to expand...

Just a wild guess, but I'm assuming that you are responding to:

"It's not just LPX, have you tried running iSCSI over a wireless network
:-)"


If so, that was not meant as a serious suggestion, it was a
tongue-in-cheek because iSCSI probably doesn't work well over wireless
either. In the case of your device it wouldn't even be an option because
it has no iSCSI capability.
 
Back
Top