Re: Remote access to Freebsd server
If you use NAT network setting in vmware or virtualbox or something else in your win 7. It cannot be access to the virtual server from your host throught network. You must use bridge network setting in your software. On Wed, Apr 13, 2011 at 11:37 PM, afiddler10 wrote: > Hi, I am new to the Linux environment. I am trying to build a virtual > Freebsd server to run another virtual device (a Juniper router). I have > found that after building the base operating system that I cannot remotely > access the virtual Freebsd server. I have tried using both Qemu and VMware > with the same result. It looks to me as though the server has a default > setting that allows it to contact other devices (e.g., I can ping, ftp, > telnet, etc., other devices from my Freebsd server) but I cannot ping, > ftp, telnet into the Freebsd server from my host PC. My host is a Windows 7 > desktop, but I have tried pinging from another virtual device and cannot get > a response from the Freebsd server. I do not believe that the issue is my > Windows 7 PC. > > I have tried the newest Disk 1 ISO image of Freebsd, 8.2, but I've also > tried a few other images with the same result. > > I have combed through the documentation, tried configuring the firewall > using the "open" template, tried to disable the packet filter in rc.conf > (pf_enable="NO"), to no avail. I cannot reach the Freebsd server no matter > what I have tried, and I feel I have exhausted my options. The ports are > open and responsive on the virtual server itself, but access seems to be > blocked to the Freebsd server. > > I am hoping you can tell me how to change the default settings on the > Freebsd server to allow access from my Windows 7 host PC. Hopefully it does > not involve manually rebuilding the kernel! > > Thanks for your help! > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscr...@freebsd.org" > -- 非淡薄无以明志，非宁静无以致远 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Remote access to Freebsd server
Damien Fleuriot wrote: > > > On 4/13/11 6:40 PM, Michael J. Kearney wrote: [snip] >> >> Hi, I am new to the Linux environment. FreeBSD is *NOT* Linux! >> I am trying to build a virtual >> Freebsd server to run another virtual device (a Juniper router). I have >> found that after building the base operating system that I cannot >> remotely access the virtual Freebsd server. I have tried using both Qemu >> and VMware with the same result. It looks to me as though the server has >> a default setting that allows it to contact other devices (e.g., I can >> ping, ftp, telnet, etc., other devices from my Freebsd server) but I >> cannot ping, ftp, telnet into the Freebsd server from my host PC. My >> host is a Windows 7 desktop, but I have tried pinging from another >> virtual device and cannot get a response from the Freebsd server. I do >> not believe that the issue is my Windows 7 PC. >> >> I have tried the newest Disk 1 ISO image of Freebsd, 8.2, but I've also >> tried a few other images with the same result. >> >> I have combed through the documentation, tried configuring the firewall >> using the "open" template, tried to disable the packet filter in rc.conf >> (pf_enable="NO"), to no avail. I cannot reach the Freebsd server no >> matter what I have tried, and I feel I have exhausted my options. The >> ports are open and responsive on the virtual server itself, but access >> seems to be blocked to the Freebsd server. >> >> I am hoping you can tell me how to change the default settings on the >> Freebsd server to allow access from my Windows 7 host PC. Hopefully it >> does not involve manually rebuilding the kernel! >> [snip] > > > This has nothing to do with firewalling. > > He's very likely using NAT on his virtual machine. > > So outgoing connections work just fine: NAT from the guest through the > host. > > But inbound connections fail, and rightly so: NO NAT *to* the guest > through the host. I use VirtualBox these days, but if memory serves it is very much like Vmware in this regard. The OP needs to understand that the default install provides a NAT and a DHCP for the guest VM so it can be brought up automagically. I know in the VirtualBox documentation it is clearly explained about how incoming connections are not passed through this NAT. There are typically 3 networking configurations available: the default as described above, bridged, and host-only. Host-only does exactly what it sounds like - only the host machine and guest may communicate with each other. Bridged networking is what you want to set up if you want your VM to be totally available to your outside network. Hint: the "bridge" is not on the VM guest OS side, but rather the bridge would connect your Windows 7 host's NIC to the VM. A bridged config replaces the default install NAT. I haven't used Vmware for a while now, but in VirtualBox you can use the VBoxManage command line to enable port forwards in the default install's NAT. This is OK if you only want to make a small number of services available, like let's say only a web server on port 80. But you'll want a bridged config if you want the entire VM visible. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Remote access to Freebsd server
On 4/13/11 6:40 PM, Michael J. Kearney wrote: > /var/log/security and "ipfw list" ftw. .. if a rule maches your configuration > atm > > afiddler10 wrote: > > > Hi, I am new to the Linux environment. I am trying to build a virtual > Freebsd server to run another virtual device (a Juniper router). I have > found that after building the base operating system that I cannot remotely > access the virtual Freebsd server. I have tried using both Qemu and VMware > with the same result. It looks to me as though the server has a default > setting that allows it to contact other devices (e.g., I can ping, ftp, > telnet, etc., other devices from my Freebsd server) but I cannot ping, ftp, > telnet into the Freebsd server from my host PC. My host is a Windows 7 > desktop, but I have tried pinging from another virtual device and cannot get > a response from the Freebsd server. I do not believe that the issue is my > Windows 7 PC. > > I have tried the newest Disk 1 ISO image of Freebsd, 8.2, but I've also tried > a few other images with the same result. > > I have combed through the documentation, tried configuring the firewall using > the "open" template, tried to disable the packet filter in rc.conf > (pf_enable="NO"), to no avail. I cannot reach the Freebsd server no matter > what I have tried, and I feel I have exhausted my options. The ports are > open and responsive on the virtual server itself, but access seems to be > blocked to the Freebsd server. > > I am hoping you can tell me how to change the default settings on the Freebsd > server to allow access from my Windows 7 host PC. Hopefully it does not > involve manually rebuilding the kernel! > > Thanks for your help! > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" This has nothing to do with firewalling. He's very likely using NAT on his virtual machine. So outgoing connections work just fine: NAT from the guest through the host. But inbound connections fail, and rightly so: NO NAT *to* the guest through the host. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Remote access to Freebsd server
2011/4/13 afiddler10 > Thank you very much. What I did was set up two interfaces on the VMware > server, one bridged and one routed. I was able to access the routed > interface from my Windows 7 host. Thanks for your help! > > You are welcome. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Remote access to Freebsd server
On Wed, Apr 13, 2011 at 09:40, Matthew Seaman wrote: > On 13/04/2011 16:37, afiddler10 wrote: > Edit the file /etc/rc.conf and add the line: > > sshd_enable="YES" > > Then run this command as root: > > # /etc/rc.d/sshd start > > (you only need to do that as a one-off -- adding the line to rc.conf > means the daemon will be started automatically on reboot from now on) > > Then you can use a SSH client from windows to remote login to your > FreeBSD box. If you need a client, try putty from > > http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html > > Nb. by default, you won't be able to SSH in as root -- so set yourself > up a normal user account, add it to the wheel group and then use su(1) > once you've logged in. As ever, the Handbook is your friend for > instructions on how to do this sort of stuff. In the interest of preventing newb pain: Please note that the entry for /etc/rc.conf must be exact. In particular, *do not* miss either of the quote marks, or your machine will hang at next boot, and force you to boot into single user mode to recover from it by adding the missing quote mark and booting again. This is not the end of the world, but until you figure it out, it can induce feelings of fear, nausea, helplessness and acute embarrassment. However, about the third time you've done it, and recovered from it by your own efforts, it's no longer a big thing. Kurt ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Remote access to Freebsd server
Hello 2011/4/13 afiddler10 : > Hi, I am new to the Linux environment. FreeBsd its not Linux environment. I am trying to build a virtual Freebsd server to run another virtual device (a Juniper router). I have found that after building the base operating system that I cannot remotely access the virtual Freebsd server. I have tried using both Qemu and VMware with the same result. It looks to me as though the server has a default setting that allows it to contact other devices (e.g., I can ping, ftp, telnet, etc., other devices from my Freebsd server) but I cannot ping, ftp, telnet into the Freebsd server from my host PC. My host is a Windows 7 desktop, but I have tried pinging from another virtual device and cannot get a response from the Freebsd server. I do not believe that the issue is my Windows 7 PC. > Try, on the wmware settings > network adapter set to bridged. Regards. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Remote access to Freebsd server
On 13/04/2011 16:37, afiddler10 wrote: > Hi, I am new to the Linux environment. I am trying to build a > virtual Freebsd server to run another virtual device (a Juniper > router). I have found that after building the base operating system > that I cannot remotely access the virtual Freebsd server. I have > tried using both Qemu and VMware with the same result. It looks to > me as though the server has a default setting that allows it to > contact other devices (e.g., I can ping, ftp, telnet, etc., other > devices from my Freebsd server) but I cannot ping, ftp, telnet into > the Freebsd server from my host PC. My host is a Windows 7 desktop, > but I have tried pinging from another virtual device and cannot get a > response from the Freebsd server. I do not believe that the issue is > my Windows 7 PC. Verb. Sap. Don't confuse FreeBSD with Linux. Especially on FreeBSD mailing lists. It's like mistaking a Scotsman for an Englishman. Tends to cause a lot of red faces and shouting, if not actual fisticuffs... Hmmm... with the firewall config set to 'open', ping should work. Are you behind a NAT gateway? Anyhow, your problem is this: you need to turn /on/ a daemon process to enable remote access. Unlike many widely used OSes, FreeBSD ships with just about everything available in the OS turned off. Which might seem perverse to the uninitiated, but trust me; it's a real blessing over all. Edit the file /etc/rc.conf and add the line: sshd_enable="YES" Then run this command as root: # /etc/rc.d/sshd start (you only need to do that as a one-off -- adding the line to rc.conf means the daemon will be started automatically on reboot from now on) Then you can use a SSH client from windows to remote login to your FreeBSD box. If you need a client, try putty from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html Nb. by default, you won't be able to SSH in as root -- so set yourself up a normal user account, add it to the wheel group and then use su(1) once you've logged in. As ever, the Handbook is your friend for instructions on how to do this sort of stuff. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: Remote access to Freebsd server
/var/log/security and "ipfw list" ftw. .. if a rule maches your configuration atm afiddler10 wrote: Hi, I am new to the Linux environment. I am trying to build a virtual Freebsd server to run another virtual device (a Juniper router). I have found that after building the base operating system that I cannot remotely access the virtual Freebsd server. I have tried using both Qemu and VMware with the same result. It looks to me as though the server has a default setting that allows it to contact other devices (e.g., I can ping, ftp, telnet, etc., other devices from my Freebsd server) but I cannot ping, ftp, telnet into the Freebsd server from my host PC. My host is a Windows 7 desktop, but I have tried pinging from another virtual device and cannot get a response from the Freebsd server. I do not believe that the issue is my Windows 7 PC. I have tried the newest Disk 1 ISO image of Freebsd, 8.2, but I've also tried a few other images with the same result. I have combed through the documentation, tried configuring the firewall using the "open" template, tried to disable the packet filter in rc.conf (pf_enable="NO"), to no avail. I cannot reach the Freebsd server no matter what I have tried, and I feel I have exhausted my options. The ports are open and responsive on the virtual server itself, but access seems to be blocked to the Freebsd server. I am hoping you can tell me how to change the default settings on the Freebsd server to allow access from my Windows 7 host PC. Hopefully it does not involve manually rebuilding the kernel! Thanks for your help! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Remote access to Freebsd server
/var/log/security and " ipfw list " ftw afiddler10 wrote: Hi, I am new to the Linux environment. I am trying to build a virtual Freebsd server to run another virtual device (a Juniper router). I have found that after building the base operating system that I cannot remotely access the virtual Freebsd server. I have tried using both Qemu and VMware with the same result. It looks to me as though the server has a default setting that allows it to contact other devices (e.g., I can ping, ftp, telnet, etc., other devices from my Freebsd server) but I cannot ping, ftp, telnet into the Freebsd server from my host PC. My host is a Windows 7 desktop, but I have tried pinging from another virtual device and cannot get a response from the Freebsd server. I do not believe that the issue is my Windows 7 PC. I have tried the newest Disk 1 ISO image of Freebsd, 8.2, but I've also tried a few other images with the same result. I have combed through the documentation, tried configuring the firewall using the "open" template, tried to disable the packet filter in rc.conf (pf_enable="NO"), to no avail. I cannot reach the Freebsd server no matter what I have tried, and I feel I have exhausted my options. The ports are open and responsive on the virtual server itself, but access seems to be blocked to the Freebsd server. I am hoping you can tell me how to change the default settings on the Freebsd server to allow access from my Windows 7 host PC. Hopefully it does not involve manually rebuilding the kernel! Thanks for your help! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Remote access to Freebsd server
Hi, I am new to the Linux environment. I am trying to build a virtual Freebsd server to run another virtual device (a Juniper router). I have found that after building the base operating system that I cannot remotely access the virtual Freebsd server. I have tried using both Qemu and VMware with the same result. It looks to me as though the server has a default setting that allows it to contact other devices (e.g., I can ping, ftp, telnet, etc., other devices from my Freebsd server) but I cannot ping, ftp, telnet into the Freebsd server from my host PC. My host is a Windows 7 desktop, but I have tried pinging from another virtual device and cannot get a response from the Freebsd server. I do not believe that the issue is my Windows 7 PC. I have tried the newest Disk 1 ISO image of Freebsd, 8.2, but I've also tried a few other images with the same result. I have combed through the documentation, tried configuring the firewall using the "open" template, tried to disable the packet filter in rc.conf (pf_enable="NO"), to no avail. I cannot reach the Freebsd server no matter what I have tried, and I feel I have exhausted my options. The ports are open and responsive on the virtual server itself, but access seems to be blocked to the Freebsd server. I am hoping you can tell me how to change the default settings on the Freebsd server to allow access from my Windows 7 host PC. Hopefully it does not involve manually rebuilding the kernel! Thanks for your help! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
