I have 20 physical stations w/ 5 network drops at each station. All are connected via cascading switches to a central switch. On the switch are: an ASUS RT-N66U (semi)intelligent router with the embedded DHCP server handing out addresses to PC's at each of the station drops for the single WAN port for connecting to the Internet.
Also attached to the central switch is a proprietary Application/Server running Windows(c) 7 that has an embedded DHCP/TFTP server that has a proprietary application that responds to PXE boot requests from PC's to load and run the application.
I need to attach a any PC to any drop at any of the stations and have SOMEthing differentiate whether the PC is booting PXE and route to the Application Server DHCP/TFTP server or, if the PC is trying to go to the Internet, route to the ASUS router. These are randomly connected PC's and there is no way to differentiate or make unique the PC attached except for the MAC addresses.
I understand that there may be custom ports of ASUSWRT firmware (DDWRT or MerlinWRT) that 'may' do this, but I'd like to do this using existing firmware and hardware. I can do nothing about the proprietary server system. They've locked the code and will only support a dedicated network. I have a basic knowledge of TCP/IP, UDP DHCP/TFTP and know that DHCP/TFTP use UDP ports 67 and 68...
I'm thinking that there must be a routing statement I might add in the ASUS router that says, " Ah! You're a PXE boot agent PC! You go to the App.s server port 67/68 pair DHCP server" Or, "You're a Firefox browser PC! You want to get to the Internet through the ASUS router DHCP server!"