Re: Understanding Local Networking - help please?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 09/15/2009 11:56 PM, Steve Searle wrote:
Around 10:34pm on Tuesday, September 15, 2009 (UK time), DB scrawled:

Does anyone have any suggestions how to proceed??
I'm no expert, but this might help move things on.

I assume each machine can ping the router, as their Internet connextions
work.  However, can each machine ping both other machines?

Steve

Hi Steve,

Thanks for the suggestion - I'd even forgotten that ping existed! I'll have to build me a Little Reminder Script "when this, then that"!!

Strangely, I don't seem to be able to ping the gateway... but after several false starts, I get the following when pinging the desktop from the laptop & the LT from itself:
[Dave@Fedora-Toshi ~]$ ping -R -a -c 5  192.168.0.160
PING 192.168.0.160 (192.168.0.160) 56(124) bytes of data.
64 bytes from 192.168.0.160: icmp_seq=1 ttl=64 time=0.337 ms
RR:     192.168.0.111
        192.168.0.160
        192.168.0.160
        192.168.0.111

64 bytes from 192.168.0.160: icmp_seq=2 ttl=64 time=0.322 ms    (same route)
64 bytes from 192.168.0.160: icmp_seq=3 ttl=64 time=0.317 ms    (same route)
64 bytes from 192.168.0.160: icmp_seq=4 ttl=64 time=0.330 ms    (same route)
64 bytes from 192.168.0.160: icmp_seq=5 ttl=64 time=0.334 ms    (same route)

--- 192.168.0.160 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.317/0.328/0.337/0.007 ms
[Dave@Fedora-Toshi ~]$ ping -R -a -c 5  192.168.0.111
PING 192.168.0.111 (192.168.0.111) 56(124) bytes of data.
64 bytes from 192.168.0.111: icmp_seq=1 ttl=64 time=0.162 ms
RR:     192.168.0.111
        192.168.0.111
        192.168.0.111
        192.168.0.111

64 bytes from 192.168.0.111: icmp_seq=2 ttl=64 time=0.132 ms    (same route)
64 bytes from 192.168.0.111: icmp_seq=3 ttl=64 time=0.108 ms    (same route)
64 bytes from 192.168.0.111: icmp_seq=4 ttl=64 time=0.133 ms    (same route)
64 bytes from 192.168.0.111: icmp_seq=5 ttl=64 time=0.122 ms    (same route)

--- 192.168.0.111 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4015ms
rtt min/avg/max/mdev = 0.108/0.131/0.162/0.020 ms

& Netstat gives the following:

[Dave@Fedora-Toshi ~]$ netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0
[Dave@Fedora-Toshi ~]$
[Dave@Fedora-Toshi ~]$ netstat -s
Ip:
    11703 total packets received
    0 forwarded
    0 incoming packets discarded
    11212 incoming packets delivered
    10408 requests sent out
Icmp:
    100 ICMP messages received
    20 input ICMP message failed.
    ICMP input histogram:
        destination unreachable: 2
        echo requests: 28
        echo replies: 60
    171 ICMP messages sent
    0 ICMP messages failed
    ICMP output histogram:
        destination unreachable: 9
        echo request: 144
        echo replies: 18
IcmpMsg:
        InType0: 60
        InType3: 2
        InType8: 28
        OutType0: 18
        OutType3: 9
        OutType8: 144
Tcp:
    546 active connections openings
    2 passive connection openings
    22 failed connection attempts
    7 connection resets received
    0 connections established
    9271 segments received
    8282 segments send out
    18 segments retransmited
    0 bad segments received.
    94 resets sent
Udp:
    1839 packets received
    2 packets to unknown port received.
    0 packet receive errors
    1935 packets sent
UdpLite:
TcpExt:
    52 TCP sockets finished time wait in fast timer
    422 delayed acks sent
    28 packets directly queued to recvmsg prequeue.
    11030 packets directly received from prequeue
    6212 packets header predicted
    9 packets header predicted and directly queued to user
    900 acknowledgments not containing data received
    489 predicted acknowledgments
    1 congestion windows recovered after partial ack
    0 TCP data loss events
    11 other TCP timeouts
    1 DSACKs received
    19 connections reset due to unexpected data
    4 connections reset due to early user close
    1 connections aborted due to timeout
IpExt:
    InMcastPkts: 146
    OutMcastPkts: 66
    InBcastPkts: 348
    OutBcastPkts: 34
    InOctets: 9439157
    OutOctets: 1123336
    InMcastOctets: 23470
    OutMcastOctets: 9545
    InBcastOctets: 55988
    OutBcastOctets: 3112
[Dave@Fedora-Toshi ~]$

I'm not much wiser.....

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora Magazine]     [Fedora News]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux