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
Why do you care? Unless you have emperical evidence that this is
causing a problem, you are trying to control something that does not
need to be controlled. You may have multiple routing tables but all
get merged together in the OS's IP stack forwarding table. That is how
the IP forwarding
On Wed, 8 Aug 2007 05:47:57 -0500
Harold Grovesteen [EMAIL PROTECTED] wrote:
Why do you care? Unless you have emperical evidence that this is
causing a problem, you are trying to control something that does not
need to be controlled.
martian packets are normally frames which have invalid
[mailto:[EMAIL PROTECTED] On Behalf Of Zach
Pratt
Sent: Tuesday, August 07, 2007 5:15 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: [LINUX-390] occasional martian source messages
I've done some further reading on the topic of asymmetrical routing,
and I'm wondering if I should set up two routing
Comments below.
Mark Post wrote:
On Mon, Aug 6, 2007 at 4:08 PM, in message
[EMAIL PROTECTED], zach pratT
[EMAIL PROTECTED] wrote:
I have been receiving some martian source messages in
/var/log/messages as I have been working on our SLES 10 system's
network configuration, and I am
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
I've done some further reading on the topic of asymmetrical routing,
and I'm wondering if I should set up two routing tables (one for each
interface). Any suggestions?
--
For LINUX-390 subscribe / signoff / archive access
: [LINUX-390] occasional martian source messages
I've done some further reading on the topic of asymmetrical routing,
and I'm wondering if I should set up two routing tables (one for each
interface). Any suggestions
I have been receiving some martian source messages in
/var/log/messages as I have been working on our SLES 10 system's
network configuration, and I am attempting to determine what the
solution to these messages. We have never had SLES properly configured
for network access (that's why I'm working
On Mon, Aug 6, 2007 at 4:08 PM, in message
[EMAIL PROTECTED], zach pratT
[EMAIL PROTECTED] wrote:
I have been receiving some martian source messages in
/var/log/messages as I have been working on our SLES 10 system's
network configuration, and I am attempting to determine what the
solution
I am assuming that these messages are due to the fact that the packet's
are being sent out one interface and replies are arriving on the other
interface.
Isn't that what the src_vipa package is supposed to help with?
Marcy Cortes
This message may contain confidential and/or privileged
11 matches
Mail list logo
