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 it), so I'm working basically from scratch here. I am by no means a networking expert, so any wisdom or knowledge will be much appreciated.
Background info on the system: - We're not running z/VM and we do not have an IFL. - We're running SLES 10 (without SP1, or any other updates) on an LPAR on our z890 with two shared CP's. - Linux has access to both of our OSA's (shared), and each OSA is connected to a separate subnet. - The two OSA's are each assigned a private ip address (a 10.x.x.x number). - I am using the dummy device for our VIPA interface (which is dummy0) for public access and for fail over. - I have installed the quagga package (0.98.5). - I am using zebra and ripd (version 2) to advertise our VIPA to the rest of the network. - The system learns almost all the available routes (except the default route) from the actual cisco routers using rip. - I have statically defined our default route in /etc/sysconfig/network/routes. I chose to do this because I was unable to find a way to use metrics to tell rip that we'd prefer to have traffic routed through this particular card when possible. - I am able to access the system from all three interfaces from our LAN, and I have tested this when either OSA is set as the default route. - I have successfully tested access from outside our LAN (only with the current OSA set as the default route) as well. - I have turned on the fake_ll option for each OSA in the hardware config file (/etc/sysconfig/hardware/hwcfg-*) to aid in debugging this problem. I notice the IP addresses that are associated with the martian source messages are from outside our network. I am able to reproduce these messages (sometimes) by using the wget utility to try to retrieve something from outside our network (example: wget --bind-address=<vipa_address> www.google.com). Using a combination of tethereal and following /var/log/messages, I've noticed the initial request leaving one OSA and the reply coming back on the other OSA; this is when the martian source messages appear. When the request and reply use the same OSA the martian source messages do not appear, and I am able to successfully download the file with wget. The martian source messages will also appear occasionally when someone requests a file from apache (currently the only other network service that I've configured) from outside our LAN. 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. I have attempted to solve this with the network guys, but together we have been unable successfully solved the entire problem. All help is greatly appreciated. ---------------------------------------------------------------------- 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
