I considered sending DHCP responses to the server myself, but decided that injecting traffic would be too risky during flight... especially since I was flying back from a conference where one of the speakers had been talking about inadequate firewalling between IFE systems and aeronautical control systems.
How is this possible? Why do they even need to be on the same network?
Furthermore, the IFE might not need to talk to critical control systems, but they both might need to talk to some of the same other systems. Cabin lights seem like a likely candidate. Displays for the pilot, too. And maybe maintenance fault logs.
It can be a real hassle to have totally isolated systems on different networks. You can do it, but you need a Good Reason. The easy thing, from an engineering perspective, is to make it so everything can talk to everything.
On a flight from Sydney to Vancouver earlier this year, the in-flight entertainment system on my plane was broken. I spoke up: "Hi, I have a doctorate in computer science and I know a bit about these systems... want me to take a look?"
I was surprised when they agreed, brought me up to the front galley, and showed me their interface to the entertainment system (alas, the server itself was in the ceiling and not accessible). I ended up pulling out my laptop, borrowing a cat5 cable from one of the flight attendants (all of mine were in my checked suitcase) and running tcpdump on the plane's network. Alas, while that allowed me to diagnose the problem, I lacked the serial cable needed to connect to the server's console and wasn't able to fix it.