Hi Mike,

Simply provide the cidr as the destination rather than a host. I.E. 
--host-route destination=192.168.0.0/24,nexthop=10.0.0.1

James

Sent from my iPhone

On Apr 4, 2016, at 8:31 PM, Mike Spreitzer 
<[email protected]<mailto:[email protected]>> wrote:

I assume `--host-route` works with a destination that is a single host.  Is 
there something I can do to establish a routing rule for a destination that is 
a CIDR block?

Thanks,
Mike



From:        Joseph Bajin <[email protected]<mailto:[email protected]>>
To:        James Denton 
<[email protected]<mailto:[email protected]>>
Cc:        Mike Spreitzer/Watson/IBM@IBMUS, openstack-operators 
<[email protected]<mailto:[email protected]>>
Date:        04/04/2016 04:46 PM
Subject:        Re: [Openstack-operators] [neutron] Attach routing rules to 
networks?
________________________________



We use the host-route flag as mentioned above.  It makes it easy to sent 
internet like traffic to a gateway type of box and internal traffic to the 
inside for tenants that do have public access.

On Sat, Apr 2, 2016 at 10:33 PM, James Denton 
<[email protected]<mailto:[email protected]>> wrote:
Hi Mike,

You should be able to update the subnet(s) and use the --host-route flag with 
destination,nexthop pairs. The routes get pushed via DHCP.

James

Sent from my iPhone

On Apr 2, 2016, at 9:28 PM, Mike Spreitzer 
<[email protected]<mailto:[email protected]>> wrote:

Is there a way to attach a routing rule to a network or subnet, with the 
consequence that each device attached to that net or subnet gets that routing 
rule?

Thanks,
Mike


_______________________________________________
OpenStack-operators mailing list
[email protected]<mailto:[email protected]>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

_______________________________________________
OpenStack-operators mailing list
[email protected]<mailto:[email protected]>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators




_______________________________________________
OpenStack-operators mailing list
[email protected]
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Reply via email to