Article View: cu.slug
Article #221Re: Almost there; networking the XL....
From: Mike McDonald
Date: Thu, 03 Jun 1999 00:00
Date: Thu, 03 Jun 1999 00:00
63 lines
3236 bytes
3236 bytes
>To: SLUG@ai.sri.com >Subject: Almost there; networking the XL.... >From: cbarry@2xtreme.net (Christopher R. Barry) >Date: 03 Jun 1999 15:39:42 -0700 > >Ever since I sent my second message to this list the machine had been >running non-stop and perfectly for over a day. I bought all the >networking hardware I needed yesterday and decided to go for it and >power down the machine so that I could hook up the transceiver and >connect it to the Linux box. When I powered it back up, the keyboard >was working perfectly, and has been. So I guess the problem magically >disappeared (well, I did pray a lot that it would...). > >Anyways, I've spent many hours reading the networking docs and trying >to get things working and I haven't had too much luck (especially >since my changes to things were making the docs unreachable and I had >to use the less searchable hardcopy stuff....). > >Basically, here is my setup: I've got a Linux 2.2.x box with a modem >that connects to the internet via PPP and has one ethernet card. The >XL is the only other machine on the network. The network is >192.168.0.0, the Linux box is host HAL, 192.168.0.1. The Symbolics is >host TRILOGY, 192.168.0.2. One easy way to get things working is to change Hal's address to 192.42.172.1. Just don't turn on routing on Hal! Then with ipmasqurading, you can find the 192.42.172.X addresses frm the rest of the world. >I did a lot of Find String commands to replace every last occurance of >the old IPs with the new yet whenever I tried to use host TRILOGY like >e.g. Edit File TRILOGY:>cbarry>whatever I would get a window about >"Host Trilogy (192.42.172.3)" being unreachable. The old IP was >somehow persisting despite my attempts to replace every last trace of >it. So in order to access files I would have to do >INTERNET|192.168.0.2:>.... The files are only read at boot time, restarting the network (I think), and thru the namepace editor (Edit Namespace Object host trilogy). >Oh yeah, in the course of playing with all this stuff I always >rebooted like: > > Command: Halt Machine > FEP Command: Clear Machine > FEP Command: Hello > FEP Command: Boot "Reset Network" works for a lot of reconfigsand is a lot faster than rebooting. >Thank you for any pointers, >Christopher I'll have to go boot my machine to see how it's config'd to compare with yours. (Symbolics changed a bunch of the site stuff between 8.1 and 8.3 and I keep forgetting how to set things up.) Unless someone else beats me to it, I'll send you mine tonight. Mike McDonald mikemac@mikemac.com
Technical Details
Message-ID:
<928452364.20723@news.Colorado.EDU>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<87d7zczz69.fsf@2xtreme.net>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10077e,c64f58e62bb28955 X-Google-Attributes: gid10077e,public From: Mike McDonald <mikemac@mikemac.com> Subject: Re: Almost there; networking the XL.... Date: 1999/06/03 Message-ID: <928452364.20723@news.Colorado.EDU> X-Deja-AN: 485458763 Distribution: cu Sender: daemon@peabody.colorado.edu References: <87d7zczz69.fsf@2xtreme.net> X-Note1: message-id generated by recnews X-Note2: mail msgid was <199906032317.QAA31452@mikemac.com> Organization: University of Colorado at Boulder Newsgroups: cu.slug NNTP-Posting-User: daemon