Re: [MirageOS-devel] mirage-net-unix problems

[Thomas Gazagnaire <thomas@xxxxxxxxxxxxxx>]

> Actually, I just tried it and I have the same problem with tap0 not
> being persistent on Ubuntu 14.04, and this is because
> https://github.com/mirage/ocaml-tuntap hasn't been released yet since
> PR #9.

I'm happy to cut a new release of ocaml-tuntap if it can helps solving the 
problems.

This can be tested by doing `opam pin add tuntap --dev`

>> (This isn't helped by me now using mirage-net-macosx for most of my
>> day-to-day dev, which uses a completely different codepath as tuntap no
>> longer works usefully on OSX as of Yosemite).

Same thing here, I don't use ocaml-tuntap at all so it's hard to track if it's 
broken. If something feels like binding all the basic tests of ocaml-tuntap 
into an allcotest binary and make it run under Travis CI (if that's possible) 
that would be great. I'll add it to my todo list anyway.

Thomas


>> 
>> -anil
>> 
>> On 30 Apr 2015, at 23:49, Robert Ream <robertream@xxxxxxxxx> wrote:
>> 
>> An update: I just cloned the mirage-net-unix repo and ran the tests. This is
>> what I got:
>> 
>> sudo ./test.native
>> plugging into tap0 with mac c2:9d:56:19:d7:2c..
>> Netif: connect tap0
>> connected
>> Netif: error, terminating listen loop
>> .
>> Ran: 1 tests in: 0.00 seconds.
>> OK
>> 
>> And the tun0 interface disappeared as well.
>> 
>> 
>> 
>> On Thu, Apr 30, 2015 at 2:55 PM, Robert Ream <robertream@xxxxxxxxx> wrote:
>>> 
>>> Ok, I'm still stumped.
>>> 
>>> Two things happen with pretty much all of the network examples when I
>>> build and execute them for unix: 1) they promptly exit with a "Netif: error,
>>> terminating listen loop" and 2) tun0 disappears and must be recreated every
>>> time.
>>> 
>>> 1) I tracked down the lines of code in mirage-net-unix that cause this
>>> error message:
>>> 
>>> let page = Io_page.get 1 in read t page >>= function | `Error _ -> printf
>>> "Netif: error, terminating listen loop\n%!"; return ()
>>> 
>>> So it is running into an error when reading a page from the network.
>>> It would be nice to pretty print the _ of `Error _ instead of drop it on
>>> the floor.
>>> 
>>> 2) I couldn't find anywhere in the code that remotely appeared to be
>>> messing with or deleting the tun0 interface. But I wonder if the error I'm
>>> seeing is due to the tun0 disappearing?
>>> 
>>> -Robert
>> 
>> 
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>> 
>> 
>> 
>> _______________________________________________
>> MirageOS-devel mailing list
>> MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
>> 
> 
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel


_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel