Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!xylogics!Westford.CCUR.COM From: loverso@Westford.CCUR.COM (John Robert LoVerso) Newsgroups: comp.sys.encore Subject: Re: SLIP on Annex II Keywords: SLIP, annex Message-ID: <10319@xenna.Xylogics.COM> Date: 28 Nov 90 21:26:42 GMT References: <3331@ns-mx.uiowa.edu> Sender: loverso@Xylogics.COM Reply-To: John Robert LoVerso Organization: Concurrent Computer Corp, Westford MA Lines: 54 In an article, Jay Ford writes: > network number: 128.255 > subnet mask: 255.255.255.0 > Ethernet IP address: 128.255.57.6 > local SLIP address: 128.255.253.1 > remote SLIP address: 128.255.253.2 As an aside, 128.255 is *NOT* a valid IP address. It is illegal to have a component with a value of 0 or 255, including for subnet number. There is no reason to use an unofficial number, because network numbers are easily assigned even if you are not attached to the Internet. Just send mail to the Internet Naming Authority (iana@isi.edu, I think, or hostmaster@nic.ddn.mil) and ask for a network number form. > The problem is that the Annex doesn't seem to recognize the SLIP interface This is because of the following: > set port=2 control_lines modem_control The line has been sent to do modem control, and thus the SLIP interface won't be initialized until the Annex sees DCD on the line. Modems won't generally emit DCD until they have a connection. This can sometimes be a chicken-and-egg problem if the modem won't dial until the Annex sends outgoing traffic. The Annex will assert DTR even if modem_control is not set (at least, I seem to remember it doing so). So, you might want to just set control_lines to none (or flow_control - for EIA flow control, becuase you cannot use XON-XOFF on a SLIP line; the Annex will ignore those parameters). A way of checking this is to do a "netstat -i". If the interface is listed as down (an "*" next to the name) then it is probably because it is waiting for carrier. Finally, if the modem is asserting DCD, make sure it is going to the correct pin on the Annex cable so that the Annex sees it, too. BTW, you can always go straight to Xylogics for customer support to report bugs and get fixes - either annex-support@xylogics.com or 617/272-8140 x256. Don't tell 'em I sent you. And if you are not running R5.0, send the $65 (or maybe its $100 now) to Xylogics and get a software release tape (its very cheap!). Any release prior to R5.0 just shouldn't be acceptable because of the list of fixed bugs and new features... John -- John Robert LoVerso, Concurrent Computer Corp, loverso@westford.ccur.com [to reach me, not the corporate puppet: john@loverso.leom.ma.us] "Serve not your terminal, 'till it has served you well"