Tom Duerbusch wrote:
Hi Mark
I'm not sure what you mean. As this is my first time into multiple
interfaces to the same host.
At school I have a vaguely similar setup:
On two machines, ppp0 is the interface to the world (we will pretend
that's so for both machines).
One is corridors.arach.net.au
The other is coco2.arach.net.au
Internally, they're both on 192.168.4.x (and each is on other networks too).
If, on corridors, I speak to coco2, then packets go out of ppp0 and
around the world and in ppp0 on coco2, and response packets follow the
route in reverse (more or less).
If I want a faster response, then on corridors I speak to 192.168.9.254
(not having DNS set up and shared), and packets exchange on the LAN.
Internally, I have corridors and a backup server both on 192.168.1.x and
10.0.0.x: I can have the default route from the backup server go through
either the 10.0.0.x or 192.168.1.x - the choice is dictated by history,
purpose and firewall rules.
Technically, I could have two interfaces on either on one LAN, but I
don't see a reason to do so.
When I want to see what's going on, then I use traceroute and "ping -R"
Are you saying that when VSE wants to use the hipersocket interface, it
should do so by using a different IP address?
In the VSE world, I have two routes:
* DIRECT ROUTES
DEFINE ROUTE,ID=NEWESA4,LINKID=VSW1,IPADDR=192.168.099.024
DEFINE ROUTE,ID=LINUX41,LINKID=HIP1,IPADDR=192.168.193.141
* INDIRECT ROUTES
On the Linux side, if I want to connect to it via the OSA/vswitch, I
specify an IP address of 192.168.193.141.
Are you suggesting that when I want to connect via the hiperchannel
(currently a test VSE system is the only other host on the
hiperchannel), that it specifies a different address (say
192.168.193.241)?
You should connect to 192.168.099.024 or 192.168.193.141 depending on
which "wire" you want the packets to travel on.
The Linux box also needs two IP addresses, one for each "wire." Default
routing should then work (at least on Linux, I can't speak for VSE).
You may need additional static* routes if either machine provides
routing to other networks.
* Or dynamic, provided by a routing daemon, but let's ignore that
complication for the moment.
Enclosed is a diagram I started, but it doesn't have the IP addresses
on it yet.
Tom Duerbusch
THD Consulting
[EMAIL PROTECTED] 12/29/2006 1:07 PM >>>
The traceroute command will show you what path a packet will follow
from one
system to another. Use the -n switch to speed things up; that disables
DNS
lookups for all the IP addresses. (In your case that wouldn't be a
big
deal, but in the general case it can be.)
I would say that your IP network setup looks a little odd. Your
HiperSocket
IP addresses should not be in the same subnet as your OSA IP
addresses.
Given that they are, you would need to set up a host route, which means
a
255.255.255.255 netmask.
You really should change the HiperSocket IP addresses instead.
Mark Post
-----Original Message-----
From: Linux on 390 Port [mailto:[EMAIL PROTECTED] Behalf Of
Tom
Duerbusch
Sent: Friday, December 29, 2006 1:48 PM
To: [email protected]
Subject: Re: routing verification
Yes, both route and netstat -r shows the routing info. But really
doesn't hit you over the head, on if a route is being used or not. At
least with ifconfig, you can watch the RX and TX byte counts
increment.
As I said, the FTP from VSE was comming in over the hipersocket, but
the replies were going back over the OSA. I would have never seen
this
problem if I used "route" or "netstat -r". And I just accidently
stumbled over it when I left the ifconfig results up. (finally
realized
that the TX count for the hipersocket connection wasn't changing, but
TX
for ETH0 was....)
Anyway, it seems like I'm having trouble setting up a static route,
via
hipersockets to my VSE machine.
I do:
yast
network services
routing
Default gateway: 192.168.192.1
Select expert configuration
Add
Destination (for VSE) 192.168.192.7
Gateway for the hipersocket connection: 192.168.192.7 (coding a
direct
route? right?)
Netmask: 255.255.255.0
Device: I select the hipersocket one.
On the Linux console, I get:
linux41:~ # Dec 29 12:43:45 linux41 ifdown-route: Error while
excuting:
Dec 29 12:43:45 linux41 ifdown-route: Command 'ip route del to
192.168.192.7/24
via 192.168.192.7 dev hsi0' returned:
Dec 29 12:43:45 linux41 ifdown-route: RTNETLINK answers: Invalid
argument
Dec 29 12:43:45 linux41 ifdown-route: Configuration line:
192.168.192.7
192.168.
192.7 255.255.255.0 hsi-bus-ccw-0.0.2500
Dec 29 12:43:46 linux41 ifup-route: Error while excuting:
Dec 29 12:43:46 linux41 ifup-route: Command 'ip route replace to
192.168.192.7/2
4 via 192.168.192.7 dev hsi0' returned:
Dec 29 12:43:46 linux41 ifup-route: RTNETLINK answers: Invalid
argument
Dec 29 12:43:46 linux41 ifup-route: Configuration line: 192.168.192.7
192.168.19
2.7 255.255.255.0 hsi-bus-ccw-0.0.2500
Dec 29 12:43:55 linux41 kernel: hsi0: no IPv6 routers present
The route command shows:
route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref
Use
Iface
192.168.192.0 * 255.255.252.0 U 0 0
0
eth0
192.168.192.0 * 255.255.252.0 U 0 0
0
hsi0
link-local * 255.255.0.0 U 0 0
0
eth0
loopback * 255.0.0.0 U 0 0
0
lo
default 192.168.192.1 0.0.0.0 UG 0 0
0
eth0
Not exactly what I wanted. I now seem to be routing 192.,168.192.0
over both interfaces.
What I want is everything to go over the default (eth0) except for
192.168.192.7 which should go over hsi0 (hipersockets).
What am I missing here?
Thanks
Tom Duerbusch
THD Consulting
(Happy New Year)
----------------------------------------------------------------------
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
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
Please do not reply off-list
----------------------------------------------------------------------
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
