-
Tomek Mrugalski authored
- default value is no longer 0.0.0.0, so global value is no longer overwritten with subnet-specific values - added 2 new unit-tests to check if the value is really set in server responses - guide updated to explain that - fix in Dhcp4ParserTest.nextServerNegative
d8d20c97