F5F Stay Refreshed Power Users Networks DHCP settings 66 and 67 available on ASUS router.

DHCP settings 66 and 67 available on ASUS router.

DHCP settings 66 and 67 available on ASUS router.

F
Fact
Junior Member
Find
1
08-19-2016, 12:32 AM
#1
You're looking to enable PXE boot on your ASUS GT-AC5300 router without relying on DHCP beyond the router itself. Focus on configuring DHCP options 66 and 67 in your router settings to support PXE boot. Let me know if you need further guidance!
Reply
Reply
F
Fact
08-19-2016, 12:32 AM #1

You're looking to enable PXE boot on your ASUS GT-AC5300 router without relying on DHCP beyond the router itself. Focus on configuring DHCP options 66 and 67 in your router settings to support PXE boot. Let me know if you need further guidance!

Reply
Reply
D
DoctorOmar
Member
Find
229
08-19-2016, 01:58 AM
#2
DHCP capabilities on consumer routers are generally restricted. When the manual doesn't address a solution, it's likely unsupported unless custom firmware is used.
Reply
Reply
D
DoctorOmar
08-19-2016, 01:58 AM #2

DHCP capabilities on consumer routers are generally restricted. When the manual doesn't address a solution, it's likely unsupported unless custom firmware is used.

Reply
Reply
L
LINK_GRIFF
Junior Member
Find
2
08-19-2016, 08:04 AM
#3
Thanks for your response. You've got the general idea right. I'm curious about the level of openness in the firmware for the GT-AC5300. I've worked with PuTTY for USB permissions, but that's the extent of my experience. Hopefully, someone with CLI expertise can help with firmware adjustments. Appreciate the support!
Reply
Reply
L
LINK_GRIFF
08-19-2016, 08:04 AM #3

Thanks for your response. You've got the general idea right. I'm curious about the level of openness in the firmware for the GT-AC5300. I've worked with PuTTY for USB permissions, but that's the extent of my experience. Hopefully, someone with CLI expertise can help with firmware adjustments. Appreciate the support!

Reply
Reply
G
GoldenEve
Member
Find
56
08-19-2016, 09:44 AM
#4
SSH connections from Asus routers are limited. I managed this with pihole. Below is my configuration layout. For arch9 and arch7, optional; if the booted server needs it, see the example. After saving, reload the service. If anyone finds a method to transfer these settings to dnsmasq on an Asus device, I’d value their input. (The server being booted is 192.168.1.6) pi@raspberrypi : /etc/dnsmasq.d $ cat 02-pihole-dhcp.conf ############################################################################### DHCP SERVER CONFIG FILE AUTOMATICALLY POPULATED BY PI-HOLE WEB INTERFACE. # Any modifications here will be lost upon change ############################################################################### dhcp-authoritative dhcp-range=192.168.1.15,192.168.1.253,24h dhcp-option=option:router,192.168.1.1 dhcp-leasefile=/etc/pihole/dhcp.leases #PXE dhcp-option=66,"192.168.1.6" dhcp-boot=ipxe.efi,,192.168.1.6 dhcp-match=set:efi-x86_64,option:client-arch,7 dhcp-match=set:efi-x86_64,option:client-arch,9 #quiet-dhcp domain=scuarmander.com local=/scuarmander.local/ pi@raspberrypi : /etc/dnsmasq.d $ sudo service pihole-FTL reload
Reply
Reply
G
GoldenEve
08-19-2016, 09:44 AM #4

SSH connections from Asus routers are limited. I managed this with pihole. Below is my configuration layout. For arch9 and arch7, optional; if the booted server needs it, see the example. After saving, reload the service. If anyone finds a method to transfer these settings to dnsmasq on an Asus device, I’d value their input. (The server being booted is 192.168.1.6) pi@raspberrypi : /etc/dnsmasq.d $ cat 02-pihole-dhcp.conf ############################################################################### DHCP SERVER CONFIG FILE AUTOMATICALLY POPULATED BY PI-HOLE WEB INTERFACE. # Any modifications here will be lost upon change ############################################################################### dhcp-authoritative dhcp-range=192.168.1.15,192.168.1.253,24h dhcp-option=option:router,192.168.1.1 dhcp-leasefile=/etc/pihole/dhcp.leases #PXE dhcp-option=66,"192.168.1.6" dhcp-boot=ipxe.efi,,192.168.1.6 dhcp-match=set:efi-x86_64,option:client-arch,7 dhcp-match=set:efi-x86_64,option:client-arch,9 #quiet-dhcp domain=scuarmander.com local=/scuarmander.local/ pi@raspberrypi : /etc/dnsmasq.d $ sudo service pihole-FTL reload

Reply
Reply
X
xX_pgmdu92_Xx
Member
Find
213
08-21-2016, 03:24 AM
#5
It varies based on your PXE setup. Some systems manage it locally, while others use TFTP and broadcast domains. Since you have a PXE server with DHCP capabilities, it makes sense to consider using DHCP directly there instead.
Reply
Reply
X
xX_pgmdu92_Xx
08-21-2016, 03:24 AM #5

It varies based on your PXE setup. Some systems manage it locally, while others use TFTP and broadcast domains. Since you have a PXE server with DHCP capabilities, it makes sense to consider using DHCP directly there instead.

Reply
Reply