Responses inline...
> -----Original Message-----
> From: Jacob Kjeldahl [mailto:[EMAIL PROTECTED]]
> Sent: Monday, 10 July 2000 8:42 AM
> To: [EMAIL PROTECTED]
> Subject: DMZ and IP
>
>
> Hi everybody
>
> I have a problem with a firewall that I been trying to set up.
[snip]
>
> The firewall has three nic's:
>
> Internal: eth0, 192.168.10.10/255.255.255.0
> DMZ: eth1, 172.24.42.200/255.255.0.0
> External: eth2, 172.24.42.100/255.255.0.0
>Bzzzzzt!<
Thanks for playing Netmasks Of Doom this evening! Sadly, both eth1 and eth2
are in the same network - notice how the netmasks put 172.24 in the
"network" part of the IP address while all the rest is in the host part?
The CORRECT answer is: Try using 172.26.42.200 for the DMZ - that will fix
this particular problem. You will also need to re-address the inside of your
router. Note that the "correct" netmask for the 172 private range is
255.240.0.0 (172.16.0.0/12 - from 172.16 through to 172.31 as the network
stub).
But don't worry, contestant - you still go home this evening with a nose
fork plated in SOLID 24 carat gold, a loaf of stale bread and twenty seven
dollars and fourteen cents in CASH!! (cash...cash...cash....)
[cheezy theme music]
[snip]
>
> Thanks in advance
>
>
> Jacob Kjeldahl
> Spobjergvej 42,12
> 8220 Brabrand
> tlf. 894449176
> [EMAIL PROTECTED]
--
Ben Nagy
Network Consultant, Volante IT
PGP Key ID: 0x1A86E304 Mobile: +61 414 411 520
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
