2:11 p.m.
Dan,
I set everything up the way you mentioned. The network I have labeled
"external network" is marked as an "extnet". By which I mean, in the
Dashboard, under "Network Details" for my external network... It has an
entry "Provider Network-> Physical Network: extnet".
I allocated a pool in the range 192.168.1.13 to 192,168.1.99 (I did this
because two of the computers on my physical network are 192.168.1.11 and
192.168.1.12).
The virtual router has an IP address of 192.168.1.13 on the external
network, and the public_subnet on the external network has a gateway of
192.168.1.2.
You're right about my physical router. Its address is 192.168.1.1
I tried pinging from a VM to the Internet, and it still fails.
I then tried allocating floating IPs to a VM, and it still failed to ping
the Internet.
So, I'm still not solved
Thanks for your feedback!
Regards,
...John
On Sat, Mar 19, 2016 at 9:58 PM, Dan Sneddon <dsneddon(a)redhat.com> wrote:
I don't think the range you are using is the problem, although
you should
be using 192.168.1.0/24 as your subnet and 192.168.1.1 as the router
gateway (assuming that the WRT is .1). You can set the allocation pool to a
range like 192.168.1.10-192.168.1.99. Also, assuming your WRT router is .1,
you will have to manually assign the virtual router IP (since the default
is .1 when you create a router on a /24 network).
You say that your VMs are connected through a virtual router. Are you
using floating IPs? You can't just route the VM traffic to the WRT router
without SNAT on the virtual router, so make sure you set that network to
external.
I suspect that the problem here might be that the virtual router was using
the same IP as the WRT router, or that you were doing routing without SNAT
because the network wasn't marked as external.
Dan Sneddon | Principal OpenStack Engineer | dsneddon(a)redhat.com
On Mar 19, 2016, at 4:39 PM, John Alway <jalway(a)gmail.com> wrote:
Hello,
I'm still not able to get snat to work (connecting to the Internet) with
my RDO all-in-one installation, and I'm wondering if my router is the issue.
My router is a Linksys WRT54G, which does not support a "DHCP reservation"
feature. I was able to set a fixed ip on it, because there is a range
available from 192.168.1.2 through to 192.168.1.99, also 192.168.1.150
through 192.168.1.254.
This is according to "toomanydonuts" posting here:
http://community.linksys.com/t5/Wireless-Routers/WRT54G-Static-IP-Questio...
I've been using the lower address range. Could this be the problem, or
should I look elsewhere?
In my setup I have two private subnets, and three VMs. I can ping between
the VMs, but can't ping the Internet. A virtual router connects the
subnets and external network.
I set up my external subnet as 192.168.1.0/28. I use the 28 to limit the
range for my router. The external range is the same as my actual physical
addresses on my LAN.
I should add, I'm not a network guy. I'm learning a lot of networking on
the fly here.
Thanks for any feedback!!
...John
_______________________________________________
Rdo-list mailing list
Rdo-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/rdo-list
To unsubscribe: rdo-list-unsubscribe(a)redhat.com