Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
From the internal eth0 int, i can access eth2 and eth3 - eth1 can access eth2 and eth3 and the DMZ(eth3) can only access eth2.
All the rules is already setup, but i have a minor problem with my nat.
The DMZ zone, where i have my mail, web, dns, etc servers, all this servers has a public ip, and it works fine. But when one of this servers access the internet via eth2, the servers own public ip is not shown.
The ip addy that is shown is the ip from eth2. This is not good when a DNS server connects to another DNS and wants to do an axfr, and the axfr security is setup on the servers IPs.
So, how do i get the DMZs servers IPs to be shown on the internet? Is there a nat rule that needed to be inserted once or for each ip?
Well, i must say:
Give the man a cigar
It works - tanx man...
Now i just have one more thing.
The internal eth0 172.16.0.0 network connects to the internet via eth2(gateway) and is shown on the internet with the ip addy of eth2.
If there a way to make the internal network eth0 public shown by an ip from the DMZ(eth3) or the DMZ(eth3's) ip addy, so it would not use the ip on eth2.
But, what if i want to be shown in the internet by the eth2 ip addy? - Or should i add an alias ip to the eth2 interface, and use this as public shown ip?
If there a way to make the internal network eth0 public shown by an ip from the DMZ(eth3) or the DMZ(eth3's) ip addy, so it would not use the ip on eth2.
When i connect to the internet from my internal(eth0) network i currently use the ip of eth2. This ip is the wan ip, and i don't want to use this.
I would rather use the ip on eth3's interface, which is the DMZ interface. This ip is the default gateway for servers on the DMZ network.
Can i use the eth3(DMZ) ip addy to be shown on the internet when ever i use the net? if so', how do i do this with masq, postrouting, etc.?
Or is it easyer to use an alternative ip addy (not the ip on eth3) from the DMZ network to be shown on the internet when ever i come from the internal network(eth0)?
I have a similar problem, would be glad if someone could help me, sorry for posting this as a reply, but you 2 seem obivous choices for this subject, so here goes:
my box:
eth0: 1.2.3.4
eth1: 192.168.1.1
eth2: 2.3.4.5
eth3: 192.168.2.1
masq'ing eth1 through eth0 works great, however no traffic is masq'd from eth3 through eth2. I can ping eth3 boxes from eth2, however no eth3 box gets out. This may have something to do with the default gateway on my box, but I dont know. My Q is, how do I get eth3 + eth2 runnin the same as eth1 + eth0 ? do I somehow need to route eth3 through eth0 ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.