[Coco] Fwd: IP packets on my coco

[Ron Klein]

Hi Brett,

Great news and so looking forward to the day when the Coco can be online
using a native IP stack.  I'll bet 250 - 500ms.  Will Tormod be able use
this for the Dragon/Coco 2 port of Fuzix as well?

Great work and thank you!

-Ron


On Sun, Jun 5, 2016 at 11:36 AM, Brett Gordon <beretta42 at gmail.com> wrote:

> It has been a slow news week on the list so I thought I would leak some
> exciting Fuzix development stuff here.  Here's hope for actual real-mccoy
> networking for the CoCo.
>
> Cheers!
>
> Brett M Gordon
> ---------- Forwarded message ----------
> From: "Brett Gordon" <beretta42 at gmail.com>
> Date: Jun 5, 2016 12:24 PM
> Subject: IP packets on my coco
>
> > Last week, I compiled the new lwwire spec code.  The spec keeps the
> drivewire stuff that works and throws the broken stuff out. Yesterday, I
> hacked up an extension to the drivewire protocol to present a Linux tun
> iface to the coco.  On the coco side, I used the proposed dw_transaction()
> ioctl to receive IP packets.  A small forth program later, fuzix was
> receiving and displaying ping and tcp syn packets from linux.  I haven't
> tested the sending of IP packets yet, but it's coded.   I'm thinking of
> trying to compile Adam Dunkle's uIP and see if I can ping fuzix from
> linux.  If it fails, at least there will be a link layer ready for Alan.
> And dw_transaction() allows this to happen in user-space - right where
> fuzix wants its native TCP/IP stack.  From my research, uIP takes 4-5k of
> code, and one modest sized packet buffer.  The uIP-TCP/kernel iface will
> need additional send buffering to make it work like BSD sockets expect.
> >
> > Any bets on ping reponse times? ;)
> >
> > Brett M Gordon
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>