Does anyone GROK configuring a CISCO 3640 to support T/R to FE using the
NM-1FE1R2W? I'm sure I'll need to hook up the T/R to a MAU, maybe a
Deskstream, then to the 3640...

https://ardent-tool.com/cisco/cisco_nm-1fe1r2w.html

On 1/25/22 1:12 PM, Louis Ohland wrote:
> Does anyone GROK configuring a CISCO 3640 to support T/R to FE using the
> NM-1FE1R2W? I'm sure I'll need to hook up the T/R to a MAU, maybe a
> Deskstream, then to the 3640...

What are you wanting to do? Route or bridge?

Routing between Token-Ring and Ethernet should be trivial.

Seeing as how Token-Ring doesn't support the concept of a cross over
cable, yes, you will need a MAU or comparable.

What protocol(s) are you wanting to use?

--
Grant. . . .
unix || die

I can only describe what I want. Otherwise, I'd have probably done it by
now.

What I got:

CD36-CP-12.0.7 on CD [CISCO 3600 IP Plus Feature Pack]
NM-1FE1R2W
3640 with maxxed out memory [SRAM and flash?]

What I wandt todo...

Use a Deskstream to enable FDX on the Tolkien Ring [we all have fantasies]

Hook up a cable from RI/RO [I suppose] to the RJ45 port on the
NM-1FE1R2W, let the 3640 do whatever bit-twiddling it wandts to, then
take the Fast Ethernet off the NM-1FE1R2W and jam it into my c
laptop. Do a direct connect over Fast Ethernet.

IP protocol. This will be totally privat. Once it works, then the next
hurdle is hooking the 3640 via FE to my cable modem.

On 1/25/2022 14:23, Grant Taylor wrote:
> On 1/25/22 1:12 PM, Louis Ohland wrote:
>> Does anyone GROK configuring a CISCO 3640 to support T/R to FE using
>> the NM-1FE1R2W? I'm sure I'll need to hook up the T/R to a MAU, maybe
>> a Deskstream, then to the 3640...
>
> What are you wanting to do?  Route or bridge?
>
> Routing between Token-Ring and Ethernet should be trivial.
>
> Seeing as how Token-Ring doesn't support the concept of a cross over
> cable, yes, you will need a MAU or comparable.
>
> What protocol(s) are you wanting to use?
>
>
>

On 1/25/22 1:39 PM, Louis Ohland wrote:
> I can only describe what I want. Otherwise, I'd have probably done it by
> now.

ACK

> What I got:
>
> CD36-CP-12.0.7 on CD [CISCO 3600 IP Plus Feature Pack]
> NM-1FE1R2W
> 3640 with maxxed out memory [SRAM and flash?]

Okay.

> What I wandt todo...
>
> Use a Deskstream to enable FDX on the Tolkien Ring [we all have fantasies]
>
> Hook up a cable from RI/RO [I suppose] to the RJ45 port on the
> NM-1FE1R2W,

I would suggest a normal station port as opposed to the RI / RO ports.
My understanding is that RI / RO /can/ /sometimes/ be weird. And
there's the fact that the Cisco is just another Token-Ring station. So
I'd use a station port and /avoid/ the RI / RO ports.

> let the 3640 do whatever bit-twiddling it wandts to, then take the
> Fast Ethernet off the NM-1FE1R2W and jam it into my c
> laptop. Do a direct connect over Fast Ethernet.

Okay.

That doesn't speak to if routing will suffice or if you need bridging.

> IP protocol. This will be totally privat.

These imply that routing will suffice.

Rather they don't indicate any /need/ for bridging.

> Once it works, then the next hurdle is hooking the 3640 via FE to my
> cable modem.

This strongly suggests routing.

I would start with one private subnet on the Token-Ring interface and a
different private subnet on the (Fast)Ethernet interface. Configure the
Token-Ring and Ethernet client's IP address appropriately for the subnet
for the router interface they are connected to.

