CentOS - Sep 2016 - Virtualization Networking

> -----Original Message-----
> From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On
> Behalf Of Gordon Messmer
> Sent: Thursday, September 29, 2016 11:47 AM
> To: CentOS mailing list
> Subject: Re: [CentOS] Virtualization Networking
> 
> On 09/28/2016 08:43 AM, tdukes at palmettoshopper.com wrote:
> > I have one of those free domains/DNS from no-ip.com,
> > centos7vm.ddns.net I plan to use as the host name.
> >
> > I want to be able to access this VM from the internet.
> ...
> > This is what I was seeing. Either it lands on the DSL router's
login
> > page or the host's website.
> 
> If you only have one address, you'll need to configure port forwarding
or
a
> "bastion host" from that DSL router (whatever it supports).  Your
"no-ip.com"
> address will simply point at that host.
> 
> > So, how much in the network setup for the new installation do I need
> > to do? Do I need to go with NAT or bridged?
> 
> 
> You have a couple of options for VMs that you want to access from the LAN.
> The best documented and probably most widely used is bridged.
> That one also probably requires the most setup:
> 
> https://access.redhat.com/documentation/en-
> US/Red_Hat_Enterprise_Linux/7/html/Networking_Guide/ch-
> Configure_Network_Bridging.html
> 
> https://access.redhat.com/documentation/en-
> US/Red_Hat_Enterprise_Linux/7/html/Virtualization_Deployment_and_Ad
> ministration_Guide/sect-Network_configuration-Bridged_networking.html
> 
> You can also use macvtap, which doesn't require the use of a special
bridge
> interface, but you do have to enable hairpin mode if you want the KVM
> guest to be able to access its guests.  I honestly can't find much
useful
> documentation.
> 
> https://access.redhat.com/documentation/en-
> US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/
> sect-attch-nic-physdev.html
> 
Thanks, I am running 6.8. 

For whatever reason, the default NAT setup no longer works. I got some kind
of bridge network (mactap) setup that has access to the outside but I still
can't connect locally.

On 09/29/2016 07:54 PM, TE Dukes wrote:
> For whatever reason, the default NAT setup no longer works.
Start over with a new install.  Record each change you make, carefully.
> I got some kind
> of bridge network (mactap) setup that has access to the outside but I still
> can't connect locally.

As I noted, when using the macvtap, the host and guest can't communicate 
unless you enable hairpin mode.

> -----Original Message-----
> From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On
> Behalf Of Gordon Messmer
> Sent: Friday, September 30, 2016 1:01 AM
> To: CentOS mailing list
> Subject: Re: [CentOS] Virtualization Networking
> 
> On 09/29/2016 07:54 PM, TE Dukes wrote:
> > For whatever reason, the default NAT setup no longer works.
> 
> Start over with a new install.  Record each change you make, carefully.
> 
> > I got some kind
> > of bridge network (mactap) setup that has access to the outside but I
> > still can't connect locally.
> 
> 
> As I noted, when using the macvtap, the host and guest can't
communicate
> unless you enable hairpin mode.
> 
I read something about turning off and disabling NetworkManager. I haven't
done this.

I'm getting ready to throw in the towel. If I can't set this up to at
least
access the VM from the LAN, I can't test CentOS 7 and the software I want to
run. It makes it very hard to setup and configure with vi.

Thanks!