<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div>Griffin,</div><div><br></div><div>See the attached for what my Network options looks like. My Adapter(s) 2-4 are grayed out and unclickable, so I can't add anything else.</div><div><br></div><div>Jon</div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Griffin Kelton <<a href="mailto:griffin.kelton@gmail.com">griffin.kelton@gmail.com</a>><br><span style="font-weight:bold">Reply-To: </span> Kitsap Perl Users Group <<a href="mailto:kpug-pm@pm.org">kpug-pm@pm.org</a>><br><span style="font-weight:bold">Date: </span> Sunday, September 16, 2012 11:53 PM<br><span style="font-weight:bold">To: </span> Kitsap Perl Users Group <<a href="mailto:kpug-pm@pm.org">kpug-pm@pm.org</a>><br><span style="font-weight:bold">Subject: </span> Re: [KPUG] Oddities with VM setup<br></div><div><br></div>Jon,<div><br></div><div>You need to somehow enable eth1 to be your host-only adapter. Otherwise, like you said, the connection will by default timeout because 192.168.56.2 won't be online. Just to clarify, this is what my disabled network adapters look like: <a href="http://cl.ly/image/3S3a170H1u3C">http://cl.ly/image/3S3a170H1u3C</a>. This is what they look like when enabled: <a href="http://cl.ly/image/1y1f0G3N2I3X">http://cl.ly/image/1y1f0G3N2I3X</a>. Are you saying that when they are disabled, you are unable to select the "Enable Network Adapter" check box?</div><div><br></div><div>In regards to your ssh client, I used Terminal as well. =)</div><div><br><div>Griffin Kelton<br>(919)306.1135<br><a href="http://www.griffinkelton.com" target="_blank">www.griffinkelton.com</a><br><br>
Please consider the environment before printing this email.<br><br><br><div class="gmail_quote">On Mon, Sep 17, 2012 at 2:34 AM, Jon <span dir="ltr"><<a href="mailto:halfbrown@gmail.com" target="_blank">halfbrown@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word"><div>Lady (Ladies?) & Gentlemen,</div><div><br></div><div>I've run into an odd snag on the VM install for my lovely MacBook Pro, so I thought I'd post to the group to see if anyone has any help because my Google-Fu is sending me around in circles.</div><div><br></div><div>I got all the way to Section E, "Establish a non-console/SSH connection to the local host-only address" and finally hit said snag. I cracked open SSH, typed in:</div><div><br></div><div>ssh –p 22 –v <a href="mailto:jon@192.168.56.2" target="_blank">jon@192.168.56.2</a></div><div><br></div><div>And received the following error:</div><div><br></div><div>ssh: connect to host 192.168.56.2 port 22: Connection timed out</div><div><br></div><div>This got me thinking. Dangerous, yes, but thinking nonetheless. :)</div><div><br></div><div>During Section D, "Debian setup", I ran into a previous snag. Several times I kept getting a problem wherein I would receive the error message:</div><div><br></div><div>Failed to bring up eth1.</div><div><br></div><div>Oddly enough the way I (accidentally) got around that was through a bug I typed into /etc/network/interfaces detailing the auto eth1 and then face eth2 (et c). Nothing alerted me to this until later on in the process when I began debugging my "odd snag" I initially mentioned. Anyhoo… I figured <span style="font-weight:bold">something</span> had to be right since I did all of the apt updates between Section D and Section E, so obviously I had networking out to the inter-tubes. Admittedly, while I'm pretty good with code, hardware has been a mystery to me since circa 1996. And even then, not so much.</div><div><br></div><div>So I've been mucking around Google trying to see what's up, heading to <a href="http://virtualbox.org" target="_blank">virtualbox.org</a> to do the same, and all that jazz. But I'm stumped and was hoping someone could at least point me in the right direction.</div><div><br></div><div>As such, I have a few ideas for where things could have gone wrong, and I thought I'd share.</div><ul><li>When working on the VirtualBlox Manager, under Network, I only have one option, and that's for Adapter 1. I selected Bridged Adapter, the Name is en0: Wi-Fi (Airport), which was the default, and the only other options I have are for Promiscuous Mode (scandalous!), the Mac Address, and a checkbox for "Cable connected". Pretty sure I didn't touch any of those, so I'm feeling good about those. However, in the VM setup instructions under B.5.d.ii, I couldn't set a virtual adapter because I have no option/availability to do so. All of the non-used Adapters listed (2-4) are grayed out and cannot be selected. I presume that's by design via the VirtualBox software or my hardware, so I just skipped it.</li><li>Section D.3, that's where I'm guessing the real issue is. AFAICT I only have 1 Adapter (see my notes above RE: B.5.d.ii), and I keep getting a "hey you can't run 2 auto loads of eth0" error if I don't use eth1, so my thinking is/was I'd have a /etc/network/interfaces file that looks like this:</li></ul><div>auto lo</div><div>iface lo inet loopback</div><div><br></div><div>auto eth0</div><div>allow-hotplug eth0</div><div>iface eth0 inet dhcp</div><div><br></div><div>auto eth1</div><div>iface eth1 inet static</div><div>
address 192.168.56.2</div><div>gateway 192.168.56.1</div><div>netmask 255.255.255.0</div><div>network 192.168.56.0</div><div>broadcast 192.168.56.255</div><div><br></div><div><span style="white-space:pre-wrap"> </span>Yes, that's actually what's in my /etc/network/interfaces file right now. It's that last section I'm really wondering about, and hoping that someone can verify yes/no on if I did that correctly. Yes, I did the restart, yes I tried the ifdown's, etc. Mostly I keep getting messages saying it doesn't recognize eth1.</div><div><br></div><div>I'm guessing that since I had apt/etc. working already, once I get past this issue the rest will be a breeze. That's what I'm hoping for, at least.</div><div><br></div><div>Oh! And one more thing… Section E starts off with "Establish a non-console/SSH connection to the local host-only address". Well, the console <span style="font-weight:bold">is</span> my favorite SSH client. :) Is there some funky issue where if I'm attempting to SSH (and assuming this whole time that I should be SSHing via the VM CLI), that <span style="font-weight:bold">that</span> is the problem? Or at least <span style="font-weight:bold">a</span> problem?</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Jon</div></font></span></div></blockquote></div><br></div></div></span></body></html>