jnford@handlebar.weeg.uiowa.edu (Jay Ford) (11/29/90)
I'm trying to set up a port on an Annex II to handle SLIP. I'm using the "Two-Host Network" model described in the Annex Network Administrator's Guide, using a V.32 modem at 9600 baud. The pertinent data is: 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 The Annex port configuration is attached below. The problem is that the Annex doesn't seem to recognize the SLIP interface. The manual says that the Annex should learn routes according to the slip_remote_address and slip_subnet_mask on all SLIP ports. However, the Annex routing table doesn't include a route to the SLIP subnet, and all packets addressed to that subnet get sent via the default route. I've tried explicitly setting the routes via the Annex gateways file as follows: net 128.255.253.0 gateway 128.255.253.1 metric 1 hardwired net 128.255.253.0 gateway 128.255.57.6 metric 2 hardwired but the Annex complained that the gateway in the first entry is on an unreachable network. It accepts the second entry (intended for the other Annexes) which mererly routes packets from the Annex to itself. The receive light on the modem indicates that data is being received when the other end of the SLIP link generates traffic, but the transmit light never goes on. The connection works fine in CLI mode, so the modem and async cables seem to be fine. Any helpful advice about this problem would be greatly appreciated. Jay Ford, Weeg Computing Center, University of Iowa, Iowa City, IA 52242 jnford@handlebar.weeg.uiowa.edu or jnfordpb@uiamvs.bitnet, 319-335-5555 ------------------------------------------------------------------------------ echo setting serial port parameters for port 2 set port=2 speed 9600 set port=2 data_bits 8 set port=2 stop_bits 1 set port=2 parity none set port=2 imask_7bits N set port=2 control_lines modem_control set port=2 type dial_in set port=2 mode slip set port=2 forwarding_timer 0 set port=2 inactivity_timer 60 set port=2 port_multiplex N set port=2 allow_broadcast N set port=2 max_session_count 3 set port=2 input_flow_control bell set port=2 input_start_char ^Q set port=2 input_stop_char ^S set port=2 output_flow_control start/stop set port=2 output_start_char ^Q set port=2 output_stop_char ^S set port=2 ixany_flow_control N set port=2 long_break Y set port=2 short_break Y set port=2 attn_char ^@ set port=2 user_name "" set port=2 prompt "" set port=2 term_var "su" set port=2 input_buffer_size 1 set port=2 bidirectional_modem N set port=2 default_modem_hangup N set port=2 location "slip" set port=2 input_is_activity Y set port=2 output_is_activity Y set port=2 reset_idle_time_on input set port=2 cli_security N set port=2 connect_security N set port=2 port_server_security N set port=2 dedicated_address 0.0.0.0 set port=2 dedicated_port telnet set port=2 newline_terminal N set port=2 leap_protocol_on N set port=2 echo N set port=2 map_to_lower N set port=2 map_to_upper N set port=2 char_erase N set port=2 line_erase N set port=2 hardware_tabs N set port=2 erase_char ^H set port=2 erase_word ^W set port=2 erase_line ^X set port=2 redisplay_line ^R set port=2 toggle_output ^O set port=2 telnet_escape ^] set port=2 slip_local_address 128.255.253.1 set port=2 slip_remote_address 128.255.253.2 set port=2 slip_subnet_mask 255.255.255.0 set port=2 slip_load_dump_host 0.0.0.0 set port=2 slip_metric 1 set port=2 slip_allow_dump N set port=2 cli_inactivity off
loverso@Westford.CCUR.COM (John Robert LoVerso) (11/29/90)
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"