Ping and general network weirdness

Phil Cooper sendphilmail at gmail.com
Thu Jun 30 00:19:18 GMT 2005


Here's the output, thanks for such a quick reply.


$ netstat -rn
Routing tables

Internet:
Destination        Gateway            Flags    Refs      Use  Netif  
Expire
default            192.168.0.1        UGS         0        0    rl0
127.0.0.1          127.0.0.1          UH          1       41    lo0
192.168.0          link#1             UC          0        0    rl0
192.168.0.1        00:0f:20:1e:e9:12  UHLW        1       25    rl0    
1084
192.168.0.4        00:11:24:87:67:e2  UHLW        0       93    rl0    
1081
192.168.0.224      127.0.0.1          UGHS        0        0    lo0

Internet6:
Destination                       Gateway                        
Flags      Netif Expire
::1                               ::1                            
UH          lo0
fe80::%rl0/64                     link#1                         
UC          rl0
fe80::240:95ff:fe60:925%rl0       00:40:95:60:09:25              
UHL         lo0
fe80::%lo0/64                     fe80::1%lo0                    
U           lo0
fe80::1%lo0                       link#3                         
UHL         lo0
ff01::/32                         ::1                            
U           lo0
ff02::%rl0/32                     link#1                         
UC          rl0
ff02::%lo0/32                     ::1                            
UC          lo0



...and...



$ ifconfig
rl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         options=8<VLAN_MTU>
         inet6 fe80::240:95ff:fe60:925%rl0 prefixlen 64 scopeid 0x1
         inet 192.168.0.224 netmask 0xffffff00 broadcast 192.168.0.255
         ether 00:40:95:60:09:25
         media: Ethernet autoselect (100baseTX <full-duplex>)
         status: active
plip0: flags=108810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
         inet 127.0.0.1 netmask 0xff000000
         inet6 ::1 prefixlen 128
         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3



Any ideas?

  - P



On 30 Jun 2005, at 01:14, Christopher Black wrote:

>> *snip*
>
> It's obviously resolving the IP to 192.168.0.116, it could be a  
> routing issue.  What is the output of 'netstat -rn' and ifconfig?






More information about the freebsd-questions mailing list