From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <45E6D1F1.8020409@arcepi.net> Date: Thu, 1 Mar 2007 14:15:29 +0100 From: Armando Camarero User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: erik quanstrom Subject: Re: [9fans] Re: booting a terminal in qemu References: <7d3530220702271130w3b4dac5fld4a48f8cc5626093@mail.gmail.com> <7d3530220702271440l1315137fm8522ff3a00d2f853@mail.gmail.com> <45E5D946.7080902@arcepi.net> <20070301031118.60F131F35FD@medicine-bow.quanstro.net> In-Reply-To: <20070301031118.60F131F35FD@medicine-bow.quanstro.net> Content-Type: text/plain; charset=UTF-8 Cc: 9fans@cse.psu.edu Content-Transfer-Encoding: quoted-printable Topicbox-Message-UUID: 170f9a96-ead2-11e9-9d60-3106f5b1d025 erik quanstrom escribi=C3=B3: > you learn something new every day. i didn't know about the -p option t= o ip/ipconfig. > > the function that does the work for dhcp and ip/ipconfig is parseipmask= (2). > parseipmask does not differentiate between "255.255.255.0" and "/120", > so it is not likely to be the problem. > > the other difference in your ndb entries is the missing dns entry in > the second. how did you check that the network doesn't work? have you= tried to > ping the gateway? > ip/ping 10.0.2.2 > if that works, it's a dns problem. > > - erik I tried again and network works. I tried network using links the first time, but it doesn't seem to understand that 172.26.0.4 shouldn't be resolved via DNS. Ping to the QEMU gateway works and I can test that TCP does too using ssh (well, I just see the error message that says it doesn't support SSH2). Armando.