| | 1 | = Notes = |
| | 2 | This section covers discussions and some background work that went into this project. |
| | 3 | |
| | 4 | == Overview == |
| | 5 | The things covered here are: |
| | 6 | |
| | 7 | * DHCP relay agents |
| | 8 | * VLANS |
| | 9 | * Trunking |
| | 10 | |
| | 11 | |
| | 12 | == VLANs == |
| | 13 | VLANs are a way to split up broadcast domains at L2. They can be statically or dynamically set, with dynamic VLANs sort of working in a similar way to DHCP. |
| | 14 | |
| | 15 | == DHCP Relay agents == |
| | 16 | Relay agents are virtual layer 3 devices residing on a switch with VLANs. In this case, they allow DHCP broadcasts to be relayed across 2 VLANs on the same switch. This is not necessary for us because the DHCP server lives beyond the ASA, and the ASA not only acts as a router between the switch and the server, but also serves to manipulate the VLAN tags (masquerades as hosts sending out DHCP requests). |
| | 17 | |
| | 18 | == Trunking == |
| | 19 | Trunking is done by making a "backbone" for all the different VLANs on a local switch to converge to. Frames from different VLANs are identified bythe means of VLAN tags, a four-byte addition to the Ethernet frame identifying which VLAN it came from. The tagging is also known as 802.1q. |
| | 20 | |
| | 21 | == Native VLANs == |
| | 22 | Normally the 4 byte addition to the Ethernet frame would cause the tagged frame to be rejected on a VLAN, and regular frames would be rejected if found in the trunk due to the lack of a tag. This is unless the "regular" frame is from a '' native VLAN '' assigned to the trunk. '' More on Native VLANs once I get some research done. '' |
| | 23 | |
| | 24 | In our case this matters because DHCP coming from the trunk needs to assign IP addresses to both the hosts connected to the switch on different VLANs (VLAN 27) and to the switch itsself. To do this, The virtual interface to which the IP address is assigned needs to be on the trunked port(s). |
| | 25 | |
| | 26 | |
