[Simh] Unable to telnet to other hosts

Mark Pizzolato - Info Comm Mark at infocomm.com
Tue Nov 5 08:23:54 EST 2013


It looks like we're not making a lot of progress yet.

Please supply:

1)      The output of "ifconfig"

2)      The output of "route -n"

3)      The details describing which Linux distro and architecture (x86 or x64)  you are running and where I can download it.


-          Mark

From: priya chincholikar [mailto:priyachinc at gmail.com]
Sent: Tuesday, November 05, 2013 5:03 AM
To: Mark Pizzolato - Info Comm
Cc: Lennert Van Alboom; simh at trailing-edge.com
Subject: Re: [Simh] Unable to telnet to other hosts

Hi Mark,

I have checked it, It is there on my LAN. Both the IP's are on same LAN.

-Priya

On Tue, Nov 5, 2013 at 6:00 PM, Mark Pizzolato - Info Comm <Mark at infocomm.com<mailto:Mark at infocomm.com>> wrote:
You do not need any additional libpcap distro, the make output AND the simulator "SHOW ETHERNET" output show that you already have a network capable simulator.

The SHOW ETHERNET output now shows that you've successfully opened the network device (em1).  As long as it is a wired Ethernet connection you should be good to go.  By that, I mean once you've got a running operating system installed with IP network stack, you should be able to talk to OTHER systems on your LAN, but NOT to the host system.

The attached image you sent earlier in this conversation shows your simulated system's IP address as 192.168.1.110, but you were attempting to PING an address of 192.168.0.37.  Given the netmask of the simulator's interface, that should be on your LAN, however, does this really describe your LAN?  What is the host Linux system's IP configuration:

      $ ifconfig
      $ route -n


-          Mark

From: priya chincholikar [mailto:priyachinc at gmail.com<mailto:priyachinc at gmail.com>]
Sent: Tuesday, November 05, 2013 4:12 AM

To: Mark Pizzolato - Info Comm
Cc: Lennert Van Alboom; simh at trailing-edge.com<mailto:simh at trailing-edge.com>
Subject: Re: [Simh] Unable to telnet to other hosts

Hi,

Attached files show the version and ethernet connections.

and will I need libpcap-devel distro package to be installed ?

-Priya



On Tue, Nov 5, 2013 at 5:03 PM, Mark Pizzolato - Info Comm <Mark at infocomm.com<mailto:Mark at infocomm.com>> wrote:
Hi Priya,

Looks good so far.

You should be able to run with the vax binary in BIN/vax and the configuration file you've already got.

I would initially comment out the "dep bdr 0" and boot manually until you get things fully working and at the >>> prompt type "SET BOOT DUA0:" to set your autoboot device in the NVRAM.

Meanwhile, to verify your network configuration, invoke the simulator and hit ^E to get to a sim> prompt and enter the following commands:

    sim> SHOW ETHERNET

This will list the available network devices which libpcap can connect to.  Not all of them will work with simh, but the one which is your wired network connection should be fully usable.

If you still have problems send back the output of

   ^E
    sim> SHOW VERSION


-          Mark

From: priya chincholikar [mailto:priyachinc at gmail.com<mailto:priyachinc at gmail.com>]
Sent: Tuesday, November 05, 2013 2:01 AM

To: Mark Pizzolato - Info Comm
Cc: Lennert Van Alboom; simh at trailing-edge.com<mailto:simh at trailing-edge.com>
Subject: Re: [Simh] Unable to telnet to other hosts

Hi,
I built the vax as told :

 $ make vax
