|
|
|
|
|
|
|
|
 |
 |
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [FW1] Home/Office NAT range conflicts
Boy, that is a potential problem.. and I hadn't thought about it before now. NAT probably won't work, because SecureRemote would have to decide whether or not to tunnel prior to the NAT taking place. You could just have a blanket policy that home networks must be 10.x.x.x and keep your internal networks 192.168, or vice versa. I'm interested to see if anyone else has a better technical solution though. -----Original Message----- From: Jeff Newton [mailto:[email protected]] Sent: Tuesday, January 09, 2001 3:51 PM To: [email protected] Subject: [FW1] Home/Office NAT range conflicts I have users with private NAT ranges in their home networks accessing the office via SecuRemote. I see a potential problem of ip address conflicts with the private ranges used in the office. Any suggestions for how to deal with this? I shudder at the idea of having to manage/allocate ranges for use in employee's home networks. Perhaps there is a way to NAT them on the way in? Cheers, ---- Jeff Newton ============================================================================ ==== To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ============================================================================ ==== ================================================================================ To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ================================================================================
|
||||||||||
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
