-
Notifications
You must be signed in to change notification settings - Fork 0
DHCP broken between B32 and B53 #101
Copy link
Copy link
Open
Labels
ip networkingInvestigation or changes to IP networking (e.g. firewalling, routing, VPN, etc.) on the SOWN networkInvestigation or changes to IP networking (e.g. firewalling, routing, VPN, etc.) on the SOWN networksystems administrationAdministation of servers and the systems running on themAdministation of servers and the systems running on them
Metadata
Metadata
Assignees
Labels
ip networkingInvestigation or changes to IP networking (e.g. firewalling, routing, VPN, etc.) on the SOWN networkInvestigation or changes to IP networking (e.g. firewalling, routing, VPN, etc.) on the SOWN networksystems administrationAdministation of servers and the systems running on themAdministation of servers and the systems running on them
If a host DHCPs in B32, we don't see that DHCP discover in B53. This means if we want to PXE boot one of our GW servers (which host the DHCP server), it can't PXE boot off the DHCP server in the other building.
To test this, try PXE booting a VM with:
And check on the GW servers with:
I think this is likely isolutions filtering DHCP on our VLAN between buildings?