T.R | Title | User | Personal Name | Date | Lines |
---|
951.1 | Yes and no... | TWICK::PETTENGILL | mulp | Fri May 23 1997 03:12 | 18 |
| I can think of no reason that SNAP wouldn't work with DU's LANE, but DU
doesn't support LANE the same way that they support an Ethernet device;
ie., if its Ethernet then everything Ethernet goes.
Each of the Ethernet protocol applications need to be qualified with LANE
and only a limited number have been qualified.
However, going beyond that point, since LANE is Ethernet frame based,
for the most part, there is no reason to do SNAP. For example, when
you go from Ethernet to FDDI you need to convert from Ethernet to SNAP
and then when you return to Ethernet, you convert any SNAP frame with
a 00-00-00 id (back) to Ethernet. This means that if you transmit an
IP packet with in an 802 SNAP frame, if it traverses most bridges it will
be converted to an Ethernet frame. There are knobs to control some specifics,
but in general, SNAP isn't used very often on Ethernet which is what LANE
emulates.
What SNAP protocol are they interested in? Appletalk? IPX?
|
951.2 | SNAP needed for TCP/IP over LANE to IBM OSA2 | TAV02::YAIR | Yair Tsoran, Israel, DTN 882-3094 | Tue May 27 1997 07:23 | 10 |
| My customer wishes to communicate with IBM Mainframe that has OSA2 ATM 155Mbps
connection. The ONLY way the IBM OSA2 can communicate is LANE (Ethernet or Token
Ring format) with TCP/IP SNAP. They don't support CLIP either.
SUN's LANE TCP/IP implementation is Ethernet format only. No SNAP suuport.
Any formal answer for TCP/IP SNAP over LAN in DU?
Thanks,
Yair
|
951.3 | TCP/IP with SNAP not supported | SMURF::GREBUS | DTN 381-1426 - Digital Unix | Wed May 28 1997 12:23 | 16 |
| The implementation of LANE on DU is such that it uses the same
kernel interfaces as an Ethernet adapter. So in theory, anything that
works over Ethernet will work over LANE.
However, LANE does not behave exactly like an Ethernet adapter, so I'm
reluctant to say that something is supported if there hasn't been at
least some testing.
In the case of TCP/IP with SNAP, I think you are still out of luck.
As best I can tell, SNAP over any Ethernet device is only supported
when you access the device through the DLI interface (i.e. when
directly accessing the Ethernet hardware). We don't support
running TCP/IP with SNAP encapsulation.
/gary
|
951.4 | Correction - it probably will work | SMURF::GREBUS | DTN 381-1426 - Digital Unix | Wed May 28 1997 14:24 | 12 |
| A correction to what was in .-1:
Incoming SNAP encapsulation for TCP/IP is supported. Enabling an
interface to send SNAP encapsulated TCP/IP requires using an
undocumented flag to ifconfig
ifconfig <iface> snap|-snap
After some testing, it looks like this works for LAN Emulation as well.
I don't know why the sending option is undocumented.
So assuming the IBM system doesn't expect something unusual in the SNAP
header, we can probably talk to it with LANE.
|