[Simh] Connecting to Ethernet

[Jordi Guillaumes i Pons]

Hello,

My laptop has broken, so I'm lagging a little bit behind. Could you post the output of ifconfig in the Linux side and a  $ show net/tcpip in the vax side?

Jordi Guillaumes i Pons
Barcelona - Catalunya - Europa

El 04/09/2012, a les 1:08, david.d.miller at att.net va escriure:
> Sergey
> 
> That was a big help, but I'm not there yet.  I did the following
> 
> $ sudo ./ linux-tap.sh create br0 eth0 tap0 david
> $ sudo vax    ; to start SIMH
> simh>   ; the usual stuff
> simh> set xq mac=bla bla
> simh> att tap0  ;  hooray, this is the first time this succeeded.
> simh> boot cpu
> 
> When logged into VMS, I could PING and TELNET to LOCALHOST (and 127.0.0.1).   But alas, not to my physical host.  And my physical host can't see the VAX either.
> 
> But I did so many things to get to this point that something else might be screwed up, so I need to reboot linux and start this drill again.
> 
> Thanks for a great start!
> 
> Any other suggestions?
> 
> --- On Mon, 9/3/12, Sergey Oboguev <oboguev at yahoo.com> wrote:
> 
> From: Sergey Oboguev <oboguev at yahoo.com>
> Subject: Re: [Simh] Basic questions
> To: david.d.miller at att.net, simh at trailing-edge.com
> Date: Monday, September 3, 2012, 12:20 PM
> 
> > In particular I get the following error:
> > david at Thinkpad:~$ sudo brctl addbr br0
> > david at Thinkpad:~$ sudo ifconfig tap0 up
> > tap0: ERROR while getting interface flags: No such device
> 
> Perhaps because 
> 
>     /usr/sbin/tunctl -t $TAPDEV -u $USERID
> 
> is missing.
> 
> You may find the following script helpful:  
> http://oboguev.net/misc/linux-tap.sh.txt
> 
> Usage is at the bottom or invokable as
> 
>     ./linux-tap.sh help
> _______________________________________________
> Simh mailing list
> 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/20120904/b2af861a/attachment-0002.html>