Code:
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x10003 ...xx xx xx xx xx xx ...... VIA Rhine II Fast Ethernet Adapter
0x10004 ...xx xx xx xx xx xx ...... Realtek RTL8187 Wireless 802.11b/g 54Mbps US
B 2.0 Network Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.2.5 192.168.2.1 25
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.1 192.168.0.1 20
192.168.0.1 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.0.255 255.255.255.255 192.168.0.1 192.168.0.1 20
192.168.2.0 255.255.255.0 192.168.2.1 192.168.2.1 25
192.168.2.1 255.255.255.255 127.0.0.1 127.0.0.1 25
192.168.2.255 255.255.255.255 192.168.2.1 192.168.2.1 25
224.0.0.0 240.0.0.0 192.168.0.1 192.168.0.1 20
224.0.0.0 240.0.0.0 192.168.2.1 192.168.2.1 25
255.255.255.255 255.255.255.255 192.168.0.1 192.168.0.1 1
255.255.255.255 255.255.255.255 192.168.2.1 192.168.2.1 1
Default Gateway: 192.168.2.5
===========================================================================
Persistent Routes:
None
Why would changing the Xbox's subnet make a difference to whether I can ping the FreeBSD server from the XP box? The Xbox can be turned off for all I care, it makes no difference.
Shish: I'm not familiar with scope or why the FreeBSD server needs to know about the Xbox if the XP box is handling the packet routing when it gets that far. The FreeBSD box isn't routing packets straight to the Xbox because they need to go through the XP box first. Or am I missing something?
Hopefully you can interpret something useful from the output above.