Thanks Mark, After I sent the note I was thinking that too. Now how to I say FTP XYZ and make it use one path or the other.
Oh well, the users and applications will need to be really flexible since we plan to be able to move an instance between more than one CPU so sometimes the Hipersockets DNS name will work and sometimes they will need to use the wide area DNS name instead. Thanks to everyone all for your input. Paul -----Original Message----- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Friday, July 27, 2007 2:11 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: hipersockets + route update command allows one DNS name >>> On Fri, Jul 27, 2007 at 11:08 AM, in message <[EMAIL PROTECTED]>, "Ayer, Paul W" <[EMAIL PROTECTED]> wrote: > This seems to work fine. > Please tell me where I may be in error or have a possible problem > waiting to happen. -snip- > pings and trace routes now work fine via the path they should for the > same DNS name ... > ping -c 1 -I eth0 agzls013 > PING agzls013 (192.168.127.5) from 192.168.32.139 eth0: 56(84) bytes of > data. > 64 bytes from agzls013 (192.168.127.5): icmp_seq=0 ttl=59 time=2.44 ms > --- agzls013 ping statistics --- > 1 packets transmitted, 1 received, 0% packet loss, time 0ms > rtt min/avg/max/mdev = 2.446/2.446/2.446/0.000 ms, pipe 2 > ping -c 1 -I hsi0 agzls013 > PING agzls013 (192.168.127.5) from 12.1.102.9 hsi0: 56(84) bytes of > data. > 64 bytes from agzls013 (192.168.127.5): icmp_seq=0 ttl=64 time=1.07 ms > --- agzls013 ping statistics --- > 1 packets transmitted, 1 received, 0% packet loss, time 0ms > rtt min/avg/max/mdev = 1.078/1.078/1.078/0.000 ms, pipe 2 Things are working for your artificial test because you're forcing the ping command to use a particular interface. What will force the application to do that? (Answer: nothing.) Give the HiperSocket interfaces a different name and use those. That really is how things are supposed to work. Mark Post ---------------------------------------------------------------------- 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
