[nylug-talk] sudo: ruby: command not found on Ubuntu

Y. Ph. philolospher at yahoo.com
Thu Jul 5 18:26:44 EDT 2007


Thank you so much, Chris.  This is very important information.  I really appreciate it your help.

I do have a router that configured for MAC addresses that can access. If virtual box have a different MAC address, should I add that MAC address to the router configuration? 

If the Virtualized Ubuntu access Internet through windows, do I need to configure the Wireless settings,  the wireless setting doesn't show up on the list of the Network Settings in Ubunut virtual machine. Since ethernet device for Ubuntu is virtualized, when I connect to the Internet (through wireless connection), do I have the same protection as I connect to the Internet through WPA on Windows machine? Do I need to reset for specific permission.

Thank you very much,
Y.

Chris Knadle <Chris.Knadle at coredump.us> wrote: On Saturday 30 June 2007, Y. Ph. wrote:
> Thank you for your help.  Do you know why the Inet Address in Ubuntu (I use
> the  ifconfig command) is different from my IP address in Windows when I do
> ipconfig? Does it mean that my Ubuntu Internet doesn't have security setup 
> as Windows, in another word, my Ubuntu connection to the Internet is wide
> open?

   No, I don't think it's a security related issue.  What specific IP address 
you receive is probably not a factor in your case when it comes to specific 
firewall rules, unless you've got firewall rules in your router that are IP 
specific.

   If I remember correctly you're running Ubuntu under VMware, presumably on 
top of Windows.  That means that the ethernet device for Ubuntu is 
virtualized, so it likely has a different MAC address than the Windows 
ethernet device is using.  Most DHCP servers also hand out the same IP 
address that was previously given to a particular MAC address.
   Last I recall I think it is possible for a virtual host to have the same IP 
address as the actual host, but only using NAT [Network Address Translation], 
and using that would mean that the host an machines outside of the host had 
no way of directly getting to the virtual machine by IP address -- because 
the IP address would primarily be that of the host.

   The bottom line is that I don't think there's anything wrong with your 
setup with regards to IP addresses.

   -- Chris

-- 

Chris Knadle
Chris.Knadle at coredump.us
_____________________________________________________________________________
Hire expert Linux talent by posting jobs here :: http://jobs.nylug.org
The nylug-talk mailing list is at nylug-talk at nylug.org
The list archive is at http://nylug.org/pipermail/nylug-talk
To subscribe or unsubscribe: http://nylug.org/mailman/listinfo/nylug-talk


       
---------------------------------
Pinpoint customers who are looking for what you sell. 


More information about the nylug-talk mailing list