Re: Deployment of VNF appliance without VR
Hmm Interesting. Thanks Alex. Will try it out. Regards, Shiv (Sent from mobile device. Please excuse brevity and typos.) On Fri, 19 Apr 2024, 21:10 Alex Mattioli, wrote: > You can set your upstream router with a static ARP entry for the public > IP, this way if your user changes the IP they'll simply lose their own > connectivity. Should be quite easy to automate. > > > > > -Original Message- > From: K B Shiv Kumar > Sent: Friday, April 19, 2024 4:30 PM > To: users@cloudstack.apache.org > Subject: Re: Deployment of VNF appliance without VR > > Hi Wei, > > The main concern with that solution is how do we prevent the user from > going into the VNF and changing the public IP. That can cause an ARP clash > and bring down someone else's system too. That's the only and very major > drawback in that solution. Was wondering if there's any workaround for that. > > Regards, > Shiv > (Sent from mobile device. Please excuse brevity and typos.) > > On Fri, 19 Apr 2024, 19:30 Wei ZHOU, wrote: > > > Hi, > > > > You can deploy the VNF appliance on a shared network as the first > > network > > > > -Wei > > > > On Fri, Apr 19, 2024 at 3:38 PM Kaushik Bora > > wrote: > > > > > > Dear Community, > > > > > > > > > > > >We have been going through the VNF appliance deployment which is > > > available in release 4.19.0. We have successfully tested the VNF > > deployment > > > scenario with the Virtual Router. However, want to evaluate if the > > > VNF appliance can be deployed without the Virtual Router as well, > > > any > > guidance > > > from the community to evaluate the use case(VNF without the VR) is > > > highly appreciated. > > > > > > > > > > > > Thanks & Regards, > > > > > > Kaushik Bora > > > > > > +91-9711100076 > > > > > > > > > > > > > > > -- > > > This message is intended only for the use of the individual or > > > entity to which it is addressed and may contain confidential and/or > > > privileged information. If you are not the intended recipient, > > > please delete the original message and any copy of it from your > > > computer system. You are hereby notified that any dissemination, > > > distribution or copying of this communication is strictly prohibited > > > unless proper authorization has been obtained for such action. If > > > you have received this communication in > > error, > > > please notify the sender immediately. Although IndiQus attempts to > > > sweep e-mail and attachments for viruses, it does not guarantee that > > > both are virus-free and accepts no liability for any damage > > > sustained as a result > > of > > > viruses. > > > > -- > This message is intended only for the use of the individual or entity to > which it is addressed and may contain confidential and/or privileged > information. If you are not the intended recipient, please delete the > original message and any copy of it from your computer system. You are > hereby notified that any dissemination, distribution or copying of this > communication is strictly prohibited unless proper authorization has been > obtained for such action. If you have received this communication in error, > please notify the sender immediately. Although IndiQus attempts to sweep > e-mail and attachments for viruses, it does not guarantee that both are > virus-free and accepts no liability for any damage sustained as a result of > viruses. > -- This message is intended only for the use of the individual or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient, please delete the original message and any copy of it from your computer system. You are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited unless proper authorization has been obtained for such action. If you have received this communication in error, please notify the sender immediately. Although IndiQus attempts to sweep e-mail and attachments for viruses, it does not guarantee that both are virus-free and accepts no liability for any damage sustained as a result of viruses.
RE: Deployment of VNF appliance without VR
You can set your upstream router with a static ARP entry for the public IP, this way if your user changes the IP they'll simply lose their own connectivity. Should be quite easy to automate. -Original Message- From: K B Shiv Kumar Sent: Friday, April 19, 2024 4:30 PM To: users@cloudstack.apache.org Subject: Re: Deployment of VNF appliance without VR Hi Wei, The main concern with that solution is how do we prevent the user from going into the VNF and changing the public IP. That can cause an ARP clash and bring down someone else's system too. That's the only and very major drawback in that solution. Was wondering if there's any workaround for that. Regards, Shiv (Sent from mobile device. Please excuse brevity and typos.) On Fri, 19 Apr 2024, 19:30 Wei ZHOU, wrote: > Hi, > > You can deploy the VNF appliance on a shared network as the first > network > > -Wei > > On Fri, Apr 19, 2024 at 3:38 PM Kaushik Bora > wrote: > > > > Dear Community, > > > > > > > >We have been going through the VNF appliance deployment which is > > available in release 4.19.0. We have successfully tested the VNF > deployment > > scenario with the Virtual Router. However, want to evaluate if the > > VNF appliance can be deployed without the Virtual Router as well, > > any > guidance > > from the community to evaluate the use case(VNF without the VR) is > > highly appreciated. > > > > > > > > Thanks & Regards, > > > > Kaushik Bora > > > > +91-9711100076 > > > > > > > > > > -- > > This message is intended only for the use of the individual or > > entity to which it is addressed and may contain confidential and/or > > privileged information. If you are not the intended recipient, > > please delete the original message and any copy of it from your > > computer system. You are hereby notified that any dissemination, > > distribution or copying of this communication is strictly prohibited > > unless proper authorization has been obtained for such action. If > > you have received this communication in > error, > > please notify the sender immediately. Although IndiQus attempts to > > sweep e-mail and attachments for viruses, it does not guarantee that > > both are virus-free and accepts no liability for any damage > > sustained as a result > of > > viruses. > -- This message is intended only for the use of the individual or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient, please delete the original message and any copy of it from your computer system. You are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited unless proper authorization has been obtained for such action. If you have received this communication in error, please notify the sender immediately. Although IndiQus attempts to sweep e-mail and attachments for viruses, it does not guarantee that both are virus-free and accepts no liability for any damage sustained as a result of viruses.
Re: Deployment of VNF appliance without VR
Hi Wei, The main concern with that solution is how do we prevent the user from going into the VNF and changing the public IP. That can cause an ARP clash and bring down someone else's system too. That's the only and very major drawback in that solution. Was wondering if there's any workaround for that. Regards, Shiv (Sent from mobile device. Please excuse brevity and typos.) On Fri, 19 Apr 2024, 19:30 Wei ZHOU, wrote: > Hi, > > You can deploy the VNF appliance on a shared network as the first network > > -Wei > > On Fri, Apr 19, 2024 at 3:38 PM Kaushik Bora > wrote: > > > > Dear Community, > > > > > > > >We have been going through the VNF appliance deployment which is > > available in release 4.19.0. We have successfully tested the VNF > deployment > > scenario with the Virtual Router. However, want to evaluate if the VNF > > appliance can be deployed without the Virtual Router as well, any > guidance > > from the community to evaluate the use case(VNF without the VR) is highly > > appreciated. > > > > > > > > Thanks & Regards, > > > > Kaushik Bora > > > > +91-9711100076 > > > > > > > > > > -- > > This message is intended only for the use of the individual or entity to > > which it is addressed and may contain confidential and/or privileged > > information. If you are not the intended recipient, please delete the > > original message and any copy of it from your computer system. You are > > hereby notified that any dissemination, distribution or copying of this > > communication is strictly prohibited unless proper authorization has been > > obtained for such action. If you have received this communication in > error, > > please notify the sender immediately. Although IndiQus attempts to sweep > > e-mail and attachments for viruses, it does not guarantee that both are > > virus-free and accepts no liability for any damage sustained as a result > of > > viruses. > -- This message is intended only for the use of the individual or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient, please delete the original message and any copy of it from your computer system. You are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited unless proper authorization has been obtained for such action. If you have received this communication in error, please notify the sender immediately. Although IndiQus attempts to sweep e-mail and attachments for viruses, it does not guarantee that both are virus-free and accepts no liability for any damage sustained as a result of viruses.
Re: Deployment of VNF appliance without VR
Hi, You can deploy the VNF appliance on a shared network as the first network -Wei On Fri, Apr 19, 2024 at 3:38 PM Kaushik Bora wrote: > > Dear Community, > > > >We have been going through the VNF appliance deployment which is > available in release 4.19.0. We have successfully tested the VNF deployment > scenario with the Virtual Router. However, want to evaluate if the VNF > appliance can be deployed without the Virtual Router as well, any guidance > from the community to evaluate the use case(VNF without the VR) is highly > appreciated. > > > > Thanks & Regards, > > Kaushik Bora > > +91-9711100076 > > > > > -- > This message is intended only for the use of the individual or entity to > which it is addressed and may contain confidential and/or privileged > information. If you are not the intended recipient, please delete the > original message and any copy of it from your computer system. You are > hereby notified that any dissemination, distribution or copying of this > communication is strictly prohibited unless proper authorization has been > obtained for such action. If you have received this communication in error, > please notify the sender immediately. Although IndiQus attempts to sweep > e-mail and attachments for viruses, it does not guarantee that both are > virus-free and accepts no liability for any damage sustained as a result of > viruses.
Deployment of VNF appliance without VR
Dear Community, We have been going through the VNF appliance deployment which is available in release 4.19.0. We have successfully tested the VNF deployment scenario with the Virtual Router. However, want to evaluate if the VNF appliance can be deployed without the Virtual Router as well, any guidance from the community to evaluate the use case(VNF without the VR) is highly appreciated. Thanks & Regards, Kaushik Bora +91-9711100076 -- This message is intended only for the use of the individual or entity to which it is addressed and may contain confidential and/or privileged information. If you are not the intended recipient, please delete the original message and any copy of it from your computer system. You are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited unless proper authorization has been obtained for such action. If you have received this communication in error, please notify the sender immediately. Although IndiQus attempts to sweep e-mail and attachments for viruses, it does not guarantee that both are virus-free and accepts no liability for any damage sustained as a result of viruses.