lib paths are: /lib/ /lib/sse2/ /usr/lib/atlas/ /usr/lib/dyninst/ /usr/lib/llvm/ /usr/lib/mysql/ /usr/lib/tcl8.5/ /usr/lib/tracker-0.14/ /usr/lib/xulrunner/
using libm: /lib//libm.so
using librt: /lib//librt.so
using libpthread: /lib//libpthread.so /usr/include/pthread.h
using libdl: /lib//libdl.so /usr/include/dlfcn.h
using libpcap: /usr/include/pcap.h
*** Warning ***
*** Warning *** vax Simulator are being built with
*** Warning *** minimal libpcap networking support
*** Warning ***
*** Warning *** Simulators on your Linux platform can also be built with
*** Warning *** extended Ethernet networking support by using VDE Ethernet.
*** Warning ***
*** Warning *** To build simulator(s) with extended networking support you
*** Warning *** should read 0readme_ethernet.txt and follow the instructions
*** Warning *** regarding the needed libvdeplug components for your Linux
*** Warning *** platform
*** Warning ***
***
*** vax Simulator being built with:
*** - compiler optimizations and no debugging support. GCC Version: 4.7.2.
*** - dynamic networking support using Linux provided libpcap components.
***
*** git commit id is 32b8f063620db62213151f18403fcd9c02fae97f.
***
mkdir -p BIN
gcc -std=c99 -U__STRICT_ANSI__  -O2 -finline-functions -fgcse-after-reload -fpredictive-commoning -fipa-cp-clone -fno-unsafe-loop-optimizations -fno-strict-overflow -Wno-unused-result -DSIM_GIT_COMMIT_ID=32b8f063620db62213151f18403fcd9c02fae97f -DSIM_COMPILER="GCC Version: 4.7.2" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO  -DHAVE_DLOPEN=so -DHAVE_GLOB  sim_BuildROMs.c -o BIN/BuildROMs
BIN/BuildROMs
rm -f BIN/BuildROMs
mkdir -p BIN
gcc -std=c99 -U__STRICT_ANSI__  -O2 -finline-functions -fgcse-after-reload -fpredictive-commoning -fipa-cp-clone -fno-unsafe-loop-optimizations -fno-strict-overflow -Wno-unused-result -DSIM_GIT_COMMIT_ID=32b8f063620db62213151f18403fcd9c02fae97f -DSIM_COMPILER="GCC Version: 4.7.2" -I . -D_GNU_SOURCE -DUSE_READER_THREAD -DSIM_ASYNCH_IO  -DHAVE_DLOPEN=so -DHAVE_GLOB  VAX/vax_cpu.c VAX/vax_cpu1.c VAX/vax_fpa.c VAX/vax_io.c VAX/vax_cis.c VAX/vax_octa.c  VAX/vax_cmode.c VAX/vax_mmu.c VAX/vax_stddev.c VAX/vax_sysdev.c VAX/vax_sys.c  VAX/vax_syscm.c VAX/vax_syslist.c PDP11/pdp11_rl.c PDP11/pdp11_rq.c PDP11/pdp11_ts.c PDP11/pdp11_dz.c PDP11/pdp11_lp.c PDP11/pdp11_tq.c PDP11/pdp11_xq.c PDP11/pdp11_vh.c PDP11/pdp11_cr.c PDP11/pdp11_io_lib.c scp.c sim_console.c sim_fio.c sim_timer.c sim_sock.c sim_tmxr.c sim_ether.c sim_tape.c sim_disk.c sim_serial.c sim_video.c -DVM_VAX -DUSE_INT64 -DUSE_ADDR64 -I VAX -I PDP11 -DUSE_SHARED -I/usr/include/ -DUSE_TAP_NETWORK -o BIN/microvax3900 -lm -lrt -lpthread -ldl

cp BIN/microvax3900 BIN/vax
[root at localhost simh-master]#

What should I do after this? Create a vax.ini file ?

- Priya

On Mon, Nov 4, 2013 at 7:13 PM, Mark Pizzolato - Info Comm <Mark at infocomm.com<mailto:Mark at infocomm.com>> wrote:
>From what you've provided, I can't really tell EXACTLY what simulator you are running or how it was built or what it thinks is its capabilities are.  The latest source is the most supportable and the build (makefile) tells us many things.  Phillip Wherry wrote the instructions you are followed 9 years ago.  Things have evolved since that time and become much smoother.

You are getting the "BOOT/R5:0 EXIT" message since you have the system setup to autoboot (BDR set to 0) but your NVRAM doesn't yet specify a default boot device.  This is NOT related to the network issues.

Please build the latest source and if what you then need to do isn't obvious, then we can explore further.

The total build instructions should be:
                $ wget https://github.com/simh/simh/archive/master.zip
               $ unzip simh-master.zip
                $ cd simh-master
                $ make vax

As I said, if the simulator doesn't work correctly for you then the output produced during the above make will be useful.


-          Mark

