Greg, thanks for that input... I just tested and it seems that while ping does not work networking is working o.k... I am new to VBOX so bare with me. This behavior with the networking does not work like this in VMware. I know there different products BUT I was expecting for this to work the same.
Right after I did my fresh debian install I just proceeded to do some pings to test networking as my minimal install does not offer much other ways to test. While I understand now that is the normal behavior I must say I don't like this. One should be able to ping similar to VMware. I don't see the rational of not making ping work or why one can't update the resolv.conf to reflect other IP's for nameservers. Anyway, i am glad this works now and will test the hosting/bridging networking as I was having problems with that too. Again, thanks for your help!!! Joe On 8/12/07, Gregory Nowak <[EMAIL PROTECTED]> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Sun, Aug 12, 2007 at 10:38:16PM -0400, Joe Leo wrote: > > I'm noticing that in my resolve.conf VBOX sets up IP 10.0.2.3 for > > nameserver. I've tried to remove this IP to place my ISP dns IP and the > IP > > address does not hold. It always reverts back to the 10.0.2.3... > > This is the expected behavior when using dhcp. It is possible however > to tell the dhcp client not to touch resolv.conf. Again though, do you > have a particular reason for using your isp's dns server, instead of > the one that vbox provides? Also, since your resolv.conf is being > updated, that's a good indication that everything does work as > expected, when it comes to the guest being assigned an ip address, > which should imply as well that the connection itself works also. > > > > > As mentioned in last email, I changed my guess networking to DHCP and > the > > guess machine is assigned a 10.0.2.15... > > This is again expected behavior, and it also shows that things seem to > work as they should. > > > I can ping 10.0.2.15 and 10.0.2.2... > > However, still can't ping any outside IP addresses. I think the problem > > could be with the resolv.conf nameserver IP. I need to change this BUT > as I > > said the confif is not holding. > > No, it looks like everything is just fine. As has been mentioned, > section 6.2 of the vbox manual has something to say about ping. In a > nutshell, you can keep pinging until the world ends, and you won't get > a single response. Pinging inside of vbox is not, I repeat, is not the > way to test your connection to the outside world. Use some other way, > such as opening a web page, to verify your connection from the guest > to the outside world. > > Greg-- > > > web site: http://www.romuald.net.eu.org > gpg public key: http://www.romuald.net.eu.org/pubkey.asc > skype: gregn1 > (authorization required, add me to your contacts list first) > > - -- > Free domains: http://www.eu.org/ or mail [EMAIL PROTECTED] > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > > iD8DBQFGv8tu7s9z/XlyUyARAhRzAKDDszWkbPMNTS/2EWs7YweztDUxAwCfaonQ > QqXu7R9ZbF1nU8lsvU8zdps= > =IFx5 > -----END PGP SIGNATURE----- > > _______________________________________________ > vbox-users mailing list > [email protected] > http://vbox.innotek.de/mailman/listinfo/vbox-users >
_______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
