Comcast Business class service has some quirks when using the Cisco branded business gateway. Essentially, the prefix delegation will not work without very specific configuration options on the client. In order to run your own network border (i.e. not using their device as the first hop router for your LAN(s)), the following is required. In addition, with static IP addresses also comes with a static IPv6 prefix delegation. For Ubiquity EdgeOS (or a derivative like a Unifi USG) the following needs to be set (eth2 is the port facing the comcast router)

Comcast Business class service has some quirks when using the Cisco branded business gateway. Essentially, the prefix delegation will not work without very specific configuration options on the client. In order to run your own network border (i.e. not using their device as the first hop router for your LAN(s)), the following is required. In addition, with static IP addresses also comes with a static IPv6 prefix delegation. For Ubiquity EdgeOS (or a derivative like a Unifi USG) the following needs to be set (eth2 is the port facing the comcast router)

Add a simple set of VLANs to a CCR or other non-CRS RouterBoard. /interface vlan add interface=sfpplus1 name=sfpplus1.4 vlan-id=4 comment="VLAN ID 4" add interface=sfpplus1 name=sfpplus1.5 vlan-id=5 comment="VLAN ID 5" add interface=sfpplus1 name=sfpplus1.6 vlan-id=6 comment="VLAN ID 6" add interface=sfpplus1 name=sfpplus1.7 vlan-id=7 comment="VLAN ID 7" add interface=sfpplus1 name=sfpplus1.8 vlan-id=8 comment="VLAN ID 8" add interface=sfpplus1 name=sfpplus1.9 vlan-id=9 comment="VLAN ID 9" Add IP addressing to each VLAN /ipv6 address add address=2001:db8:c33e:f0::1/64 advertise=no add address=2001:db8:c:f4::1/64 advertise=yes interface=sfpplus1.

Add a simple set of VLANs to a CCR or other non-CRS RouterBoard. /interface vlan add interface=sfpplus1 name=sfpplus1.4 vlan-id=4 comment="VLAN ID 4" add interface=sfpplus1 name=sfpplus1.5 vlan-id=5 comment="VLAN ID 5" add interface=sfpplus1 name=sfpplus1.6 vlan-id=6 comment="VLAN ID 6" add interface=sfpplus1 name=sfpplus1.7 vlan-id=7 comment="VLAN ID 7" add interface=sfpplus1 name=sfpplus1.8 vlan-id=8 comment="VLAN ID 8" add interface=sfpplus1 name=sfpplus1.9 vlan-id=9 comment="VLAN ID 9" Add IP addressing to each VLAN /ipv6 address add address=2001:db8:c33e:f0::1/64 advertise=no add address=2001:db8:c:f4::1/64 advertise=yes interface=sfpplus1.

set load-balance group LoadBalance_WAN interface route-test initial-delay 15 set load-balance group LoadBalance_WAN interface route-test interval 5 set load-balance group LoadBalance_WAN interface route-test type ping target set load-balance group LoadBalance_WAN interface weight 95 # weight based on more bandwidth set load-balance group LoadBalance_WAN interface route-test initial-delay 15 set load-balance group LoadBalance_WAN interface route-test interval 5 set load-balance group LoadBalance_WAN interface route-test type ping target set load-balance group LoadBalance_WAN interface weight 5 # weight based on less bandwidth Share this: Twitter Email Print LinkedIn Facebook Reddit Tumblr Pinterest Pocket

set load-balance group LoadBalance\_WAN interface route-test initial-delay 15 set load-balance group LoadBalance\_WAN interface route-test interval 5 set load-balance group LoadBalance\_WAN interface route-test type ping target set load-balance group LoadBalance\_WAN interface weight 95 # weight based on more bandwidth set load-balance group LoadBalance\_WAN interface route-test initial-delay 15 set load-balance group LoadBalance\_WAN interface route-test interval 5 set load-balance group LoadBalance\_WAN interface route-test type ping target set load-balance group LoadBalance\_WAN interface weight 5 # weight based on less bandwidth

This section contains various configuration examples that I have built or found otherwise useful. [child_pages]

CPU type “host” for proper nested virtualization https://pve.proxmox.com/wiki/Nested_Virtualization Converting images qemu-img convert -f vmdk -O qcow2 vmx-nested-18.2R1.9-4.vmdk vmx-18.2R1.9-4/hda.qcow2

OpenFlow statistics from my home installation powered by a 48 port, PoE Allied Telesis x930 and a minimal linux container running Faucet. This installation runs my home, my home office, and my rack of lab gear.

As a follow on to my post on why small to medium ISPs should deploy IPv6 and the associated APNIC blog post, I have begun to compile a list of commonly asked questions IPv6 and their answers in relation to how a small to medium sized ISP can (and should) deploy IPv6. Expect this list to change and grow over time. -—– Q: Is there DHCP in IPv6?  -—–