I've got kind of an interesting technical challenge.
I run a small network with unmanaged switches. In this environment there is some development going on that does ugly things to us, like for example, virtual PC's come up running DHCP and start handing out addresses and DNS server pointers that go no where...
So I've set up a 2611XM with two NICS and have physically segmented off the dev servers that are doing this.
The developers still want DHCP on the new subnet, which I can set up for them no problem, either on a Windows 2003 server on that segment or on the router itself. But I don't want to relay DHCP from the main subnet to the new 'devnet'.
With basically a default RIP2 setup and a couple of static routes I have the new network working fine and things like DNS and LDAP and other things Windows networking needs is all happy. The developers can browse the windows network and still get out to the internet...and there is no real need to get all strict with security on the router since it is on the inside of our firewall...
But before I setup DHCP on the new subnet, is there an easy way to ensure that DHCP traffic will not traverse the router from one physical segment to the other? (from one onboard NIC to another onboard NIC and vice versa)
Thanks in advance for any help or pointers to resources...
By default, router will not pass dhcp related traffic(for that matter any broadcast traffic), so you need not worry. But to ensure ,you can use 'no ip forward-protocol udp 67' which will block bootp/dhcp related UDP traffic from traversing.
I hope you have not enabled 'ip helper-address' on the router.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...