February 2008: These tests are all badly in need of update.
Some
questions are incorrect because of changing technology and others
just make no sense in today's IT world.
I do intend to update these,
but it's a big project..
Copyright 2002,2003 A.P. Lawrence
Next
Previous
Return to Start Page
Get Complete 305 Question
Set
bash-2.05a$ ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
inet 127.0.0.1 netmask 0xff000000
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::203:93ff:fed8:db98%en0 prefixlen 64 scopeid 0x4
inet 10.1.36.20 netmask 0xffffff00 broadcast 10.1.36.255
ether 00:03:93:d8:db:98
media: autoselect (100baseTX <full-duplex>) status: active
supported media: none autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <half-duplex,hw-loopback> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 100baseTX <half-duplex> 100baseTX <half-duplex,hw-loopback> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback>
bash-2.05a$ sudo arp -s 192.168.1.1 fe:ff:ff:ff:ff:ff
cannot intuit interface index and type for 192.168.1.1
Why does this error happen?