Re: [c-nsp] LACP between router VMs (James Bensley)

[Sergio D.]

You can use the following on ovs:

ovs-vsctl set bridge  other-config:forward-bpdu=true

according to the ovs-vsctl docs[0] this includes 01:80:c2:00:00:0x which is
LACP.

[0] http://openvswitch.org/support/dist-docs/ovs-vswitchd.conf.db.5.html


>
>1. Re: [c-nsp] LACP between router VMs (James Bensley)
>
>
> --
>
> Message: 1
> Date: Wed, 8 Nov 2017 18:21:07 +
> From: James Bensley 
> To: adamv0...@netconsultings.com
> Cc: "cisco-nsp@puck.nether.net" ,
> juniper-nsp 
> Subject: Re: [j-nsp] [c-nsp] LACP between router VMs
> Message-ID:
> 

Re: [c-nsp] cisco ip nat question

[Aaron Gould]

You may be able to accomplish it with proxy arp and not have to nat

I recall proxy arp will allow hosts to arp for everything, and the router to 
arp reply to any and all arps on the subnet with its own mac address 

-Aaron


___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] cisco ip nat question

[Mike]

On 11/9/17 4:17 PM, Nick Cutting wrote:

There is more to it.

What is the model and code version of the router? - we need these to help you 
with the configuration.





Fair enough.

Its a Cisco 7201 running 12.2(33)SRE7

Thank you.

___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Re: [c-nsp] cisco ip nat question

[Nick Cutting]

There is more to it.

What is the model and code version of the router? - we need these to help you 
with the configuration.

-Original Message-
From: cisco-nsp [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Mike
Sent: Thursday, November 9, 2017 6:50 PM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] cisco ip nat question

This message originated outside of your organisation.

Hi,


     I have a bunch of dumb devices that don't know how to deal with a default 
gateway. They all live in a subnet 172.16.144.0/20.

     A router lives here @ 172.16.144.1, and my device management station lives 
on another network, say 10.0.1.0/24.

     What I think I want, is for packets going from my management station to 
the dumb devices to be source ip natted so that they appear to come from the 
router itself 172.16.144.1, so that any devices on the
172.16.144.0/20 network that can't understand default gateway, can at least 
respond since the source address they will see will be the router itself and 
within their same subnet.

     How would this be accomplished? Is it as simple as putting 'ip nat inside' 
on the interface facing the dumb devices? Or is there more to it?

Mike-
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

[c-nsp] cisco ip nat question

[Mike]

Hi,


    I have a bunch of dumb devices that don't know how to deal with a 
default gateway. They all live in a subnet 172.16.144.0/20.


    A router lives here @ 172.16.144.1, and my device management 
station lives on another network, say 10.0.1.0/24.


    What I think I want, is for packets going from my management 
station to the dumb devices to be source ip natted so that they appear 
to come from the router itself 172.16.144.1, so that any devices on the 
172.16.144.0/20 network that can't understand default gateway, can at 
least respond since the source address they will see will be the router 
itself and within their same subnet.


    How would this be accomplished? Is it as simple as putting 'ip nat 
inside' on the interface facing the dumb devices? Or is there more to it?


Mike-
___
cisco-nsp mailing list  cisco-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/