Re: [coLinux-users] Preventing to break coLinux

[yin s. <sun...@gm...>]

yes, that is by definition. but to make DMZ work under ethernet, the
packet need to have the unique destination MAC address.
So your DMZ colinux need to be setup to bridge mode to expose its own MAC.
those are normal networking setup. maybe you can try all this using
virtual box, then switch to colinux, which can give you a performance
boost.


On Fri, Jan 4, 2013 at 6:32 AM, deneme.true <den...@gm...> wrote:
> Sorry, I couldn't express my thoughts.
>
> As I know, if specific internal ip is DMZ, all attacks will go to DMZ
> area , and DMZ image area is close anywhere. Threats(worm,sniffer etc)
> will remain in DMZ image.
>
> When we assign specific internal ip to DMZ area. For instance: we can
> test the DMZ zone with port scanning if it is getting port knocking or
> not.
>
> So Isn't it true that DMZ area will get threats?
>
> Regards