| h3lpmee | what is the use of autofs? is it needed when i plugged new hard disk in my box? |
| so_ | h3lpmee, man autofs it's not generally used for harddrives |
| lang72 | h3lpmee: autofs is mostly for use with nfs when users have their home directories on a nfs server h3lpmee: It can be used for other things, but this is the main use |
| h3lpmee | thanks for the vivid explaination im puzzled when i edited my /etc/sysconfig/network-scripts/ifcfg-eth0 , ifcfg-eth0:1, and ifcfg-eth0:2 , i have added GATEWAY in my ifcfg-eth0 and for 0:1 and 0:2 file no gateway but when i typed service network restart it added three gateways by checking it through netstat -nr, why is this? do i have to edit some file? |
| jbt | h3lpmee: /etc/sysconfig/network is what you need |
| h3lpmee | ok i got it .thanks jbt |
| dt | on the subject of network config, anyone got any thoughts on the 'right' way of configuring persistent policy routing? |
| bronze_0_1 | I did But I wasn't persistent enough to finish it.......... |
| action | jbt wonder what persistent policy routing means...seems bit alien to him |
| jbt | wonder what persistent policy routing means...seems bit alien to him |
| bronze_0_1 | jbt: sticky? survives a reboot? |
| dt | bit of background, I've got a box with multiple IPs connected to multiple gateways, any traffic from the first IP should go to the first gateway, any traffic from the second IP should go to the second gateway... I've got this configured with multiple routing tables specifying a default gateway each and with iptables doing tagging of traffic from the different sources which then gets picked up by policy and maps to the routing ta ble with the correct default gateway all works fine, but, having the config in rc.local seems dirty to me :) yep, persisitent, across reboots, policy routing, apply routing decisions based on 'policy' or basically, rules to affect the way different traffic gets routed i.e. not just on the destination in my case, it's two ISPs |
| errr | why does "minimal" install X network manager and cups stuff? |
| Evolution | dt: why aren't you using /etc/sysconfig/network-scripts/route-<interface> |
| errr | in the description for minimal it says ideal for routers and firewlls, since when did either of those need those things? |
| Evolution | errr: our install is that way because RHEL's install is that way. |
| errr | Evolution: thats HIGHLY missleading to reccomend something for a router that has X on it, its going to take for ever to get all this off there |
| h3lpmee | dt we have same situation i have two providers too.can you pls share how you did that policy routing and iptables? pls show me the sample file you're doing |
| dt | Evolution, because I'm needing multiple default gateways that get applied based on source IP |
| Evolution | errr: again. we just drive the bus. if you feel this way, file a bug at bugzilla.redhat.com |
| h3lpmee | dt: as of now im doing manual routing if my first isp is down |
| errr | Evolution: is that the centos bug tracker? |
| Evolution | errr: no. that's redhat's bug tracker. |
| errr | they will close it as fast as I open it as "notabug" |
| Evolution | errr: so will we, as we match what they release. our goal is to provide a release as close as possible to their offering, without the cost and SLA for folks who don't need it. your complaint is in the package selection for 'minimal', which matches what upstream has in their release. because that's the goal of the distro. |
| dt | h3lpmee, it depends on what it is you are using the connections for... if it's just outbound access like browsing and you are doing some for of NAT, it's not so easy to do it automatically... if it's inbound access to services in multiple ISP subnets, it's more easy |
| errr | no matter how you try to word it its still HIGHLY missleading |
| h3lpmee | dt: cool.pls share it to me if it's ok with you, any of the two would greatly help me a lot |
| Evolution | errr: and it's STILL not a decision we make. |
| dt | h3lpmee, my case, this is a mail gateway that has multiple MX records pointing at it for different ISP IPs... if ISP1 goes down, no problem, we can still receive mail over ISP2, but, only if we don't use ISP1's gateway for traffic to ISP2's subnet |