redhat F9 with multiple nics....configure one to go out onto internet
 

i have redhat F9 with 5 nics... 192.168.1.1 1.2 1.3 1.4
and an external IP for the www to see 42.35;
i also have a firewall with a content filter service blocking certain websites on 2 of these subnets 1.1 & 1.2

how can i get my F9 box to go out on one of the unblocked subnets? its going out on one of the blocked ones now and im not sure how to change that...
thanks in advance
davide123

some one help me lol!!!

any one???

Well first of, 1.1 and 1.1 are not separate subnets, they are separate IPs. Second off, what is your default gateway, it can't be 1.1 if you are using that on a nic, else this will cause everything to just speak to that nic and not the firewall. I would configure a route on the router for 192.168.42.1 and set this as the default gateway for that nic and then configure 192.168.42.35 to point to that gateway. I do not know how to default a source device off the top of my head however so I can not help with that part of the configuration.

sorry sub nets 1.1 2.1 3.1 4.1
each subnet has its own default gateway... dont want traffic going out thru my external ip, only coming; i want all traffic to go out thru 3.1 or 4.1 somw how right now it defaults to 2.1 not sure how or how to change....

also BE ADVISED Fedora 9 is UNSUPPORTED - that means there will never be any updates to it ever, NO SECURITY updates , no nothing. Fedora 9 is insecure --DO NOT use it for the net !!!!!!
install fedora 12 and in 5 months fedora 13 then 6 months after that fedora 14

I would however install the long life CentOS 5.4 or purchase RHEL 5.4 and use THAT as the gateway OS.

thanks for that tidbit. I understand that, however does not solve my issue or shed any light whatsoever. if i were to re-install my OS that often or change to a different platform, it would require substanial work to my net and possibly cause down time to my employees and customers. i am in a network enviroment protected by a HW firewall. not concerned about intrusion, since my firewall takes care of that for me... anyway again is there a way i can default a specific nic for all outbound traffic? i know there must be a way since its default on the subnet i have blocked now...any help appreciated.

don't come crawling for help when someone exploits a security hole that was PATCHED in a SUPPORTED version of Fedora.

This is WHY fedora IS NOT A GOOD CHOICE for a server!!!
the 13 month life span

vers the 5 year RHEL, debain extended and suse extended all have 5 year lifes.

ok will keep advised thanks... any suggestions on my original question? lol this is difficult

wow cant believe no one on this forum has an answer other than to tell me to upgrade or use a different version of linux...what a crock

maybe this will help:
http://www.linuxquestions.org/questi...ternet-774246/

Sorry david , it seem your question it's not clear, maybe if you want to give more detail about your problem, or what you want to do, or what port that firewall granted or not, etc , maybe many people will came with answer

Maybe you can read this link for enlighten
http://www.linuxhomenetworking.com/

Regards

I suggest that you read: man interfaces that way you can manually edit your /etc/network/interfaces, as root, to first only enable the interface(s) that relate to your addresses 192.168.3.1 and/or 192.168.4.1. If you don't know which interface relates to each IP address I suggest that you run ifconfig -a and then make an appropriate note of the eth0, eth1, eth2 and eth4 settings.

Once you have just enabled the apprpriate outbound interfaces then we can work on the inbound, however be aware that if you allow port 80 and/or 8080 and/or 443 (http and/or https) then traffic will be two way because otherwise a URL you enter in a browser will be blocked from receiving a rsponse from the web. If you gave a little more info. about your router/firewall etc. and internet access facilities - do you really have 4 dsl/modems and 4 lines coming into your office? I used to have two and had to have a special VIGOR box that split them and which allow automatic failover to the other slower (more contention) line.

Hope this helps