217 lines
3.2 KiB
HTML
217 lines
3.2 KiB
HTML
<HTML
|
|
><HEAD
|
|
><TITLE
|
|
>VMWare and Token Ring</TITLE
|
|
><META
|
|
NAME="GENERATOR"
|
|
CONTENT="Modular DocBook HTML Stylesheet Version 1.63
|
|
"><LINK
|
|
REL="HOME"
|
|
TITLE="Token-Ring mini-HOWTO"
|
|
HREF="index.html"><LINK
|
|
REL="PREVIOUS"
|
|
TITLE="Known problems"
|
|
HREF="problemns.html"><LINK
|
|
REL="NEXT"
|
|
TITLE="Commonly asked Questions"
|
|
HREF="qanda.html"></HEAD
|
|
><BODY
|
|
CLASS="SECT1"
|
|
BGCOLOR="#FFFFFF"
|
|
TEXT="#000000"
|
|
LINK="#0000FF"
|
|
VLINK="#840084"
|
|
ALINK="#0000FF"
|
|
><DIV
|
|
CLASS="NAVHEADER"
|
|
><TABLE
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TH
|
|
COLSPAN="3"
|
|
ALIGN="center"
|
|
>Token-Ring mini-HOWTO</TH
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="left"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="problemns.html"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="80%"
|
|
ALIGN="center"
|
|
VALIGN="bottom"
|
|
></TD
|
|
><TD
|
|
WIDTH="10%"
|
|
ALIGN="right"
|
|
VALIGN="bottom"
|
|
><A
|
|
HREF="qanda.html"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"></DIV
|
|
><DIV
|
|
CLASS="SECT1"
|
|
><H1
|
|
CLASS="SECT1"
|
|
><A
|
|
NAME="VMWARE"
|
|
>5. VMWare and Token Ring</A
|
|
></H1
|
|
><P
|
|
> Thanks to Scott Russell scottrus@raleigh.ibm.com for this little "trick"
|
|
</P
|
|
><P
|
|
> One of the bummers about VMWare is if you are on a
|
|
Token-Ring adapter, your VMWare system can't have a real TCP/IP
|
|
address. Turns out this isn't the case. Here's how to do it.
|
|
</P
|
|
><P
|
|
></P
|
|
><UL
|
|
><LI
|
|
><P
|
|
> In the info below we'll call your linux box 'linux.mycompany.biz.com'
|
|
</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
> Register another ip address, I'll call it 'vmware.mycompany.biz.com'
|
|
</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
> Make sure FORWARD_IPV4=true in your /etc/sysconfig/network file. If you have
|
|
to change it you can dynamically turn on the feature as root
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="90%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
> cat 1 > /proc/sys/net/ipv4/ip_forward</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
>
|
|
</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
> Alias the second ip to the TR adapter. You end up with something like
|
|
this from /sbin/ifconfig:
|
|
<TABLE
|
|
BORDER="1"
|
|
BGCOLOR="#E0E0E0"
|
|
WIDTH="90%"
|
|
><TR
|
|
><TD
|
|
><FONT
|
|
COLOR="#000000"
|
|
><PRE
|
|
CLASS="SCREEN"
|
|
> tr0 linux.mycompany.biz.com
|
|
tr0:0 vmware.mycompany.biz.com
|
|
vmnet1 192.168.0.1
|
|
</PRE
|
|
></FONT
|
|
></TD
|
|
></TR
|
|
></TABLE
|
|
>
|
|
</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
>
|
|
Make sure you can ping both ip addresses from another box.
|
|
If you cannot then this next step will not work.
|
|
</P
|
|
></LI
|
|
><LI
|
|
><P
|
|
> Use ipchains/iptables to redirect incoming traffic for the tr0:0 interface to
|
|
your vmnet1 interface. (When I did this I only redirected specific
|
|
ports from tr0:0 to vmnet1.)
|
|
</P
|
|
></LI
|
|
></UL
|
|
><P
|
|
> Now any outside system your 'NT' box appears to be on the TR. In bound
|
|
traffic can find it as well as out.
|
|
</P
|
|
></DIV
|
|
><DIV
|
|
CLASS="NAVFOOTER"
|
|
><HR
|
|
ALIGN="LEFT"
|
|
WIDTH="100%"><TABLE
|
|
WIDTH="100%"
|
|
BORDER="0"
|
|
CELLPADDING="0"
|
|
CELLSPACING="0"
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="problemns.html"
|
|
>Prev</A
|
|
></TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="index.html"
|
|
>Home</A
|
|
></TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
><A
|
|
HREF="qanda.html"
|
|
>Next</A
|
|
></TD
|
|
></TR
|
|
><TR
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="left"
|
|
VALIGN="top"
|
|
>Known problems</TD
|
|
><TD
|
|
WIDTH="34%"
|
|
ALIGN="center"
|
|
VALIGN="top"
|
|
> </TD
|
|
><TD
|
|
WIDTH="33%"
|
|
ALIGN="right"
|
|
VALIGN="top"
|
|
>Commonly asked Questions</TD
|
|
></TR
|
|
></TABLE
|
|
></DIV
|
|
></BODY
|
|
></HTML
|
|
> |