You can cheat and use the IP of the router's interface facing the
clients as the client's default gateway.

If things work correctly, then the Token-Ring and Ethernet clients
should be able to ping each other. (Presuming nothing's running a host
based firewall doing any filtering.)

--
Grant. . . .
unix || die

All links to CISCO seem to bring up a new page and the files are not
forthcoming. Assessing the damage. Internet Archive seems to have most
of it.

On 1/25/2022 16:32, Grant Taylor wrote:
> On 1/25/22 1:39 PM, Louis Ohland wrote:
>> I can only describe what I want. Otherwise, I'd have probably done it
>> by now.
>
> ACK
>
>> What I got:
>>
>> CD36-CP-12.0.7 on CD [CISCO 3600 IP Plus Feature Pack]
>> NM-1FE1R2W
>> 3640 with maxxed out memory [SRAM and flash?]
>
> Okay.
>
>> What I wandt todo...
>>
>> Use a Deskstream to enable FDX on the Tolkien Ring [we all have
>> fantasies]
>>
>> Hook up a cable from RI/RO [I suppose] to the RJ45 port on the
>> NM-1FE1R2W,
>
> I would suggest a normal station port as opposed to the RI / RO ports.
> My understanding is that RI / RO /can/ /sometimes/ be weird.  And
> there's the fact that the Cisco is just another Token-Ring station.  So
> I'd use a station port and /avoid/ the RI / RO ports.
>
>> let the 3640 do whatever bit-twiddling it wandts to, then take the
>> Fast Ethernet off the NM-1FE1R2W and jam it into my c
>> laptop. Do a direct connect over Fast Ethernet.
>
> Okay.
>
> That doesn't speak to if routing will suffice or if you need bridging.
>
>> IP protocol. This will be totally privat.
>
> These imply that routing will suffice.
>
> Rather they don't indicate any /need/ for bridging.
>
>> Once it works, then the next hurdle is hooking the 3640 via FE to my
>> cable modem.
>
> This strongly suggests routing.
>
> I would start with one private subnet on the Token-Ring interface and a
> different private subnet on the (Fast)Ethernet interface.  Configure the
> Token-Ring and Ethernet client's IP address appropriately for the subnet
> for the router interface they are connected to.
>
> You can cheat and use the IP of the router's interface facing the
> clients as the client's default gateway.
>
> If things work correctly, then the Token-Ring and Ethernet clients
> should be able to ping each other.  (Presuming nothing's running a host
> based firewall doing any filtering.)
>
>
>

https://web.archive.org/web/20070226104239/http://www.cisco.com/univercd/cc/td/doc/product/access/acs_mod/cis2600/hw_inst/nm_inst/nm-doc/connteth.pdf

Figure 3-22 Connecting a Token Ring STP Port (DB-9) to a MAU

It seems CISCO agrees with you [whew! the pressure is off...]

It doesn't say avoid RI/RO, but the illustration shows connection to an
inner port. Usually, RI/RO is an outer port [on one end].

On 1/25/2022 16:32, Grant Taylor wrote:
> I would suggest a normal station port as opposed to the RI / RO ports.
> My understanding is that RI / RO /can/ /sometimes/ be weird.  And
> there's the fact that the Cisco is just another Token-Ring station.  So
> I'd use a station port and /avoid/ the RI / RO ports.

On 1/25/22 7:46 PM, Louis Ohland wrote:
> It doesn't say avoid RI/RO, but the illustration shows connection to an
> inner port. Usually, RI/RO is an outer port [on one end].

I can't point to anything hard and fast that says that RI / RO ports
won't work. But I have had issues where stations didn't work properly
when connected to RI / RO ports. Issues where moving the station to a
normal station (non-RI / non-RO) port resolved the problem.

So, you can try it if you want. But be prepared to fall back to a
station port if RI / RO present a problem.

--
Grant. . . .
unix || die