Hi, We have tried the following to try and get the Linux LPAR to talk to the rest of the network :
Hi! ifconfig tr0 147.110.49.17 netmask 255.255.255.252 broadcast 147.110.49.19 route add default gw 147.110.49.18 netmask 0.0.0.0 metric 0 This is what happens : The route 49.16 appears on the 2216 routing table and shows that it is directly connected to the Linux LPAR via the interface on the 2216. We can then ping 49.17 from the 2216 and 49.18 from the Linux LPAR. Infact most of the 49.* ip's. However we cannot get connectivity to the rest of our network. We added a static ip telling the network that to get to 147.110.49.17 you must go through 147.110.49.18 and it worked out perfect. We can now telnet to our Linux partition whithout any problems. We dont want to use static ip on the 2216, Is there anyway that we can achieve the same configuration(working one) without putting a static ip. Thanks moloko > -----Original Message----- > From: Rob van der Heij [SMTP:[EMAIL PROTECTED]] > Sent: 21 February 2002 09:54 > To: [EMAIL PROTECTED] > Subject: Re: Hostname Lookup failure > > >I think that there needs to be some sort of routing protocol on the > >Linux LPAR for this to work.Is there anything else that can be loaded > >for this to be effective? > > Certainly. If for example 147.110.49.* lives on your TR LAN then you > cannot simply take part of that IP address range and put it outside. > This is what also hit people who use their VM TCP/IP stack as the > virtual router. > I assume your 147.110.49.16/30 is part of the real LAN so you'd want > the 2216 to do proxyarp for the .17 end. Otherwise you need some of > the boxes on that LAN (probably the 2216) to have a static route for > your Linux LPAR via the 2216.
