Re: [MirageOS-devel] mirage-www on xen and networking (on ARM)

[Magnus Therning <magnus@xxxxxxxxxxxx>]

On 2 April 2015 at 22:32, Magnus Therning <magnus@xxxxxxxxxxxx> wrote:
> On Thu, Apr 02, 2015 at 09:20:42PM +0100, David Scott wrote:
>> On Thu, Apr 2, 2015 at 9:18 PM, Magnus Therning <magnus@xxxxxxxxxxxx> wrote:
>> > Hmm, I'm now wondering if I've done something completely wrong here.
>> > After the re-build with tcpip 2.3.1 I no longer get any asserts, but I
>> > also get absolutely nothing in reply on HTTP requests... that wasn't
>> > exactly what I expected.  I did expect a reply with a bit of HTML.
>> >
>> > ~~~ output on xen console on ARM
>> > Sending DHCP broadcast (length 552)
>> > DHCP response:
>> > input ciaddr 0.0.0.0 yiaddr 192.168.0.27
>> > siaddr 192.168.0.1 giaddr 0.0.0.0
>> > chaddr 00163e2128a900000000000000000000 sname  file
>> > DHCP: offer received: 192.168.0.27
>> > DHCP options: Offer : Unknown(59[4]), Unknown(58[4]), DNS
>> > servers(83.255.245.11,193.150.193.150), Subnet mask(255.255.255.0), Server
>> > identifer(192.168.0.1), Routers(192.168.0.1), Lease time(86400)
>> > Sending DHCP broadcast (length 552)
>> > DHCP response:
>> > input ciaddr 0.0.0.0 yiaddr 192.168.0.27
>> > siaddr 192.168.0.1 giaddr 0.0.0.0
>> > chaddr 00163e2128a900000000000000000000 sname  file
>> > DHCP: offer received
>> >                     IPv4: 192.168.0.27
>> >                                       Netmask: 255.255.255.0
>> >                                                             Gateways:
>> > [192.168.0.1]
>> >  sg:true gso_tcpv4:true rx_copy:true rx_flip:false smart_poll:false
>> > ARP: sending gratuitous from 192.168.0.27
>> > DHCP offer received and bound to 192.168.0.27 nm 255.255.255.0 gw
>> > [192.168.0.1]
>> > Manager: configuration done
>> > ARP responding to: who-has 192.168.0.27?
>> > ARP: transmitting probe -> 192.168.0.11
>> > ARP: updating 192.168.0.11 -> 00:c2:c6:0f:72:dd
>> > conn 1 closed
>> > conn 2 closed
>> > ARP responding to: who-has 192.168.0.27?
>> > conn 3 closed
>> > conn 4 closed
>> > ~~~
>> >
>> > ~~~ on my laptop
>> > % curl http://192.168.0.27/
>> > ~~~
>> >
>> > curl doesn't produce any output, but shortly after invoking it I see a
>> > `conn N closed` on teh Xen console.
>> >
>>
>> Could you grab a tcpdump of that and post the .pcap file?
>
> I've attached it, and put it on my Dropbox just in case the list
> doesn't like attachments.
>
> https://www.dropbox.com/s/u0zoeciy6t30sjz/arm-xen-www.pcap?dl=0
>
> It's captured using `tcpdump -w arm-xen-www.pcap host 192.168.0.27`.
> Let me know you need me to re-capture with some other switches on.

Anyone with any pointers on where I should start looking for this
issue on my own?

Any test suites I can run that might help me locate where in the stack
the issue is?
Or maybe there's a known good version I can revert to just in order to
verify that there's nothing more seriously wrong with my setup?

/M

-- 
Magnus Therning                      OpenPGP: 0xAB4DFBA4
email: magnus@xxxxxxxxxxxx   jabber: magnus@xxxxxxxxxxxx
twitter: magthe               http://therning.org/magnus

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