Zach Pratt wrote:
Three interfaces? You only talked about OSAs previously.
eth0, eth1, and dummy0.
What interface the packets leave on isn't the issue. It's that the system is
receiving packets on an interface that it wouldn't expect them to be arriving
on. Packets for the IP address of eth1 arriving on eth0, etc.
makes sense.
Isn't that what the src_vipa package is supposed to help with?
I've attempted to configure the src_vipa package without success,
though I would think the --bind-address option on wget should
accomplish the same goal: setting the source ip address.
Hardcoding the default route kills availability, the entire reason you
are going through this exercise. You should listen to the default route
advertisements and either increase the metric advertised to you, if you
can, or have the network guys do so with their advertisements.
I am aware of this, and I can successfully learn a default route from
the routers. However, both potential default routes currently have the
same metric when I learn them from the routers.
The routers can adjust the advertised metric to whichever route you
desire to be preferred. Talk to the network guys. The other question
is why do you care on which interface a packet leaves? Either path
should deliver it to the destination. There can be reasons where it
makes sense to have a preference, particularly where RIP's metric is
hops and attributes such as latency and transmission rates can differ
between hops, but from the standpoint of your Linux system and the
external routers that probably isn't the case. Besides, if you are
learning the routes advertised by the routers, then the default route
likely means "this is the path to the Internet," not "this is the path
for hosts on my network." Hosts on your internal network have their own
routes in the explicit routing table entries advertised by the routers
which take precedence over the default route.
Harold Grovesteen
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
