Per the discussions this evening, we did identify a reason why you might need a dhcp namespace for v6 - because networks don't actually have to have routers. It's clear you need an agent in the router namespace for RAs and another one in the DHCP namespace for when the network's not connected to a router, though.
We've not pinned down all the API details yet, but the plan is to implement an RA agent first, responding to subnets that router is attached to (which is very close to what Randy and Shixiong have already done). -- Ian. On 19 December 2013 14:01, Randy Tuttle <randy.m.tut...@gmail.com> wrote: > First, dnsmasq is not being "moved". Instead, it's a different instance > for the attached subnet in the qrouter namespace. If it's not in the > qrouter namespace, the default gateway (the local router interface) will be > the interface of qdhcp namespace interface. That will cause blackhole for > traffic from VM. As you know, routing tables and NAT all occur in qrouter > namespace. So we want the RA to contain the local interface as default > gateway in qrouter namespace > > Randy > > Sent from my iPhone > > On Dec 19, 2013, at 4:05 AM, Xuhan Peng <pengxu...@gmail.com> wrote: > > I am reading through the blueprint created by Randy to bind dnsmasq into > qrouter- namespace: > > > https://blueprints.launchpad.net/neutron/+spec/dnsmasq-bind-into-qrouter-namespace > > I don't think I can follow the reason that we need to change the namespace > which contains dnsmasq process and the device it listens to from qdhcp- to > qrouter-. Why the original namespace design conflicts with the Router > Advertisement sending from dnsmasq for SLAAC? > > From the attached POC result link, the reason is stated as: > > "Even if the dnsmasq process could send Router Advertisement, the default > gateway would bind to its own link-local address in the qdhcp- namespace. > As a result, traffic leaving tenant network will be drawn to DHCP > interface, instead of gateway port on router. That is not desirable! " > > Can Randy or Shixiong explain this more? Thanks! > > Xuhan > > _______________________________________________ > > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev