it, and would update.
>
> Thanks
> Arie
>
> -Original Message-
> From: cisco-nsp-boun...@puck.nether.net
> [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Olof Kasselstrand
> Sent: Thursday, September 10, 2009 13:03
> To: cisco-nsp@puck.nether.net
> Subject:
: Thursday, September 10, 2009 13:03
To: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] small cisco as ethernet bridge, IPv6 broken, sadness
I think there is some serious problems with BVIs and IPv6.
// Olof
On Wed, Sep 9, 2009 at 5:53 PM, Joe Abley wrote:
>
> On 2009-09-09, at 04:56, Bjørn Mork
I think there is some serious problems with BVIs and IPv6.
// Olof
On Wed, Sep 9, 2009 at 5:53 PM, Joe Abley wrote:
>
> On 2009-09-09, at 04:56, Bjørn Mork wrote:
>
>> Joe Abley writes:
>>
>>> interface FastEthernet0/1
>>> description facing the exchange point
>>> bridge-group 1
>>> bridge-gr
On 2009-09-09, at 04:56, Bjørn Mork wrote:
Joe Abley writes:
interface FastEthernet0/1
description facing the exchange point
bridge-group 1
bridge-group 1 output-pattern-list 1100
And this access list does allow e.g. IPv6 multicast frames?
That access list is just cleaning frames being s
On 2009-09-09, at 04:13, Arie Vayner (avayner) wrote:
Did you check for MTU issues?
IPv6 has different MTU requirements than IPv4, and the setup you are
describing is prone to MTU issues due to the reduced MTU on the L2
transport.
That's an interesting idea, but in this case I've tested and t
On 2009-09-08, at 18:47, Michael K. Smith - Adhost wrote:
I don't think the bridge is really transparent due to the 'bridge 1
route ip' on your exchange-point side device. If possible, you might
want to try removing that statement (if you're local to the device, of
course) to see if that does
Joe Abley writes:
> interface FastEthernet0/1
> description facing the exchange point
> bridge-group 1
> bridge-group 1 output-pattern-list 1100
And this access list does allow e.g. IPv6 multicast frames?
Bjørn
___
cisco-nsp mailing list cisco-ns
] On Behalf Of Joe Abley
Sent: Wednesday, September 09, 2009 01:37
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] small cisco as ethernet bridge, IPv6 broken, sadness
I have the following setup in place for remote access to an exchange
point in Toronto:
juniper J2320 router
Hello Joe:
>
> Is there something fundamental I'm missing, here? Why should a
> transparent bridge behave differently with IPv4 than it does with
IPv6?
>
>
> Joe
>
> ! cisco bridge 1
>
> cisco 2620 (MPC860) processor (revision 0x102) with 61440K/4096K bytes
> of memory.
> System image file
I have the following setup in place for remote access to an exchange
point in Toronto:
juniper J2320 router
|
cisco bridge 1
|
| ) telco-provided
---|--- ) layer-2
| ) transport
|
cisco bridge 2
|
e
10 matches
Mail list logo