From: priya chincholikar [mailto:priyachinc at gmail.com<mailto:priyachinc at gmail.com>]
Sent: Monday, November 04, 2013 5:31 AM
To: Mark Pizzolato - Info Comm
Cc: Lennert Van Alboom; simh at trailing-edge.com<mailto:simh at trailing-edge.com>
Subject: Re: [Simh] Unable to telnet to other hosts

I have followed steps from http://www.wherry.com/gadgets/retrocomputing/vax-simh.html to build the simulator, earlier I was having a problem while starting TCP/IP, but I solved that by attaching the interface type in vax.ini file,

Attach Ethernet to a network interface
set XQ mac=08-00-2B-AC-AC-B1
set XQ type=DELQA
attach XQ em1

I don't think I have to build it again unless of course that is the only solution to make this work.

I dont know why I get the (BOOT/R5:0 EXIT when I run the simulator,
Please check this,

VAX simulator V3.9-0
NVR: buffering file in memory
RQ: unit is read only
/usr/local/vax/bin/vax.ini> attach XQ em1
Command not allowed


KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
Loading system software.
(BOOT/R5:0 EXIT



  2..
?41 DEVASSIGN, EXIT
?06 HLT INST
        PC = 00000C1A
Failure.
>>>show version
KA655-B V5.3, VMB 2.7
>>>boot dua0
(BOOT/R5:0 DUA0



  2..
-DUA0
  1..0..


%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped
%SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk
%SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the PAGEFILE.SYS
   OpenVMS (TM) VAX Version V7.3     Major version id = 1 Minor version id = 0
%WBM-I-WBMINFO Write Bitmap has successfully completed initialization.
$!  Copyright 2001 Compaq Computer Corporation.

%STDRV-I-STARTUP, OpenVMS startup begun at  4-NOV-2013 18:44:52.23
%RUN-S-PROC_ID, identification of created process is 00000206
%DCL-S-SPAWNED, process SYSTEM_1 spawned
%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:11.64  %%%%%%%%%%%
Operator _FORD$OPA0: has been enabled, username SYSTEM

%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:11.65  %%%%%%%%%%%
Operator status for operator _FORD$OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12

%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:11.69  %%%%%%%%%%%
Logfile has been initialized by operator _FORD$OPA0:
Logfile is FORD::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;32

%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:11.70  %%%%%%%%%%%
Operator status for operator FORD::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;32
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12

%SET-I-NEWAUDSRV, identification of new audit server process is 0000020C
%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:14.87  %%%%%%%%%%%
Message from user SYSTEM on FORD
%SECSRV-I-PROXYSTARTINGUP, proxy processing now starting up

%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:14.88  %%%%%%%%%%%
Message from user SYSTEM on FORD
%SECSRV-I-CIACRECLUDB, security server created cluster intrusion database

%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:14.89  %%%%%%%%%%%
Message from user SYSTEM on FORD
%SECSRV-I-SERVERSTARTINGU, security server starting up

%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:14.89  %%%%%%%%%%%
Message from user SYSTEM on FORD
%SECSRV-I-CIASTARTINGUP, breakin detection and evasion processing now starting up

%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:17.07  %%%%%%%%%%%
Message from user SYSTEM on FORD
%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager


%LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
Startup processing continuing...

%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:17.72  %%%%%%%%%%%
Message from user SYSTEM on FORD
Warning: DECdtm log file not found (SYS$JOURNAL:SYSTEM$FORD.LM$JOURNAL)
        %RMS-E-FNF, file not found
        TP server process waiting


%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:18.72  %%%%%%%%%%%
Message from user AUDIT$SERVER on FORD
Security alarm (SECURITY) and security audit (SECURITY) on FORD, system id: 1025
Auditable event:          Audit server starting up
Event time:                4-NOV-2013 18:45:18.58
PID:                      00000203
Username:                 SYSTEM

%STARTUP-I-AUDITCONTINUE, audit server initialization complete

The OpenVMS VAX system is now executing the site-specific startup commands.


%TCPIP-I-INFO, TCP/IP Services startup beginning at  4-NOV-2013 18:45:27.15
%TCPIP-I-NORMAL, timezone information verified
%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:29.91  %%%%%%%%%%%
Message from user INTERnet on FORD
INTERnet Loaded

%RUN-S-PROC_ID, identification of created process is 00000211
%TCPIP-I-SETLOCAL, setting domain and/or local host
%TCPIP-I-STARTCOMM, starting communication
%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:32.13  %%%%%%%%%%%
Message from user INTERnet on FORD
INTERnet Started

%TCPIP-I-SETPROTP, setting protocol parameters
%TCPIP-I-DEFINTE, defining interfaces
%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:33.43  %%%%%%%%%%%
Message from user INTERnet on FORD
INTERnet ACP Created INTERnet interface: QE0

%TCPIP-I-STARTNAME, starting name service
%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:34.16  %%%%%%%%%%%
Message from user Proxy Server on FORD
Loading proxy server image TCPIP$PROXY_SERVICES

%TCPIP-S-STARTDONE, TCP/IP Kernel startup completed
%TCPIP-E-PROXYERROR, error processing proxy request
-TCPIP-W-NORECORD, information not found
-RMS-E-RNF, record not found
%TCPIP-E-PROXYERROR, error processing proxy request
-TCPIP-W-NORECORD, information not found
-RMS-E-RNF, record not found
%TCPIP-I-LOADSERV, loading TCPIP server proxy information
%TCPIP-I-SERVLOADED, auxiliary server loaded with 0 proxy records
-TCPIP-I-SERVSKIP, skipped 0 communication proxy records
-TCPIP-I-SERVTOTAL, total of 0 proxy records read
%TCPIP-S-STARTDONE, TCPIP$PROXY startup completed
%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:44.48  %%%%%%%%%%%
Message from user INTERnet on FORD
INTERnet ACP Activate FTP Server

%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:44.49  %%%%%%%%%%%
Message from user INTERnet on FORD
INTERnet ACP NOLISTEN Process creation success: Service - FTP

%TCPIP-S-STARTDONE, TCPIP$FTP startup completed
%TCPIP-S-STARTDONE, TCPIP$FTP_CLIENT startup completed
%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:48.13  %%%%%%%%%%%
Message from user PWIPdriver on FORD

 PWIPdriver successfully started.

%RUN-S-PROC_ID, identification of created process is 00000213
%TCPIP-S-STARTDONE, TCPIP$PWIP_DRIVER startup completed
%%%%%%%%%%%  OPCOM   4-NOV-2013 18:45:49.29  %%%%%%%%%%%
Message from user INTERnet on FORD
INTERnet ACP Activate TELNET Server

%TCPIP-S-STARTDONE, TCPIP$TELNET startup completed
%TCPIP-S-STARTDONE, TCP/IP Services startup completed at  4-NOV-2013 18:45:50.33

%MOUNT-I-MOUNTED, DATA1 mounted on _FORD$DUA1:
%MOUNT-I-MOUNTED, DATA2 mounted on _FORD$DUA2:
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
  SYSTEM       job terminated at  4-NOV-2013 18:45:53.04

  Accounting information:
  Buffered I/O count:            2340         Peak working set size:    1821
  Direct I/O count:               866         Peak page file size:      8473
  Page faults:                  12611         Mounted volumes:             2
  Charged CPU time:           0 00:00:49.40   Elapsed time:     0 00:01:01.11

 Welcome to OpenVMS (TM) VAX Operating System, Version V7.3

After I login <file attached>


On Mon, Nov 4, 2013 at 6:30 PM, Mark Pizzolato - Info Comm <Mark at infocomm.com<mailto:Mark at infocomm.com>> wrote:
Hi Priya,

I was looking for the output of "SHOW VERSION" from the "sim> " prompt.  The "SHOW VERSION" output from the ">>> " prompt is the version of the VAX console ROM.  The "sim>" Version information describes the simulator's capabilities.

>From the simulator startup message I can see you're running simh V3.9.

Please download and build the source from https://github.com/simh/simh/archive/master.zip

You should just be able to unzip the file and build the vax simulator with "make vax".

The "messages you get when you run the simulator" include an error message.  It would be useful to see what command caused that error.  To do so you can invoke the simulator with the "-v" command switch.

If this doesn't help, then the output produced when you invoked the "make vax" command to build the simulator will be useful.


-          Mark

From: priya chincholikar [mailto:priyachinc at gmail.com<mailto:priyachinc at gmail.com>]
Sent: Monday, November 04, 2013 4:50 AM
To: Mark Pizzolato - Info Comm
Cc: Lennert Van Alboom; simh at trailing-edge.com<mailto:simh at trailing-edge.com>
Subject: Re: [Simh] Unable to telnet to other hosts

I'm using fedora 18 as the host.
This is the message i get when i run the simulator :

VAX simulator V3.9-0
NVR: buffering file in memory
RQ: unit is read only
/usr/local/vax/bin/vax.ini> attach XQ em1
Command not allowed


KA655-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
Loading system software.
(BOOT/R5:0 EXIT



  2..
?41 DEVASSIGN, EXIT
?06 HLT INST
        PC = 00000C1A
Failure.
>>>show version
KA655-B V5.3, VMB 2.7

This is the vax.ini file :

;
; Load CPU microcode
load -r /usr/local/vax/data/ka655x.bin
;
; Attach non-volatile RAM to a file
attach nvr /usr/local/vax/data/nvram.bin
;
; This virtual machine has 64M memory
set cpu 64m
;
; Define disk drive types. RA92 is largest-supported VAX drive.
set rq0 ra92
set rq1 ra92
set rq2 ra92
set rq3 cdrom
;
; Attach defined drives to local files
attach rq0 /usr/local/vax/data/d0.dsk
attach rq1 /usr/local/vax/data/d1.dsk
attach rq2 /usr/local/vax/data/d2.dsk
;
; Attach the CD-ROM to its file (read-only)
attach -r rq3 /usr/local/vax/data/cd.iso
;
; Disable unused devices. It's also possible to disable individual devices,
; using a construction like "set rq2 disable" if desired.
;
set rl disable
set ts disable
;
; Attach Ethernet to a network interface
set XQ mac=08-00-2B-AC-AC-B1
set XQ type=DELQA
attach XQ em1
;
;Uncomment the line below to enable auto-boot
dep bdr 0
;
;Choose one of the following lines.SET CPU CONHALT returns control to the
; VAX console monitor on a halt event (where behavior will be further
; determined by whether auto-boot is set--see above. SET CPU SIMHALT will
; cause the simulator to get control instead.
set cpu conhalt
;set cpu simhalt
;
;Now start the emulator
boot cpu
;
; Exit the simulator
exit

Regards,
Priya

On Mon, Nov 4, 2013 at 6:02 PM, Mark Pizzolato - Info Comm <Mark at infocomm.com<mailto:Mark at infocomm.com>> wrote:
On Monday, November 04, 2013 at 4:29 AM, Lennert Van Alboom wrote:
> The output you sent seems to indicate that your problem isn't with telnet,
> but with the guest not having networking at all (configuring the network
> inside simh alone doesn't do much).
>
> What host OS are you doing this on?
> What does your host networking stack look like?
> Can you show your simh configuration file?
Also include the output of SHOW VERSION from within the simulator you are using...

> Regards,
>
>
> Lennert
>
>
> On Mon, Nov 04, 2013 at 05:20:34PM +0530, priya chincholikar wrote:
> >    Hi,
> >    I'm new to openvms and simh. I installed open vms 7.3 and have
> configured
> >    tcpip too.
> >    I want to connect to other hosts to test my tcpip.
> >    $ telnet 192.168.0.37
> >    %TELNET-E-IVHOST, Invalid or unknown host 192.168.0.37
> >    -TCPIP-E-NO_RECOVERY, unexpected name server failure
> >    $ ucx
> >    TCPIP>  ping 192.168.0.37
> >    PING 192.168.0.37 (192.168.0.37): 56 data bytes
> >    ----192.168.0.37 PING Statistics----
> >    4 packets transmitted, 0 packets received, 100% packet loss
> >    %SYSTEM-F-TIMEOUT, device timeout
> >    I'm not able to understand where I went wrong.
> >    Thanks,
> >    Priya
>
> > _______________________________________________
> > Simh mailing list
> > Simh at trailing-edge.com<mailto:Simh at trailing-edge.com>
> > http://mailman.trailing-edge.com/mailman/listinfo/simh





-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.trailing-edge.com/pipermail/simh/attachments/20131105/440bba0a/attachment-0002.html>


More information about the Simh mailing list