Posted 16 February 2010 - 09:08 PM
To find the interface referred to by the "link#5" do a netstat -i on the command line. You should see the port name in the left column and the link number in the third. It ought to be (better be) en1 on your system.
I don't see any obvious issues with the table.
The first line defines your default gateway and default route:
default 192.168.1.254 UGSc 125 0 en1
192.168.1.254 is both the gateway and default route, it is Up (U), a Gateway (G), is Statically defined (S), and has the protocol cloning © flag set, which is normal for this route.
The next line maps the entire 127.x.x.x network to 127.0.0.1 and ties it to your loopback port (lo0)
The next line loops 127.0.0.1 back to itself just so nothing can get away
The next line sets up 169.254.x.x so you can talk to self-assigned IP's on your local subnet
The next line sets up 192.168.1.x as your locally attached subnet
The © indicator shows these two as directly connected via en1
The next two define individual host machines at 192.168.1.69 & 192.168.1.70, with their associated MAC addresses.
The next, 192.168.1.72, should be your own IP address on the 192.168.1.x subnet, and maps it to the loopback port
Next we have the host entry for your router, 192.168.1.254, with it's MAC
Finally we have the broadcast address definition.
The flag definitions are:
1 RTF_PROTO1 Protocol specific routing flag #1
2 RTF_PROTO2 Protocol specific routing flag #2
3 RTF_PROTO3 Protocol specific routing flag #3
B RTF_BLACKHOLE Just discard packets (during updates)
b RTF_BROADCAST The route represents a broadcast address
C RTF_CLONING Generate new routes on use
c RTF_PRCLONING Protocol-specified generate new routes on use
D RTF_DYNAMIC Created dynamically (by redirect)
G RTF_GATEWAY Destination requires forwarding by intermediary
H RTF_HOST Host entry (net otherwise)
L RTF_LLINFO Valid protocol to link address translation
M RTF_MODIFIED Modified dynamically (by redirect)
R RTF_REJECT Host or net unreachable
S RTF_STATIC Manually added
U RTF_UP Route usable
W RTF_WASCLONED Route was generated as a result of cloning
X RTF_XRESOLVE External daemon translates proto to link address
Based on what I see, it looks like your routes are fine. Your gateway is probably the next suspect.
Any more info on what is not working right ?