|
From: Heiko Z. <he...@zu...> - 2007-04-05 19:25:01
|
On Thu, April 5, 2007 14:19, ne...@co... wrote: > Heiko, thank you for your quick reply. > > >> What do you mean exactly with swapping sessions? >> I'm currently failing to understand where the DL box comes into play >> (except for the firewalling). >> > > Swapping sessions: > Each user logs into the telnet-based app. > When they log in, they get specific menu options based on their logon. > When one handheld "steals" a session, someone can power up a scanner and > be logged in as someone else--or be logged in as someone else who might > have been in the middle of an inventory transaction. A good example of > this might be where one person was adding to an outbound shipment at the > same time someone else was receiving product. Without warning the > receiver's scanner was using the shipper's session. That really messes > up the transactions and can take a while to solve. > > > The DL box: > This is how we are controlling the access to the network. When we put the > DL box in, the dozen or so clients connecting to the telnet server all > seem to be coming from the same IP (the DL box). Before the DL box, each > of the scanners had their own IP that could be seen by the telnet server. > This means that it could restore a session if there was a disruption in > our T1. > > Basically I'm looking for suggestions on how to keep the DL box in use > without (or at least minimizing) the problems with the telnet clients. > The DL box has prevented a number of people from hopping onto our > wireless network and I'd like to keep it. OK so you're currently hiding all the scanners behind a NAT right now. Would it be possible for you to 'officially' route the IPs from the scanners, without the NAT? -- Regards Heiko Zuerker http://www.devil-linux.org |