> I have a situation where a client needs to use 192.168.200.0/24 range on
> their local machines for internal reasons however I wish to route a block
> of ips to the client via an OR-U connected to our PM3. The problem I'm in
> is that I can't change the physical addresses on the clients machines,
> they HAVE to be in the unrouted range and since some of the machines are
> winblows 95 I can't just add another ip to their adaptor interface. I've
Sure you can. Just add an additional instance of TCP/IP in the control panel
and give it another IP address. The Original 95 did leak memory when doing
this though (I think it is now fixed).
> been looking through the OR-U manuals and can't figure out how to get the
> OR-U which sits on a simple /30 block to see the 192.168.200.0/24 ips
> (i.e. no sub interfaces). Is there a way I'm missing to get this to work
> so that the machines in that office can still use the internet but have
> the unroutable block? NAT maybe?
Since they are on a 192.168.X.X net you would need to use NAT to translate the
addresses or give each box two IPs. The OR-U will not support NAT or sub
interfaces until the 3.9 release. However if you run the 3.9 open beta on the
PM3 you can do server side NAT for the OR-U dialing into it. The other Option
is to route the 192.168 net to your network internally and setup a proxy for
them to point to.
-- Thomas C Kinnen - <tkinnen@ra.lucent.com> <tkinnen@sobhrach.com> [RADIUS Test Engineer] - LUCENT Technologies RABU "All of the opinions stated above are my own and not my employer's, unless they were given to me by my employer" - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>