You can actually add more default gateways to one interface by using
Advanced option under TCP/IP properties. Of course, these are default
gateways, so all traffic that doesn't match other routing rules will get
routed thru these. You can alter the metrics to define gateway priority.
I doubt you can add default gateways that reside under different networks
this way tho. (I have used multiple default gateways on different
interfaces in Windows before tho and I didn't have any problems. The real
default interface had lower metric value than then the other, so if I
wanted use the other, I would need to bind to it directly)
Anyway, this got a little off-topic :)
Покотиленко Костик <casper@xxxxxxxxxxxx> kirjoitti Fri, 14 Dec 2007
10:23:40 +0200:
В Чтв, 13/12/2007 в 10:41 -0800, Jacob Lear пишет:
I don't think that's the problem... based on what I've read online,
Windows
doesn't like having more than 1 Default Gateway -- it confuses it (big
shocker there huh?). I tried it that way at first and it was complaining
when I tried to save the TCP/IP properties. I don't think the routing
was
working right either... I seem to recall some issues.
Because that way windows will get two default gateways, which it thinks
is not correct. You can add only one default gateway (via TCP/IP
properties), and if you need more you can add one non-default with a
comamnd "route add...".
--
Käytössä Operan vallankumouksellinen sähköpostiohjelma:
http://www.opera.com/mail/
-
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
