Network Problem with 2 network cards on the same subnet on Redhat
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Network Problem with 2 network cards on the same subnet on Redhat
Hello,
I have a network problem on Redhat ES v3.
I whish to have 2 network cards on the same subnet.
eth0 take traffic except the one from a specific subnet.
eth0 ip 192.168.1.1 mask 255.255.255.0
eth1 ip 192.168.1.2 mask 255.255.255.0
I have modified network routes configuration all 192.168.1 is on eth0 and access to default gateway too.
There is a route to 192.168.2.0/24 by eth1.
From a computer in 192.168.2.1 I wish to do a ssh session to 192.168.1.2. But it just work if I desactivate iptables.
If I activate iptables I see that ssh packet from 192.168.2.1 to 192.168.1.2 is denied because it's taken by eth0 insteed of eth1 (even if destination ip is the one of eth1).
How can I configure this to work ? (I think it could work isn't it ?).
A stange thing is when I desactivate iptables I can do a ssh session but if I let this session open and reactivate iptables it still work !! And it works even if I reboot the system !!
but the problem is that the next day (or a long moment after) the problem reappear.
thank you for any help
Seb
In order for others to be able to help you, a basic requirement is to be able to understand what the problem is about in a commonly known language.
Thanks, and happy holidays
-Y1
(Emphasis added.)
Just to yank your chain , do note that French is, in fact, a "commonly know" language. The problem was that LinuxQuestions forum entries are expected to be in "American English." (And, yes, I've had my chain yanked for using "British English" on occation).
As to the poster's question, set.its, why do you want to put both cards on the same subnet? If you're using 192. for security, you could consider putting the other card on 90. instead. Or use two different subnet masks, say 255.255.127.0 and 255.255.128.0.
Just to yank your chain , do note that French is, in fact, a "commonly know" language. The problem was that LinuxQuestions forum entries are expected to be in "American English." (And, yes, I've had my chain yanked for using "British English" on occation).
As to the poster's question, set.its, why do you want to put both cards on the same subnet? If you're using 192. for security, you could consider putting the other card on 90. instead. Or use two different subnet masks, say 255.255.127.0 and 255.255.128.0.
Please find my response in thread 395887. The same but with title in English...
Sorry I can't put an url for the moment (forbidden for newbies...)
Please do not post the same thread in more than one forum. Picking the most relevant forum and posting it once there makes it easier for other members to help you and keeps the discussion all in one place.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.