This. is. just. beautiful.
Pintando una Canción (translated: “Drawing a Song”) is a mind blowing, gracious, fluid en well-executed semi-interactive Flash animation. Just amazing. Wow.
This. is. just. beautiful.
Pintando una Canción (translated: “Drawing a Song”) is a mind blowing, gracious, fluid en well-executed semi-interactive Flash animation. Just amazing. Wow.
Suppose you have a network with multiple VLANs, each with its own subnet, and you want your DHCP server(s) to serve addresses and configuration to all subnets (or at least more than one of them). The problem normally is that broadcast traffic (such as DHCP requests from clients) cannot traverse broadcast domains, which is exactly what VLAN separation does: limit broadcast domains.
There’s basically three solutions: the first is to provide a single DHCP server with a network interface in each VLAN. This will work fine for a very limited number of VLANs, but is not very effective for larger numbers of VLANs and it’s also not very flexible. Every new VLAN requires an extra NIC, cabling, etc.
The second solution is to provide each VLAN with its own DHCP server. This is not very flexible either and eats lots of resources per VLAN and adds a lot of management complexity.
The third solution adds flexibility, ease of management and does not require a major investment in separate servers. What you do need however is a Layer3 switch in stead of a Layer2 model. The reason for this is that the switch has to be capable to route, or more accurately: re-route IP packets.
To enable a single DHCP server to serve multiple subnets, one per VLAN, you can configure your switch (both Cisco and HP Layer3 switches can do this, and probably most other brands as well) with an ‘IP helper’. An IP helper address tells the switch to forward certain types of broadcasts (like DHCP requests, TFTP requests and DNS requests) via unicast to the IP address(es) configured. An example:

Here the DHCP server is using address 10.0.1.5 in VLAN 1, on subnet 10.0.1.0 /24. The two clients are on separate VLANs 2 and 3 with subnets 10.0.2.0 /24 and 10.0.3.0 /24 respectively. In this case, we need the switch that receives the DHCP requests broadcast from the clients to forward the requests to the DHCP server. To do this, we add the IP address of the server to the different VLAN interfaces as the IP helper:
interface vlan 1 ip address 10.0.1.1 255.255.255.0 interface vlan 2 ip address 10.0.2.1 255.255.255.0 ip helper-address 10.0.1.5 interface vlan 3 ip address 10.0.3.1 255.255.255.0 ip helper-address 10.0.1.5
The switch will now forward the request broadcasts to the DHCP server. If the DHCP server has been configured with separate ranges for each subnet, the right answer will be sent back by it to the switch and then forwarded to the client.
I went to hear Carlos Solari speak here in The Netherlands last week, and his message makes a lot of sense: to create truly secure infrastructures, devices and services, all components must be built using the ‘SBD’ or Security By Design principles.
Solari and his team put forth the view that to create a fully secure chain of trust (because trust is as important as security, if not more) the IT industry needs a verifiable, certifiable standard method of testing the eight factors they propose to enable manufacturers and developers to create truly secure products.
Aside from the solid message, Solari is a great speaker with an impressive career: the armed forces, then the FBI, followed by a couple of years as CIO for the Executive Office of the President at the White House. Now with Alcatel-Lucent’s Bell Labs as VP of security solutions, Carlos Solari is spreading the word on security, trust and reliability as inherent parts of any solution.
The book is “Security in a Web 2.0+ World: A Standards-Based Approach” and I recommend it. Amazon link here.
I took the ‘new’ Safari 4 out for a test spin today, and although I have absolutely no factual test data the page rendering was indeed as fast as promised. All in all Safari is a very clean and sleek browser and does handle all I can throw at it with ease (like big Flash content, old and new Java apps and even some huge Javascript stuff).
Having moved from IE to Mozilla some time ago I’m actually contemplating using Safari for my day-to-day browsing now. Me like.
This made me giggle all day:
Thanks to Geekologie.