Re: tuntap apparently misbehaving on osx

[Dave Scott <Dave.Scott@xxxxxxxxxxxxx>]

I don't know if it applies to the dns stuff but to make the http server work 
under Xen I had to add a line

configure interface 'DHCP

In the callback in slides/server.ml

In the case of DHCP there were 2 other glitches which I've sent Anil some pull 
requests for. I guess you want to set a static IP tho ( instead of the 0.0.0.0 
) - I'm sure I saw a config option for that in there somewhere.

-- 
Dave Scott

On Sep 17, 2011, at 11:58 PM, "Richard Mortier" 
<Richard.Mortier@xxxxxxxxxxxxxxxx> wrote:

> i'm porting the dns perf suite over to the new regress/ setup.  with the 
> unix-socket build, i don't seem to be able to contact it at all - and netstat 
> doesn't show anything listening on 53/UDP as i'd expect.  with unix-direct 
> then i see the usual startup but then start seeing many failed writes:
> 
> : mort@greyjay:net$; sudo _build/unix-direct/deens.bin 
> Password:
> Main: startup
> [00000] 2011/08/17T22:06:39Z  info                Deens: starting server, 
> port 53 
> Manager: create
> opendev: /dev/tap0
> Netif: plug tap0
> Manager: plug tap0
> Manager: plug done, to listener
> Manager: init done
> Devices: starting provider Unix.Blkif
> Main: entering runloop
> ARP: who-has 10.0.0.1?
> IPv4: dropping proto 2
> IPv4: dropping proto 2
> IPv4: dropping proto 2
> ARP: transmitting probe -> 10.0.0.1
> EXN: Failure("tap: partial write")
> ARP: updating 10.0.0.1 -> 1e:81:8c:9d:18:0c
> EXN: Failure("tap: partial write")
> EXN: Failure("tap: partial write")
> 
> via "tcpdump -i tap0", pinging 10.0.0.1 from a terminal gets me nothing; 
> pinging 10.0.0.255 shows echo requests from 10.0.0.1 -> 10.0.0.255, and 
> responses from 0.0.0.0 -> 10.0.0.1 which seems odd.
> 
> similar behaviour if i build the tutorial slideset with unix-direct, although 
> with unix-socket it works just fine.
> 
> so- is this a broken setup on my part, or something that's become broken due 
> to eg., new device model?  (or am i just missing something really obvious?!)
> 
> -- 
> Cheers,
> 
> R.
> 
> This message and any attachment are intended solely for the addressee and may 
> contain confidential information. If you have received this message in error, 
> please send it back to me, and immediately delete it.   Please do not use, 
> copy or disclose the information contained in this message or in any 
> attachment.  Any views or opinions expressed by the author of this email do 
> not necessarily reflect the views of the University of Nottingham.
> 
> This message has been checked for viruses but the contents of an attachment
> may still contain software viruses which could damage your computer system:
> you are advised to perform your own checks. Email communications with the
> University of Nottingham may be monitored as permitted by UK legislation.