Pierre Labastie wrote:
If I am allowed to comment on this without being accused of all crimes on
Earth,
Please stop these types of comments.
I'd agree that it may be a good idea to have both methods on the page
(the bridge allows to connect on any port: telnet, pop, .... , while port
forwarding has to be set up for each port. OTOH, port forwarding can be set up
by a user). Changing the sentence as Ken wrote is a good idea too. I can do
that, but I'd rather finish the ticket on Kernel Configuration first, so if
anybody else wants to take it, please do.
I can do that, but would like to discuss first.
As the book says, networking can be brought up by adding -net nic -net
user to the qemu line. The problem with that is that it doesn't set up
forwarding or configure the host.
For example, my local network is set up on 192.168.0.x and the qemu dhcp
server sets up the client as 10.0.2.15. I can't ping anything on the
192 network from the client or vice versa.
If we do expand the discussion to add
-net user,hostfwd=tcp::2222-10.0.2.15:22
we still would have problems getting out. For instance ntp or dns would
not work on the guest AFAICT. We also couldn't ping the client from the
host or other network system. In other words, I think the hostfwd
solution is a limited solution.
I may be wrong here. If so, please tell me what else is needed.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
