Menu
▾
▴
Re: [Devil-Linux-discuss] Devil-linux-discuss Digest, Vol 11, Issue 1
|
From: Fred F. <ffr...@lo...> - 2007-04-05 19:30:31
|
It may sound obvious but you can DHCP and route one of the non-internet routable networks. Either 192.168.x.x/24 or even partition 10.x.x.x./8 into many /24 You can even superpose that IP network on another but then you would have to assign the IP's to a given MAC address on the DHCP server so you don't disturb your normal network. Another option is go the vlan way which is probably cleaner but may need an upgrade of the switches. What is the reason to do NAT? Fred Frigerio Locust USA =20 This electronic message transmission contains information from Locust USA which may be confidential or privileged. The information is intended to be for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please notify us by telephone (305-889-5410) or by reply via electronic mail immediately. -----Original Message----- From: dev...@li... [mailto:dev...@li...] On Behalf Of Heiko Zuerker Sent: Thursday, April 05, 2007 3:25 PM To: dev...@li... Subject: Re: [Devil-Linux-discuss] Devil-linux-discuss Digest, Vol 11, Issue 1 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=20 >> (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=20 > and be logged in as someone else--or be logged in as someone else who=20 > might have been in the middle of an inventory transaction. A good=20 > example of this might be where one person was adding to an outbound=20 > shipment at the same time someone else was receiving product. Without > warning the receiver's scanner was using the shipper's session. That=20 > 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=20 > 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=20 > 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=20 > 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? --=20 Regards Heiko Zuerker http://www.devil-linux.org ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D= DEVDE V _______________________________________________ Devil-linux-discuss mailing list Dev...@li... https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss |
