Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- Separate VMs on a network.
- I have my own box with dedicated internet and block of public IPs from ISP.
- Cable with internet goes to one port of a managed switch (Brocade VDX 6740).
- ++++++++++++++
- list of top cheapest host http://Listfreetop.pw
- Top 200 best traffic exchange sites http://Listfreetop.pw
- free link exchange sites list http://Listfreetop.pw
- list of top ptc sites
- list of top ptp sites
- Listfreetop.pw
- Listfreetop.pw
- +++++++++++++++
- Next port is used by a server.
- I want to sell VPSs from this server.
- I wonder how to separate VMs network discovery-wise. I can imagine to use VLANs. How it should be done to work with lets say Virtualizor to generate VMs already in different VLANs? Is there any other way to isolate them? Any other setup is needed?
- I think easy way is split into small subnet but I guess you have a small IP block, so its a waste of resources.
- 2nd easy is to block discovery-wise using firewall rules.
- Panamaserver.com
- Offshore Shared Hosting, VPS and Dedicated Servers in Panama
- Shouldn't client receive direct access to VPS via public IP?
- I plan to have more VPS in near future than I have IPs right now. It seems like having firewall on many connections will require very fast firewall box and this seems not cost-efficient in my case at the moment. I was experimenting with Firewall on pfSense -I know it isn't as good as hardware solution- but even with it I had poor performance using quite fast server.
- The best way to set this up is to allocate a public ip to an internal ip that the client has access to. That public IP will be routable to the private IP. This allows the customer to also have private VPS servers that are not publicly accessible on the internet and prevent them from using IPs that are not actually assigned to them when you put the client in their own VLAN. This will also insure they can only see their own traffic and if they want to setup multiple IPs they will need to go through you to get them routed publicly to the internet which you can automate after they pay for an additional IP. If your pfsense is going slow you probably have something misconfigured or something turned on that is very CPU intensive.
- Could someone tell his process setting up VLANs for public IPs.
- Do you setup them on the fly as needed or is there a way to make VLANs for public IPs, that will be picked up by mentioned virtualizor when client buys a VPS.
- have you researched how to setup a global VLAN on the switch side?
- Lee L. Account Manager | HIVELOCITY - Everything Bare Metal | You Imagine It, We deploy it.
- Instant Deployment | Fully Custom | Standalone | Dedicated Cloud | Dedicated Storage | cPanel | OpenStack | Proxmox | Windows | Linux
- TAMPA | MIAMI | LOS ANGELES | ATLANTA | NYC | DALLAS | FRANKFURT
- Thank you for reply. This sounds good. I was hoping to cut-out the router from the picture but in this case I need to resolve pfSense issue first. pfSense configuration is rather good and CPU usage on a whole box is very very low as that server is dedicated for doing routing only. This is some NIC
- or pfSense in VM on Proxmox related problem. I need to install on bare metal for final test.
- www.xtrememailer.com
- www.ebesucher.com
- northerntraffic.net
- timecrazy.com
- domain definition math
- www.zigma.cash
- domain of rational function
- easyleadsandcash.com
Advertisement
Add Comment
Please, Sign In to add comment
