[GitHub] [cloudstack] kioie commented on issue #3499: Physical networking with pfsense

[GitBox <gi...@apache.org>]

kioie commented on issue #3499: Physical networking with pfsense
URL: https://github.com/apache/cloudstack/issues/3499#issuecomment-512152134
 
 
   Hey @imacks 
   
   For starters, I'm assuming this is not a prod environment, possibly test/dev in which case please note this as mentioned in the documentation
   
   > A /24 network with the gateway being at xxx.xxx.xxx.1, no DHCP should be on this network and none of the computers running CloudStack will have a dynamic address. Again this is done for the sake of simplicity.
   
   So you might want to give a static IP to all machines and possibly disable DHCP. You will also realize, that Advanced networking may not work with a single subnet, you will need additional subnets/vlans to isolate traffic
   
   **Guest cidr** - the default `10.1.1.0/24` should work fine
   
   **Internal DNS 1 and Internal DNS 2**- These are DNS servers for use by system VMs in the zone(these are VMs used by CloudStack itself, such as virtual routers, console proxies,and Secondary Storage VMs.) These DNS servers will be accessed via the management traffic network interface of the System VMs. If unsure about what to use here, you can use `8.8.8.8` and `8.8.4.4`, as long as management traffic has access to the internet.
   
   **physical network page setup** - 
   
   > The traffic types are management, public, guest, and storage traffic. For more information about the types, roll over the icons to display their tool tips, or see “Advanced Zone Network Traffic Types”. This screenstarts out with one network already configured. If you have multiple physical networks, you need to add more. Drag and drop traffic types onto a greyed-out network and it will become active. You can move the traffic icons from one network to another; for example, if the default traffic types shown for Network 1 do not match your actual setup, you can move them down. You can also change the network names if desired.
   > 
   > (Introduced in version 3.0.1) Assign a network traffic label to each traffic type on each physical network. These labels must match the labels you have already defined on the hypervisor host. To assign each label, click the Edit button under the traffic type icon within each physical network. A popup dialog appears where you can type the label, then click OK.
   > 
   > These traffic labels will be defined only for the hypervisor selected for the first cluster. For all other hypervisors, the labels can be configured after the zone is created.
   
   In your case, you may need additional bridges if you are setting up an advanced network. See **[here](https://www.shapeblue.com/networking-kvm-for-cloudstack-2018-revisit-for-centos7-and-ubuntu-18-04/)** for a detailed account on what bridges you might require.
   
   **Pod Configuration/guest vlan range/public traffic ips** - Alot of this will depend on how you setup your bridges
   
   Also, considering this is not a dev issue, you might want to close this and move this conversation to the mailing list where you might get better support.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services