On 03/05/2014 10:23 PM, Alexandru Gheorghe wrote: > On 03/04/2014 12:19 AM, Alexandru Gheorghe wrote: >> On 03/03/2014 10:53 PM, Lyndon Nerenberg wrote: >>> >>> On Mar 3, 2014, at 12:52, Alexandru Gheorghe <[email protected]> wrote: >>> >>>> should we gather some configuration steps/examples for known stable >>>> builds of vbox and post them in a wiki somewhere(?) >>> >>> Yes! That's what the wiki is for. >>> >> >> sure, I agree. I am only enquiring so as to brainstorm if we should >> actually (and be better of) providing a sort of how-to in debugging >> network setup on plan9 (besides what is already on the net). >> >> i.e., even if somebody runs into trouble (ultimately), it is better off >> posting his output of: >> >> cat /net/ndb >> >> ls /net | grep ether (optional) >> ls /net/ether* >> >> ip/ipconfig -DGP >> >> >> in case he/she is running in recv timeout for 15 secs; shortcut: >> >> ppid=`{ps | grep ipconfig | awk '{print $2}'} >> echo kill > /proc/$ppid/note >> >> sorry for the ` as I am writing from GNU/Linux >> >> >> this may not fully represent what is needed, but this is what I could >> gather in few minutes of man pages and some trial and error, after only >> 30 minutes of Plan9 experience. so I am sure far more experienced users >> from the mailinglist can contribute to the article >> >> I will try to tackle it this weekend from this approach/point of view, >> maybe I can come up with something rather useful, if not, at least >> networking setup for the build I use of vbox/os/v > > ersion etc. >> > > Hmm, actually related to this, I encounter dhcprecv read timed out. > I searched and seems there are some interrupt related "issues", this > happens with VirtualBox (4.1.18_Debian r78361) for me, not on bare > metal. NIC is in NAT, tried with a second NIC in bridged; definitely not > the NIC as the below code also points out in !0 and !1 > > dhcp.c: > ------- > void > dhcprecv(void) > { > [...] > uchar buf[8000], vopts[256], taddr[IPaddrlen]; > [...] > memset(buf, 0, sizeof buf); > alarm(1000); > !0 n = read(conf.fd, buf, sizeof buf); > alarm(0); > > if(n < 0){ > rerrstr(err, sizeof err); > !1 if(strstr(err, "interrupt") == nil) > warning("dhcprecv: bad read: %s", err); > else > DEBUG("dhcprecv: read timed out"); > return; > > > n <- ipconfig.h: > ---------------- > typedef struct Conf Conf; > [...] > struct Conf > { > [...] > /* dhcp specific */ > int fd; > > > Any ideas? I don't seem to find plan9.ini to try the fix Akshat Kumar > pointed out in [1]; all the other answers from erik and ron are bare > metal hardware related (like the original post). How to deal with this > in VirtualBox? > > Chipset is PIIX3 [2] > > > References: > [1] > https://groups.google.com/forum/?_escaped_fragment_=topic/comp.os.plan9/9nlmIoY4-C8#!topic/comp.os.plan9/9nlmIoY4-C8 > > [2] https://www.virtualbox.org/manual/ch03.html#settings-motherboard > (under Chipset section) -- there is another option "ICH9" and the MSI > seems a plus; not sure how this will interact with Plan9 but I'll give > it a go >
OK, bad idea. I got it fixed finally.
Chipset for motherboard certainly: PIIX3
NIC info:
- Attached: NAT
- Adapter type (changing this made it working): Intel PRO/1000 MT Server
(82545EM)
- Promisc. mode: Deny
- No port forwarding
Can ping IPs (Google dns: 8.8.8.8 for example), now I have to setup dns.
--
; Alexandru Gheorghe
; alghe.global {at} gmail {dot} com
; OpenPGP key ID 0xCAF985D2
signature.asc
Description: OpenPGP digital signature
