As I understand it, Raptor does reverse lookups on the IP address and
compares the result to the authorized user list. WINS resolves that
address to the workstation name but if there is a domain server server
that Raptor uses it to validate the user name. The requirement to do
reverse look ups can be disabled. The other option is to set up DNS to
resolve all (or a range) of DHCP addresses to a common group name and
assign access rules to that group.
> -----Original Message-----
> From: Ed Martins [SMTP:etmartins @
rocketmail .
com]
> Sent: Wednesday, October 22, 1997 1:16 PM
> To: firewalls @
GreatCircle .
COM
> Subject: Using DHCP with Firewalls
>
> I'm involve with a large manufacturing company,
> evaluating various firewall solutions. The problem is
> that they use DHCP for I.P distribution, which causes
> problems relating to firewall operation. I've read
> the Literature on FW-1 and Raptor which appears to
> support DHCP but looks like user authentication. Does
> anyone on this list have any experience in this area.
> I'm trying to avoid the manufacturer hype and look at
> what might work. Pitfalls? Vendor Promises?
>
> Thanks in advance
> Edwin T Martins
>
>
>
>
>
>
>
> _____________________________________________________________________
> Sent by RocketMail. Get your free e-mail at http://www.rocketmail.com
|
|
