Ladies and Gentlemen,
Since yesterday's summary of no solution I got some
information from Sun to the effect that the instructions
included with the SumPCi card were not completely correct.
The correct instructions are:
----- Begin Included Message -----
>From Richard.Pichette@East.Sun.COM Wed Oct 13 14:42:45 1999
But I NEED to have IP connectivity between my workstation host and SunPCi! Is
there any way to accomplish this?
Yes, you can set up static routes between the systems using a
third system or router as a proxy. For example, assume the following
conditions:
The SunPCi card has IP address 192.9.200
The host workstation has IP address 192.9.200.2
There is another system on the network (our routing proxy)
with IP address 192.9.200.3
To allow IP connectivity between the host workstation and SunPCi,
you need to do the following:
1.On SunPCi:
route add 192.9.200.2 192.9.200.3
2.On the host workstation:
route add 192.9.200.1 192.9.200.3 1
3.On the routing proxy:
route add 192.9.200.1 192.9.200.3 0
route add 192.9.200.2 192.9.200.3 0
4.If the routing proxy is a Sun, make sure that IP forwarding
is enabled:
ndd -set /dev/ip ip_forwarding 1
Not the most elegant solution, but it DOES work.
Please note that these routes are NOT permanent, i.e. they will
disappear at the next reboot. If you want to make the routes "stick"
across reboots:
On SunPCi:
If you are using Windows NT, use
"route -p add 192.9.200.2 192.9.200.3"
If you are using Windows 95, you should copy this file
into your StartUp folder (e.g.
C:\Windows\Start Menu\Programs\StartUp) and edit it
as necessary.
On the host workstation:
Create a script file under /etc/init.d that issues
the appropriate route command, and then link it with
an appropriate name under /etc/rc3.d.
On the routing proxy:
Use an appropriate method to make the route permanent.
----- End Included Message -----
Our corporate network people weren't real happy about the idea of
static routes on the router plus if/when I want to make a change
I'd have to have them do it. So I have deputized a workstation to
be the routing proxy for this purpose. It does work now, but it
seems far from neat/clean/tidy/elegant.
After the first summary I heard from "Tom Jones" <tjones@statesman.com>
whose install worked and robsonk@ebrd.com who noted the -p in the
PC route to make it persistent.
Thanks to all.
Hap
-----------------------------------------------------------
| Hap Hinrichs G W Hinrichs, III |
| Research Director |
| gwh@stat.nielsenmedia.com Nielsen Media Research|
| voice: (847) 605-3923 150 N Martingale Rd |
| fax: (847) 605-2542 Schaumburg, IL 60173 |
-----------------------------------------------------------
> From sun-managers-relay@sunmanagers.ececs.uc.edu Wed Oct 13 12:55:13 1999
> Date: Wed, 13 Oct 1999 11:48:22 -0500 (CDT)
> From: Hap Hinrichs <gwh@stat.nielsenmedia.com>
> To: sun-managers@sunmanagers.ececs.uc.edu
> Subject: SUMMARY: SunPCi and routing
> X-Sun-Charset: US-ASCII
> Sender: owner-sun-managers@sunmanagers.ececs.uc.edu
> Content-Length: 5544
>
> Ladies and Gentlemen,
>
> I had only one response to my query, from Timothy
> Lindgren who apparently doesn't have the problem
> I do. I've managed to delay the decision for a
> little while and am still trying to resolve the
> problem.
>
> Original statement of problem below in case
> anyone may have missed the original.
>
>
> >
> > Ladies and Gentlemen,
> >
> > I have a Sun Ultra5 with a SunPCi card that I was asked to
> > do an evaluation of for possible deployment. The U5 is
> > running 2.6 with appropriate patches and the SunPCi is
> > running M$ W95SR2. All basic stuff looks fine (except for
> > color flashing - 19" monitor at 1280x1024 can only run
> > 8bit color).
> >
> > I've been beating on this for a few days and the time
> > to make a recommendation is coming up fast.
> >
> > The problem is with the workstation and SunPCi seeing
> > each other on the network. In the SunPCi Release Notes,
> > item 16 this problem is discussed. I tried the approach
> > and it doesn't work. I'm not sure part of it (PC side)
> > even makes sense.
> >
> > In the following:
> >
> > a.b.70.1 router
> > a.b.70.49 SunPCi
> > a.b.70.91 U5 workstation
> >
> > State before trying to set specific routes per Sun suggestion
> >
> > On the workstation - routing table
> >
> >
> > Routing Table:
> > Destination Gateway Flags Ref Use Interface
> > -------------------- -------------------- ----- ----- ------ ---------
> > a.b.70.0 a.b.70.91 U 3 687 hme0
> > 224.0.0.0 a.b.70.91 U 3 0 hme0
> > default a.b.70.1 UG 0 39
> > 127.0.0.1 127.0.0.1 UH 0 113 lo0
> >
> > On the PC - routing table
> >
> >
> > Active Routes:
> >
> > Network Address Netmask Gateway Address Interface Metric
> > 0.0.0.0 0.0.0.0 a.b.70.1 a.b.70.49 1
> > a.b.70.0 255.255.255.0 a.b.70.49 a.b.70.49 1
> > a.b.70.49 255.255.255.255 127.0.0.1 127.0.0.1 1
> > 10.255.255.255 255.255.255.255 a.b.70.49 a.b.70.49 1
> > 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> > 224.0.0.0 224.0.0.0 a.b.70.49 a.b.70.49 1
> > 255.255.255.255 255.255.255.255 a.b.70.49 a.b.70.49 1
> >
> > Route Table
> >
> > Active Connections
> >
> > Proto Local Address Foreign Address State
> >
> > -------------
> >
> > Now, per instructions, on the PC:
> >
> > route add a.b.70.91 mask 255.255.255.0 a.b.70.1
> >
> > (add a route to the workstation through the router,
> > but with a mask as if it's a route to a network)
> >
> > This does not change the PC routing table.
> >
> > Per instructions, on the Sun:
> >
> > route add a.b.70.49 a.b.70.1 1
> >
> > (add a route to the SunPCi through the router)
> >
> > This does change the Sun routing table:
> >
> > Routing Table:
> > Destination Gateway Flags Ref Use Interface
> > -------------------- -------------------- ----- ----- ------ ---------
> > a.b.70.49 a.b.70.1 UGH 0 0
> > a.b.70.0 a.b.70.91 U 3 687 hme0
> > 224.0.0.0 a.b.70.91 U 3 0 hme0
> > default a.b.70.1 UG 0 39
> > 127.0.0.1 127.0.0.1 UH 0 113 lo0
> >
> > Since the PC routing was not changed, a ping to SunPCi gives
> >
> > ICMP Host redirect from gateway router (a.b.70.1) to SunPCi (a.b.70.49)
> > for SunPCi (a.b.70.49)
> >
> > and pinging from the PC times out.
> >
> > If I now try a route command on the PC more equivalent to the Sun:
> >
> > route add a.b.70.91 a.b.70.1
> >
> > I now see in the PC routing table
> >
> > Network Address Netmask Gateway Address Interface Metric
> > 0.0.0.0 0.0.0.0 a.b.70.1 a.b.70.49 1
> > a.b.70.0 255.255.255.0 a.b.70.49 a.b.70.49 1
> > a.b.70.49 255.255.255.255 127.0.0.1 127.0.0.1 1
> > -> a.b.70.91 255.255.255.255 a.b.70.1 a.b.70.49 1
> > 10.255.255.255 255.255.255.255 a.b.70.49 a.b.70.49 1
> > 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> > 224.0.0.0 224.0.0.0 a.b.70.49 a.b.70.49 1
> > 255.255.255.255 255.255.255.255 a.b.70.49 a.b.70.49 1
> >
> > -> shows the route that was added
> >
> > Now if I ping from the workstation to SunPCi or vice versa, the first
> > ping works and subsequent pings time-out. There also appears a line
> > in the workstation routing table that looks like:
> >
> > a.b.70.49 a.b.70.49 UGHD 0 3
> >
> > that hangs around for several seconds and then disappears. After which
> > I can get a single ping through again.
> >
> > So, is Sun confused? At this point I know I am. Have you gotten this
> > to work or just ignored the problem?
> >
> > Thanks in advance, summary will follow.
> >
>
> -----------------------------------------------------------
> | Hap Hinrichs G W Hinrichs, III |
> | Research Director |
> | gwh@stat.nielsenmedia.com Nielsen Media Research|
> | voice: (847) 605-3923 150 N Martingale Rd |
> | fax: (847) 605-2542 Schaumburg, IL 60173 |
> -----------------------------------------------------------
>
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:29 CDT