Actually, the reason things are kind of complicated is because I have multiple
WAN's using multiple watchguard firewall's all on the same network segment.
I've been wanting to get around to cleaning that up but have not planned it
out yet.
The problem is that the firewall's are routing their own
> Well, that depends where his DNS servers are. If they are on, for
> example, 192.168.2 then DNS traffic is routed through the public
> interface.
Public's don't allow clients so I have private's on the 192.168.1.0 network.
> 2008/3/13 Bennie Thomas <[EMAIL PROTECTED]>:
>> I never use multiple
Well, that depends where his DNS servers are. If they are on, for
example, 192.168.2 then DNS traffic is routed through the public
interface.
2008/3/13 Bennie Thomas <[EMAIL PROTECTED]>:
> I never use multiple routes. can cause you some grief. Make sure your
> /etc/hosts, /etc/resolv.conf, /etc/ns
Actually, I take it back in your example I guess you can add a static
route to the network where DNS servers are and that should do it.
PS: You can have multiple routing tables which are selected base on
the rules (which I forgot to mention):
http://lartc.org/howto/lartc.rpdb.html
On Thu, Mar 13,
I never use multiple routes. can cause you some grief. Make sure your
/etc/hosts, /etc/resolv.conf, /etc/nsswitch.conf files.
I use multiple networks currently and have no problems with the traffic
going out the correct paths
B
[EMAIL PROTECTED] wrote:
Guess I forgot to edit those IP's :).
I
Guess I forgot to edit those IP's :).
I thought you could only have one default gateway on a machine.
I've never needed to deal with multiple nics other than bonded.
PS: What does tab 1/2 mean?
Mike
On Thu, 13 Mar 2008 13:39:25 -0700, Alex Kompel wrote:
> Google "linux policy based routing".
>
Google "linux policy based routing".
In your example you just need to setup different gateways for both
interfaces. For example:
ip route add default via 69.2.237.57 dev eth0 tab 1
ip route add default via 192.168.1.1 dev eth1 tab 2
On Thu, Mar 13, 2008 at 9:23 AM, [EMAIL PROTECTED]
<[EMAIL PROT
I don't know that there would be such a possibility in the cluster.conf.
But I think you do not need this.
Look at the function ipv4_same_subnet in the
script /usr/share/cluster/ip.sh, this and the following ones should do
this for you. The script figures out which physical interface(s) (even
if
It dawns on me that there might be another solution, at least in my case.
Could I not bond the nics, then use a virtual IP? Would that not be the
simplest way of accomplishing multiple IP's for incoming traffic?
Course, how do you add a virtual IP to a bonded setup?
Anyhow, I digress. Looks like
Is there a good document somewhere which explains in not too great technical
terms how to use multiple nics on a system. I've been running bonded nics for
many years but getting a machine to use two (or more networks) is still a
mystery to me.
For example, I have a VoIP machine which has two ni
FYI - everything worked as I expected. I put a second interface in
each host and configured it for another network. Then, I configured the
resources for this 2nd network and created a separate service
specifically for the resources on this network. So I have a service for
nfs exports to ou
11 matches
Mail list logo
