cribió:
>
>> No problem. Which solution did you go for?
>>
>> --
>> Sent from the Delta quadrant using Borg technology!
>>
>> Nux!
>> www.nux.ro
>>
>> - Original Message -
>> > From: "Sebastian Gomez"
>> > To: us
-
> > From: "Sebastian Gomez"
> > To: users@cloudstack.apache.org
> > Sent: Friday, 29 January, 2016 10:43:07
> > Subject: Re: cloudstack-agent 4.5 problem with cloudbr bridges
>
> > It worked for me!
> >
> > Oh my God, I spent lot of time try
No problem. Which solution did you go for?
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Sebastian Gomez"
> To: users@cloudstack.apache.org
> Sent: Friday, 29 January, 2016 10:43:07
> Subject: Re: cloudstack-
It worked for me!
Oh my God, I spent lot of time trying to solve it.. Thank a lot!
El vie., 29 ene. 2016 a las 9:44, Sebastian Gomez ()
escribió:
> Thank you Lucian, I will try it and let you know if worked for me.
>
>
>
> El vie., 29 ene. 2016 a las 2:25, Nux! () escribió:
>
>> Hello Sebast
Thank you Lucian, I will try it and let you know if worked for me.
El vie., 29 ene. 2016 a las 2:25, Nux! () escribió:
> Hello Sebastian,
>
> Cloudstack creates a new bridge because it's standard behaviour if you
> mention a VLAN number when you add the public network details.
>
> I believe you
Hello Sebastian,
Cloudstack creates a new bridge because it's standard behaviour if you mention
a VLAN number when you add the public network details.
I believe you can just skip mentioning the VLAN id when you add the public
network, in which case it will just use the bridge you created manual
