OP
- Thread Starter
- #26
Dank U
While my posting was hard to follow while I struggled with this - and I applaud you for trying -
this was not the case.
If I disconnected from the university system, then booted up by USB or DVD iso,
the dhcp servers were on/in the unix or linux filesystems - and the server was getting IP addresses like 10.0.0.1 . . .
The university computer - even though ethernet cable was unplugged and I boot it (either FreeBSD or Fedora live versions with servers) then
with ethernet cable plugged directly into the laptop - was multicasting to a Laser Printer -
it was just configured to do that even after the live version OS boots -
so I guess it made little difference to it that the actual physical MAC address for the laptop is really (now known to be)
The fixes included getting the Intel UNDI, PXE-2.0 (build 082) starting up correctly on the laptop,
with also changing to unicast by the terminal command
SirDice said:
While my posting was hard to follow while I struggled with this - and I applaud you for trying -
this was not the case.
If I disconnected from the university system, then booted up by USB or DVD iso,
the dhcp servers were on/in the unix or linux filesystems - and the server was getting IP addresses like 10.0.0.1 . . .
SirDice said:
The university computer - even though ethernet cable was unplugged and I boot it (either FreeBSD or Fedora live versions with servers) then
with ethernet cable plugged directly into the laptop - was multicasting to a Laser Printer -
it was just configured to do that even after the live version OS boots -
so I guess it made little difference to it that the actual physical MAC address for the laptop is really (now known to be)
Code:
00:40:D0:xxxxxxThe fixes included getting the Intel UNDI, PXE-2.0 (build 082) starting up correctly on the laptop,
with also changing to unicast by the terminal command
Code:
# ip link set dev eth3 multicast off