Re: Net.Manager

[Vincent Bernardoff <vb@xxxxxxxxxxxxxx>]

On 29/03/2013 18:49, Richard Mortier wrote:
> On 27 Mar 2013, at 11:46, Anil Madhavapeddy wrote:
>
> > On 27 Mar 2013, at 11:44, Vincent Bernardoff <vb@xxxxxxxxxxxxxx> wrote:
> >
> > > On 27/03/2013 11:36, Haris Rotsos wrote:
> > > > sorry replied too late to the first mail. Ok tell me when the code is
> > > > ready for the tap case to see the resulting API and we can see then how
> > > > we can fit something in a more modular way.
> > > For now I made that:
> > > https://github.com/vbmithr/ocaml-tuntap
> > >
> > > This is a Linux/Mac library that covers only creating/attaching tun/tap 
> > > interfaces, extracted out of the mirage tab stubs and completed for Linux.
> > Mort: does this fix your weird Linux routing problem with the old tap code?
> ok, tried this, sort of, i think. short answer: no joy.
>
> that is,
>
> - i pulled and built the latest ocaml-tuntap, producing tunctl.native.
> - i ran "sudo ./tunctl.native add tap0 ; sudo ./tunctl.native inet tap0 
> 10.0.0.2"
> - i ran "make run" in mirage-www
>
> ...and i still get the same results, i.e., i see the outgoing SYN on lo getting 
> a RST in response. i also see pings to 10.0.0.2 being received on and replied 
> to via lo. i tried creating tap1 with address 10.0.0.3 which worked fine, but 
> same results -- trying to get packets (eg., ping) to 10.0.0.3 causes them to be 
> visible on lo and not on tap1.
>
> or am i missing something obvious?
The code in mirage-platform is not using ocaml-tuntap for now… :( Since 
we want to change the design, I did not bother updating the code for 
now, sorry. I could make the changes quite quickly, if you want.
Cheers

Vincent