[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: TCP/IP L95 <-> Linux fails on coax ether (10MB)
Hi,
what is this trumpet talk ? do you mean trumpet winsock ? don't use it in
l95, it only hurts. I also have l95 at work with exactly the same setup
and no problems at all (I use /windows/hosts, too).
Schlomo
On Sat, 19 Sep 1998, Peter L. Peres wrote:
>
> Hello
>
> I have a bare bones L95 machine (not OSR2) that has TCP/IP and the
> ethercard's manufacturer's driver installed. I have only TCP/IP enabled in
> protocols (and nothing else). I have a set of pd TCP/IP tools on it
> (especially, WS_PING).
>
> The Linux host is used for all sorts of things and I'd like to connect
> the L95 to its web server. There is no nameserver anywhere on the network
> (only /etc/hosts).
>
> This does not work. The L95 sends PING packets, Trumpet logs them, the
> light on the ethercard is flashing and the process fails. Trumpet also
> logs ARP requests going out (WHY are there ARP requests if there is no DNS
> configured ?!). There is no gateway, no DNS, no nothing specified in the
> L95 setup and it has a fixed IP. This is reflected in Trumpet's hosts and
> in Linux's /etc/hosts.
>
> PING eventually reports ICMP fail and gives up. All connection requests
> specify IP directly (not name).
>
> Of course connecting to the Linux machine using Linux works and pings
> and all that (with the same computer - dual boot).
>
> Q: What the **** is wrong ?! Ideas (before I start sniffing packets) ? I
> can't believe a packet sniffer is required to get TCP/IP going on a
> Microdoze product. <g> BTW if the packets reported by Trumpet were going
> out unmodified it SHOULD have worked imho.
>
> Peter
>
>
>