Wireless can't ping wireless

[Jim Lewis]

 I just realized that my wireless computers can't ping each other.
Wireless to wired and vice versa is just fine. The IP addresses (DHCP)
are all on the same subnet. If I switch to wired the computer can then
ping a wired or wireless. The computers can all access the Internet at
any time (either wired or wireless). I did some research and have
determined the problem might be my router.

  I use a LinkSys E3000 which I have had for a very long time. I checked
their site and looked at the Release Notes for firmware upgrades. No
mention of this issue and so I am hesitant to perform it (I did however
download the latest file). I got into their Live Chat and the guy said
since the unit is no longer in warranty I would have to pay to get
assistance. I thought about doing this, but he could not guarantee
success and the payment is not refundable. I thought that sucked and
told him so.

 So, does anyone have any ideas about how I might solve this? I am going
to be rather surprised if the problem is not the router. If it matters
here is my hardware:

Fedora 14 - wired desktop
Fedora 20 - wireless laptop
Fedora 21 - wireless laptop (or wired)
Fedora 21 - wireless laptop (or wired)
Ubuntu 12.04.2 LTS - wireless (practically unusable because of Gnome 3)


Jim Lewis

Wireless can't ping wireless (even more info)

[Jim Lewis]

>  On 01/25/15 11:39, Jim Lewis wrote:
> >> On 01/25/15 11:16, Jim Lewis wrote:
> >>>   Okay, I was able to recreate the other problem after rebooting
> >>> laptop1
> >>> (Fedora 21 Mate-Compbiz Spin). I could not ping it from either wired
> >>> box. However, I tried pinging from the router and that worked fine (so
> >>> did traceroute). Speaking of traceroute, this from wired box big4:
> >>>
> >>>
> >>> big4 / # traceroute 192.168.1.111
> >>> traceroute to 192.168.1.111 (192.168.1.111), 30 hops max, 60 byte
> >>> packets
> >>>  1  192.168.1.109 (192.168.1.109)  3006.581 ms !H  3006.573 ms !H
> >>> 3006.563 ms !H
> >>>
> >>>   The !H is of course host unreachable.
> >> What has IP 192.168.1.109?
> >>
> >    My wired box, big4, is 192.168.1.109. All the machines can ping it
> > without issues.
>
>  Sorry if this has already been asked/answered.....
>
>  192.168.1.111 is what?  I'm guessing a wireless system?
>
>  And the IP address of your LinkSys is?
>  
Hi Ed,

   Ask anything you want, I enjoy the help:

   laptop1 is 192.168.1.111  (when wireless)

   LinkSys is 192.168.1.1

   big4 is 192.168.1.109       (desktop machine, always wired)


Jim Lewis

Wireless can't ping wireless (even more info)

[Jim Lewis]

>  On 01/25/15 11:16, Jim Lewis wrote:
> >
> >   Okay, I was able to recreate the other problem after rebooting laptop1
> > (Fedora 21 Mate-Compbiz Spin). I could not ping it from either wired
> > box. However, I tried pinging from the router and that worked fine (so
> > did traceroute). Speaking of traceroute, this from wired box big4:
> >
> >
> > big4 / # traceroute 192.168.1.111
> > traceroute to 192.168.1.111 (192.168.1.111), 30 hops max, 60 byte
> > packets
> >  1  192.168.1.109 (192.168.1.109)  3006.581 ms !H  3006.573 ms !H
> > 3006.563 ms !H
> >
> >   The !H is of course host unreachable.
>
>  What has IP 192.168.1.109?
>  
   My wired box, big4, is 192.168.1.109. All the machines can ping it
without issues.


Jim Lewis

Wireless can't ping wireless (even more info)

[Ed Greshko]

On 01/25/15 12:46, Ed Greshko wrote:
>  When in this condition, what is the output of "arp" on
> big4? 
I meant "arp -n"

-- 
If you can't laugh at yourself, others will gladly oblige.

Wireless can't ping wireless (even more info)

[Ed Greshko]

On 01/25/15 12:16, Jim Lewis wrote:
>  Hi Ed,
>
>     Ask anything you want, I enjoy the help:
>
>     laptop1 is 192.168.1.111  (when wireless)
>
>     LinkSys is 192.168.1.1
>
>     big4 is 192.168.1.109       (desktop machine, always wired) 
OK....  What I saw in a previous message seemed odd to me....

I saw

big4 / # traceroute 192.168.1.111 traceroute to 192.168.1.111 (192.168.1.111), 30 hops
max, 60 byte packets 1 192.168.1.109 (192.168.1.109) 3006.581 ms !H 3006.573 ms !H
3006.563 ms !H

When in this condition, what is the output of "arp" on big4?

-- 
If you can't laugh at yourself, others will gladly oblige.

Wireless can't ping wireless (more info)

[Fred Smith]

On Thu, Jan 22, 2015 at 06:58:07PM -1000, Jim Lewis wrote:
>  
>  >
>  >  I just realized that my wireless computers can't ping each other.
>  > Wireless to wired and vice versa is just fine. The IP addresses (DHCP)
>  > are all on the same subnet. If I switch to wired the computer can then
>  > ping a wired or wireless. The computers can all access the Internet at
>  > any time (either wired or wireless). I did some research and have
>  > determined the problem might be my router.
>  >
>  >   I use a LinkSys E3000 which I have had for a very long time. I checked
>  > their site and looked at the Release Notes for firmware upgrades. No
>  > mention of this issue and so I am hesitant to perform it (I did however
>  > download the latest file). I got into their Live Chat and the guy said
>  > since the unit is no longer in warranty I would have to pay to get
>  > assistance. I thought about doing this, but he could not guarantee
>  > success and the payment is not refundable. I thought that sucked and
>  > told him so.
>  >
>  >  So, does anyone have any ideas about how I might solve this? I am going
>  > to be rather surprised if the problem is not the router. If it matters
>  > here is my hardware:
>  >
>  > Fedora 14 - wired desktop
>  > Fedora 20 - wireless laptop
>  > Fedora 21 - wireless laptop (or wired)
>  > Fedora 21 - wireless laptop (or wired)
>  > Ubuntu 12.04.2 LTS - wireless (practically unusable because of Gnome 3)
>  >
>  
>    I just discovered something new: If I boot up one of my Fedora 21
>  laptops and try to ping it from any computer (wired or wireless), it
>  will fail with the same "Destination Host Unreachable" message. Note
>  that I am using the correct IP as shown by ifconfig. This laptop can
>  access the Internet just fine. Now here comes the good part: If I ping
>  my wired computer from this laptop it succeeds, and if I now try to ping
>  this laptop from the wired machine that now succeeds as well!  I have
>  tried this a bunch of times with the same result. Note that a wired 
Makes me think (a wild guess, more likely) of an ARP problem. though
I couldn't point at anything in particular.

Might be helpful to break out wireshark and look at the low-level
traffic.

>  connection does not behave this way, I can ping it immediately. Also,
> I
>  just tried this with my Fedora 20 system (wireless) and it does NOT
>  fail, I can ping it immediately. So, assuming I haven't made some
>  brilliant error (I only make really stupid ones) there is something not
>  quite right in my Fedora 21 setups (yes, this is happening on both of
>  them).
>  
>   I am using the Mate Compiz spin. Once the connection is made and can ping
>  both ways it seems to stay that way without any further issues.
>  
>   I believe this also explains why wireless to wireless doesn't work. Since
>  it can't ping in either direction I can't "jog" it into working.
>  
>   One more data point: This also occurs if I disable the interface and
>  start it back up again. A reboot is not required to show the problem.
>  
>  
>  
>  Jim Lewis
>  
>  
>  
>  
>  -- 
>  users mailing list
>  users(a)lists.fedoraproject.org
>  To unsubscribe or change subscription options:
>  https://admin.fedoraproject.org/mailman/listinfo/users
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>  Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>  Have a question? Ask away: http://ask.fedoraproject.org 
-- 
-------------------------------------------------------------------------------
 .----    Fred Smith   /              
( /__  ,__.   __   __ /  __   : /     
 /    /  /   /__) /  /  /__) .+'           Home: fredex(a)fcshome.stoneham.ma.us 
/    /  (__ (___ (__(_ (___ / :__                                 781-438-5471 
-------------------------------- Jude 1:24,25 ---------------------------------

[Andy Paterson]

Sounds to me like broadcasts aren't being forwarded by the router to the wireless
network - check router settings ?

Sent from my iPhone

>  On 23 Jan 2015, at 02:14, Rick Stevens <ricks(a)alldigital.com&gt;
> wrote:
>  
> > On 01/22/2015 05:30 PM, Jim Lewis wrote:
> > 
> >  I just realized that my wireless computers can't ping each other.
> > Wireless to wired and vice versa is just fine. The IP addresses (DHCP)
> > are all on the same subnet. If I switch to wired the computer can then
> > ping a wired or wireless. The computers can all access the Internet at
> > any time (either wired or wireless). I did some research and have
> > determined the problem might be my router.
> > 
> >   I use a LinkSys E3000 which I have had for a very long time. I checked
> > their site and looked at the Release Notes for firmware upgrades. No
> > mention of this issue and so I am hesitant to perform it (I did however
> > download the latest file). I got into their Live Chat and the guy said
> > since the unit is no longer in warranty I would have to pay to get
> > assistance. I thought about doing this, but he could not guarantee
> > success and the payment is not refundable. I thought that sucked and
> > told him so.
> > 
> >  So, does anyone have any ideas about how I might solve this? I am going
> > to be rather surprised if the problem is not the router. If it matters
> > here is my hardware:
> > 
> > Fedora 14 - wired desktop
> > Fedora 20 - wireless laptop
> > Fedora 21 - wireless laptop (or wired)
> > Fedora 21 - wireless laptop (or wired)
> > Ubuntu 12.04.2 LTS - wireless (practically unusable because of Gnome 3)
>  
>  Are the wired and wireless connections on the same subnet? If so, you
>  may be having with the routing of packets. Simply yanking out a cable
>  doesn't guarantee that the default route gets changed (unless you're
>  using NetworkManager).
>  
>  Consider: "A" has 192.168.1.10/24 on the wired NIC and 192.168.1.100/24
>  on the wireless (both NICs on the same subnet). "B" has 192.168.1.11/24
>  and 192.168.1.101/24 respectively. Now, "A" sends out a ping to "B".
>  Which NIC does it use? It will use the default route. Odds are that's
>  the wired NIC. Now, if you pull "A"s cable out, the default route is
>  still over the wire (unless NetworkManager or you manually change it).
>  Hence the outgoing ping never gets sent.
>  
>  So, check the routes. On "A" with the wired cable hooked up, do a
>  
>     netstat -rn
>  
>  as root and look for the line with the "UG" in it. The value under
>  "Iface" is which NIC is the default one. Now pull one of cables and
>  repeat the netstat command. See if the route changes to the other NIC.
>  If it does, you should be able to ping the other nodes. If it doesn't,
>  you'll need to drop the wireless connection and restart it (or change
>  the route manually to the other NIC) and try the ping again.
>  
>  It's always dangerous to have two different physical NICs on the same
>  subnet because this sort of routing issue can occur. One way around it
>  is to use the two NICs in a mode 1 (failover) bonded pair. "bond0"
>  gets the IP and the network system will automatically fail over to the
>  other NIC if the primary goes down.
>  ----------------------------------------------------------------------
>  - Rick Stevens, Systems Engineer, AllDigital    ricks(a)alldigital.com -
>  - AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
>  -                                                                    -
>  -       "As for me, I aspire to be the Walmart Greeter in Hell."     -
>  ----------------------------------------------------------------------
>  -- 
>  users mailing list
>  users(a)lists.fedoraproject.org
>  To unsubscribe or change subscription options:
>  https://admin.fedoraproject.org/mailman/listinfo/users
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>  Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>  Have a question? Ask away: http://ask.fedoraproject.org

[Jens Neu]

On 01/23/2015 02:30 AM, Jim Lewis wrote:
>    I just realized that my wireless computers can't ping each
> other. 
I would assume the ordinary first, your AP is in "isolate" mode.
Lots of 
routers do this on default, in OpenWRT or similar you can usually 
configure this. However, not all AP hardware does support it.

See http://wiki.openwrt.org/doc/uci/wireless and look for "isolate".

regards
Jens

Wireless can't ping wireless (more info)

[Jim Lewis]

>   I just realized that my wireless computers can't ping each other.
>  Wireless to wired and vice versa is just fine. The IP addresses (DHCP)
>  are all on the same subnet. If I switch to wired the computer can then
>  ping a wired or wireless. The computers can all access the Internet at
>  any time (either wired or wireless). I did some research and have
>  determined the problem might be my router.
>
>    I use a LinkSys E3000 which I have had for a very long time. I checked
>  their site and looked at the Release Notes for firmware upgrades. No
>  mention of this issue and so I am hesitant to perform it (I did however
>  download the latest file). I got into their Live Chat and the guy said
>  since the unit is no longer in warranty I would have to pay to get
>  assistance. I thought about doing this, but he could not guarantee
>  success and the payment is not refundable. I thought that sucked and
>  told him so.
>
>   So, does anyone have any ideas about how I might solve this? I am going
>  to be rather surprised if the problem is not the router. If it matters
>  here is my hardware:
>
>  Fedora 14 - wired desktop
>  Fedora 20 - wireless laptop
>  Fedora 21 - wireless laptop (or wired)
>  Fedora 21 - wireless laptop (or wired)
>  Ubuntu 12.04.2 LTS - wireless (practically unusable because of Gnome 3)
>  
  I just discovered something new: If I boot up one of my Fedora 21
laptops and try to ping it from any computer (wired or wireless), it
will fail with the same "Destination Host Unreachable" message. Note
that I am using the correct IP as shown by ifconfig. This laptop can
access the Internet just fine. Now here comes the good part: If I ping
my wired computer from this laptop it succeeds, and if I now try to ping
this laptop from the wired machine that now succeeds as well!  I have
tried this a bunch of times with the same result. Note that a wired
connection does not behave this way, I can ping it immediately. Also, I
just tried this with my Fedora 20 system (wireless) and it does NOT
fail, I can ping it immediately. So, assuming I haven't made some
brilliant error (I only make really stupid ones) there is something not
quite right in my Fedora 21 setups (yes, this is happening on both of
them).

 I am using the Mate Compiz spin. Once the connection is made and can ping
both ways it seems to stay that way without any further issues.

 I believe this also explains why wireless to wireless doesn't work. Since
it can't ping in either direction I can't "jog" it into working.

 One more data point: This also occurs if I disable the interface and
start it back up again. A reboot is not required to show the problem.



Jim Lewis

[Rick Stevens]

On 01/22/2015 05:30 PM, Jim Lewis wrote:
>    I just realized that my wireless computers can't ping each other.
>  Wireless to wired and vice versa is just fine. The IP addresses (DHCP)
>  are all on the same subnet. If I switch to wired the computer can then
>  ping a wired or wireless. The computers can all access the Internet at
>  any time (either wired or wireless). I did some research and have
>  determined the problem might be my router.
>
>     I use a LinkSys E3000 which I have had for a very long time. I checked
>  their site and looked at the Release Notes for firmware upgrades. No
>  mention of this issue and so I am hesitant to perform it (I did however
>  download the latest file). I got into their Live Chat and the guy said
>  since the unit is no longer in warranty I would have to pay to get
>  assistance. I thought about doing this, but he could not guarantee
>  success and the payment is not refundable. I thought that sucked and
>  told him so.
>
>    So, does anyone have any ideas about how I might solve this? I am going
>  to be rather surprised if the problem is not the router. If it matters
>  here is my hardware:
>
>  Fedora 14 - wired desktop
>  Fedora 20 - wireless laptop
>  Fedora 21 - wireless laptop (or wired)
>  Fedora 21 - wireless laptop (or wired)
>  Ubuntu 12.04.2 LTS - wireless (practically unusable because of Gnome 3) 
Are the wired and wireless connections on the same subnet? If so, you
may be having with the routing of packets. Simply yanking out a cable
doesn't guarantee that the default route gets changed (unless you're
using NetworkManager).

Consider: "A" has 192.168.1.10/24 on the wired NIC and 192.168.1.100/24
on the wireless (both NICs on the same subnet). "B" has 192.168.1.11/24
and 192.168.1.101/24 respectively. Now, "A" sends out a ping to "B".
Which NIC does it use? It will use the default route. Odds are that's
the wired NIC. Now, if you pull "A"s cable out, the default route is
still over the wire (unless NetworkManager or you manually change it).
Hence the outgoing ping never gets sent.

So, check the routes. On "A" with the wired cable hooked up, do a

	netstat -rn

as root and look for the line with the "UG" in it. The value under
"Iface" is which NIC is the default one. Now pull one of cables and
repeat the netstat command. See if the route changes to the other NIC.
If it does, you should be able to ping the other nodes. If it doesn't,
you'll need to drop the wireless connection and restart it (or change
the route manually to the other NIC) and try the ping again.

It's always dangerous to have two different physical NICs on the same
subnet because this sort of routing issue can occur. One way around it
is to use the two NICs in a mode 1 (failover) bonded pair. "bond0"
gets the IP and the network system will automatically fail over to the
other NIC if the primary goes down.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    ricks(a)alldigital.com -
- AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
-                                                                    -
-       "As for me, I aspire to be the Walmart Greeter in Hell."     -
----------------------------------------------------------------------

Wireless can't ping wireless (SOLVED)

[poma]

On 29.01.2015 22:15, Jim Lewis wrote:
>  
> > On 29.01.2015 06:07, Jim Lewis wrote:
> >>
> >>   For those following this thread I solved the problem by getting a new
> >> router. Here's a quick recap:
> >>
> >>   - I found I couldn't ping a wireless device from another wireless
> >> device.
> >>
> >>   - I could not ping a wireless device from a wired device unless I
> >> pinged
> >> the wired device from the wireless device first (try saying that 3 times
> >> fast).
> >>
> >>   - I then started noticing other strange things, a wireless device that
> >> could ping a wired device a few moments ago could not now do it.
> >>
> >>   - Eventually all of my wireless stuff decided they didn't want to see
> >> my
> >> printer anymore.
> >>
> >>   I was originally using a LinkSys E3000 which I have had for many
> >> years.
> >> I could have attempted to upgrade the firmware but chose not to do it.
> >>
> >>   I bought a Netgear R6200 (AC1200) Dual Band Gigabit router. So far it
> >> has solved all of the above problems. It seems to be a bit faster than
> >> the old router as well.
> >>
> >
> > http://www.dd-wrt.com/wiki/index.php/Supported_Devices#Netgear
> >
> > PY312100189 or PY312400218?
> >
> >
>  
>     It's the R6200 version 2 (PY312400218). And, the first thing I did
>  after getting it was to upgrade the firmware. If it screwed up and got
>  bricked I would just take it back.
>   
:)

RAM 256MB / Flash 128MB / USB 3.0 - nice.

Too bad it isn't officially supported by DD-WRT, such as R6300v2.


>  
>  Jim Lewis
>  
>

Wireless can't ping wireless (SOLVED)

[Jim Lewis]

>  On 29.01.2015 06:07, Jim Lewis wrote:
> >
> >   For those following this thread I solved the problem by getting a new
> > router. Here's a quick recap:
> >
> >   - I found I couldn't ping a wireless device from another wireless
> > device.
> >
> >   - I could not ping a wireless device from a wired device unless I
> > pinged
> > the wired device from the wireless device first (try saying that 3 times
> > fast).
> >
> >   - I then started noticing other strange things, a wireless device that
> > could ping a wired device a few moments ago could not now do it.
> >
> >   - Eventually all of my wireless stuff decided they didn't want to see
> > my
> > printer anymore.
> >
> >   I was originally using a LinkSys E3000 which I have had for many
> > years.
> > I could have attempted to upgrade the firmware but chose not to do it.
> >
> >   I bought a Netgear R6200 (AC1200) Dual Band Gigabit router. So far it
> > has solved all of the above problems. It seems to be a bit faster than
> > the old router as well.
> >
>
>  http://www.dd-wrt.com/wiki/index.php/Supported_Devices#Netgear
>
>  PY312100189 or PY312400218?
>
>  
   It's the R6200 version 2 (PY312400218). And, the first thing I did
after getting it was to upgrade the firmware. If it screwed up and got
bricked I would just take it back.


Jim Lewis

Wireless can't ping wireless (SOLVED)

[poma]

On 29.01.2015 06:07, Jim Lewis wrote:
>  
>    For those following this thread I solved the problem by getting a new
>  router. Here's a quick recap:
>  
>    - I found I couldn't ping a wireless device from another wireless device.
>  
>    - I could not ping a wireless device from a wired device unless I pinged
>  the wired device from the wireless device first (try saying that 3 times
>  fast).
>  
>    - I then started noticing other strange things, a wireless device that
>  could ping a wired device a few moments ago could not now do it.
>  
>    - Eventually all of my wireless stuff decided they didn't want to see my
>  printer anymore.
>  
>    I was originally using a LinkSys E3000 which I have had for many years.
>  I could have attempted to upgrade the firmware but chose not to do it.
>  
>    I bought a Netgear R6200 (AC1200) Dual Band Gigabit router. So far it
>  has solved all of the above problems. It seems to be a bit faster than
>  the old router as well.
>   
http://www.dd-wrt.com/wiki/index.php/Supported_Devices#Netgear

PY312100189 or PY312400218?


>    So, thanks to all who helped me with this. I will try to return
> the
>  favor someday.
>  
>  
>  Jim Lewis
>  
>

Wireless can't ping wireless (SOLVED)

[Jim Lewis]

  For those following this thread I solved the problem by getting a new
router. Here's a quick recap:

  - I found I couldn't ping a wireless device from another wireless device.

  - I could not ping a wireless device from a wired device unless I pinged
the wired device from the wireless device first (try saying that 3 times
fast).

  - I then started noticing other strange things, a wireless device that
could ping a wired device a few moments ago could not now do it.

  - Eventually all of my wireless stuff decided they didn't want to see my
printer anymore.

  I was originally using a LinkSys E3000 which I have had for many years.
I could have attempted to upgrade the firmware but chose not to do it.

  I bought a Netgear R6200 (AC1200) Dual Band Gigabit router. So far it
has solved all of the above problems. It seems to be a bit faster than
the old router as well.

  So, thanks to all who helped me with this. I will try to return the
favor someday.


Jim Lewis

Wireless can't ping wireless (even more info)

[Jim Lewis]

>  On 01/25/15 12:46, Ed Greshko wrote:
> > When in this condition, what is the output of "arp" on big4?
>
>  I meant "arp -n"
>  
 Great idea Ed! It's been years since I worked on Ethernet drivers for IBM
and forgot all about that command. Checking man it shows arp to be
obsolete so I used ip:

big4 /temp # ip -s neigh
fe80::9afc:11ff:fe83:6dfe dev eth0 lladdr 98:fc:11:83:6d:fe router ref 1
used 1364540/1364600/1 STALE
192.168.1.111 dev eth0  ref 1 used 140/200/137 FAILED
192.168.1.1 dev eth0 lladdr 98:fc:11:83:6d:fe ref 31 used 71/11/44 REACHABLE

  As you can see laptop1 at 192.168.1.111 cannot be pinged by big4. Now I
will ping big4 from laptop1:
laptop1 ~ # ping -c 1 192.168.1.109
PING 192.168.1.109 (192.168.1.109) 56(84) bytes of data.
64 bytes from 192.168.1.109: icmp_seq=1 ttl=64 time=0.666 ms

--- 192.168.1.109 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.666/0.666/0.666/0.000 ms

 Now running the ip command again from big4:

big4 /temp # ip -s neigh
fe80::9afc:11ff:fe83:6dfe dev eth0 lladdr 98:fc:11:83:6d:fe router ref 1
used 1364856/1364916/1 STALE
192.168.1.111 dev eth0 lladdr 00:23:4e:df:d1:5d ref 3 used 47/47/32 STALE
192.168.1.1 dev eth0 lladdr 98:fc:11:83:6d:fe ref 25 used 23/11/1 REACHABLE

  Of course the ping/ssh work now as well. Will look at new routers tomorrow.


Jim Lewis

Wireless can't ping wireless (even more info)

[poma]

On 25.01.2015 04:16, Jim Lewis wrote:

>    I guess the only bad thing about spending time on crap like this is
> I
>  used to get paid real money to debug and fix crap like this :).
>   
There ain't no such lunch as a free thing.

Wireless can't ping wireless (even more info)

[Ed Greshko]

On 01/25/15 11:39, Jim Lewis wrote:
> > On 01/25/15 11:16, Jim Lewis wrote:
> >>   Okay, I was able to recreate the other problem after rebooting laptop1
> >> (Fedora 21 Mate-Compbiz Spin). I could not ping it from either wired
> >> box. However, I tried pinging from the router and that worked fine (so
> >> did traceroute). Speaking of traceroute, this from wired box big4:
> >>
> >>
> >> big4 / # traceroute 192.168.1.111
> >> traceroute to 192.168.1.111 (192.168.1.111), 30 hops max, 60 byte
> >> packets
> >>  1  192.168.1.109 (192.168.1.109)  3006.581 ms !H  3006.573 ms !H
> >> 3006.563 ms !H
> >>
> >>   The !H is of course host unreachable.
> > What has IP 192.168.1.109?
> >
>     My wired box, big4, is 192.168.1.109. All the machines can ping it
>  without issues. 
Sorry if this has already been asked/answered.....

192.168.1.111 is what?  I'm guessing a wireless system?

And the IP address of your LinkSys is?

-- 
If you can't laugh at yourself, others will gladly oblige.

Wireless can't ping wireless (even more info)

[Ed Greshko]

On 01/25/15 11:16, Jim Lewis wrote:
>    Okay, I was able to recreate the other problem after rebooting laptop1
>  (Fedora 21 Mate-Compbiz Spin). I could not ping it from either wired
>  box. However, I tried pinging from the router and that worked fine (so
>  did traceroute). Speaking of traceroute, this from wired box big4:
>
>
>  big4 / # traceroute 192.168.1.111
>  traceroute to 192.168.1.111 (192.168.1.111), 30 hops max, 60 byte packets
>   1  192.168.1.109 (192.168.1.109)  3006.581 ms !H  3006.573 ms !H 
>  3006.563 ms !H
>
>    The !H is of course host unreachable. 
What has IP 192.168.1.109?

>    And again, if I ping from laptop1 to big4 it succeeds, and now so does
>  the ping/traceroute from big4:
>
>  big4 / # ping -c 1 192.168.1.111
>  PING 192.168.1.111 (192.168.1.111) 56(84) bytes of data.
>  64 bytes from 192.168.1.111: icmp_req=1 ttl=64 time=12.9 ms
>
>  --- 192.168.1.111 ping statistics ---
>  1 packets transmitted, 1 received, 0% packet loss, time 0ms
>  rtt min/avg/max/mdev = 12.902/12.902/12.902/0.000 ms
>
>  big4 / # traceroute 192.168.1.111
>  traceroute to 192.168.1.111 (192.168.1.111), 30 hops max, 60 byte packets
>   1  192.168.1.111 (192.168.1.111)  20.310 ms  20.394 ms  20.453 ms
>
>  

-- 
If you can't laugh at yourself, others will gladly oblige.

Wireless can't ping wireless (even more info)

[Jim Lewis]

>  Hey Jim.
>
>  I'm going to cheat!! But given that you're retired, you might have a
>  bit of time. Is there a "big box" (staples/bestbuy/radioshack/etc...)
>  close by. If there is, go get a cheap/different router
>  (wired/wireless) and test to see if this box gives you the same
>  behaviour.
>
>  To be honest, never run into this kind of issue, but given murphy, I
>  know that sometime in my future I will!
>
>  Let us know.
>
>  thanks 
  Yes, even here in Hawaii (Oahu) there are stores all over the place.
I'll probably get a new router (NOT a LinkSys) from Best Buy as I got my
modem from them.

  Okay, I was able to recreate the other problem after rebooting laptop1
(Fedora 21 Mate-Compbiz Spin). I could not ping it from either wired
box. However, I tried pinging from the router and that worked fine (so
did traceroute). Speaking of traceroute, this from wired box big4:


big4 / # traceroute 192.168.1.111
traceroute to 192.168.1.111 (192.168.1.111), 30 hops max, 60 byte packets
 1  192.168.1.109 (192.168.1.109)  3006.581 ms !H  3006.573 ms !H 
3006.563 ms !H

  The !H is of course host unreachable.

  And again, if I ping from laptop1 to big4 it succeeds, and now so does
the ping/traceroute from big4:

big4 / # ping -c 1 192.168.1.111
PING 192.168.1.111 (192.168.1.111) 56(84) bytes of data.
64 bytes from 192.168.1.111: icmp_req=1 ttl=64 time=12.9 ms

--- 192.168.1.111 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 12.902/12.902/12.902/0.000 ms

big4 / # traceroute 192.168.1.111
traceroute to 192.168.1.111 (192.168.1.111), 30 hops max, 60 byte packets
 1  192.168.1.111 (192.168.1.111)  20.310 ms  20.394 ms  20.453 ms


  I guess the only bad thing about spending time on crap like this is I
used to get paid real money to debug and fix crap like this :).


Jim Lewis

[bruce]

Hey Jim.

I'm going to cheat!! But given that you're retired, you might have a
bit of time. Is there a "big box" (staples/bestbuy/radioshack/etc...)
close by. If there is, go get a cheap/different router
(wired/wireless) and test to see if this box gives you the same
behaviour.

To be honest, never run into this kind of issue, but given murphy, I
know that sometime in my future I will!

Let us know.

thanks


On Fri, Jan 23, 2015 at 10:25 PM, Jim Lewis <jim(a)jklewis.com&gt; wrote:
> > On 01/24/15 09:59, bruce wrote:
> >> Just sort of following the thread.
> >>
> >> Does this same behaviour happen if you have a separate box running a
> >> different distro? Can it not ping as well?
> >>
> >> Curious.
> >
> > Sort of doing the same as well....
> >
> > FWIW, the router itself has a "diagnostic" screen and one option is to
> > ping an IP address.  So, wonder if the OP has tried pinging a wireless
> > system directly from the router.
> >
> > Also, another tool to try would be tcping.
> >
>
>    Now why did I not think to try pinging from the router itself? It's a
>  good damn thing I am retired. Anyway, that is an excellent idea and was
>  going to try it. However, now, for some reason, both Fedora 21 boxes can
>  be shutdown, or their wireless interface disabled, and when brought back
>  up can be pinged without a problem from my wired computer. Bizarre. I'll
>  keep watching this. When it happens again I'll try pinging from the
>  router.
>
>    The original problem is still there. I cannot ping from wireless to
>  wireless. I have three Fedoras and one Ubuntu systems, all wireless. No
>  box can ping another one while wireless. They can all access the
>  Internet just fine. They can all ping to a wired box. The wired box can
>  ping/ssh into them (I currently have 4 ssh sessions open, 1 for each
>  laptop). If I change to the wired interface it works as expected. Yes, I
>  am using the correct IP (gee even I can do that correctly). I'm back to
>  being convinced this is a router issue. It's too bad the jerks at
>  LinkSys wanted me to pay them to attempt to get it resolved.
>
>    I'll look into tcping and/or tcpdump soon.
>
>
>  Jim Lewis
>
>
>  --
>  users mailing list
>  users(a)lists.fedoraproject.org
>  To unsubscribe or change subscription options:
>  https://admin.fedoraproject.org/mailman/listinfo/users
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>  Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>  Have a question? Ask away: http://ask.fedoraproject.org

[Jim Lewis]

>  On 01/24/15 09:59, bruce wrote:
> > Just sort of following the thread.
> >
> > Does this same behaviour happen if you have a separate box running a
> > different distro? Can it not ping as well?
> >
> > Curious.
>
>  Sort of doing the same as well....
>
>  FWIW, the router itself has a "diagnostic" screen and one option is to
>  ping an IP address.  So, wonder if the OP has tried pinging a wireless
>  system directly from the router.
>
>  Also, another tool to try would be tcping.
>  
  Now why did I not think to try pinging from the router itself? It's a
good damn thing I am retired. Anyway, that is an excellent idea and was
going to try it. However, now, for some reason, both Fedora 21 boxes can
be shutdown, or their wireless interface disabled, and when brought back
up can be pinged without a problem from my wired computer. Bizarre. I'll
keep watching this. When it happens again I'll try pinging from the
router.

  The original problem is still there. I cannot ping from wireless to
wireless. I have three Fedoras and one Ubuntu systems, all wireless. No
box can ping another one while wireless. They can all access the
Internet just fine. They can all ping to a wired box. The wired box can
ping/ssh into them (I currently have 4 ssh sessions open, 1 for each
laptop). If I change to the wired interface it works as expected. Yes, I
am using the correct IP (gee even I can do that correctly). I'm back to
being convinced this is a router issue. It's too bad the jerks at
LinkSys wanted me to pay them to attempt to get it resolved.

  I'll look into tcping and/or tcpdump soon.


Jim Lewis

[Ed Greshko]

On 01/24/15 09:59, bruce wrote:
>  Just sort of following the thread.
>
>  Does this same behaviour happen if you have a separate box running a
>  different distro? Can it not ping as well?
>
>  Curious. 
Sort of doing the same as well....

FWIW, the router itself has a "diagnostic" screen and one option is to ping an
IP address.  So, wonder if the OP has tried pinging a wireless system directly from the
router.

Also, another tool to try would be tcping.

-- 
If you can't laugh at yourself, others will gladly oblige.

[bruce]

Hi.

Just sort of following the thread.

Does this same behaviour happen if you have a separate box running a
different distro? Can it not ping as well?

Curious.

Thanks...

On Fri, Jan 23, 2015 at 6:29 PM, Jim Lewis <jim(a)jklewis.com&gt; wrote:
> > On 01/23/2015 05:46 PM, poma wrote:
> >
> >  > http://www.dd-wrt.com/wiki/index.php/Linksys_E3000
> >
> > Honestly, reading this nightmare I would invest ~$65 in a TP-LINK
> > TL-WDR3600
> >
> > It has similar performance, Atheros hardware and perfect dd-wrt/openwrt
> > support...
> >
> > regards Jens
> >
>
>   Calling that a nightmare is a real understatement. How did things get so
>  stupid? Anyway, I believe there are two separate problems here. The
>  router is almost certainly part of the problem, and Fedora 21 has a
>  problem that Fedora 20 doesn't. I will investigate this more thoroughly
>  and report back.
>
>   Thanks everyone for the help.
>
>
>  Jim Lewis
>
>
>  --
>  users mailing list
>  users(a)lists.fedoraproject.org
>  To unsubscribe or change subscription options:
>  https://admin.fedoraproject.org/mailman/listinfo/users
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
>  Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
>  Have a question? Ask away: http://ask.fedoraproject.org

[Jim Lewis]

>  On 01/23/2015 05:46 PM, poma wrote:
>
>   > http://www.dd-wrt.com/wiki/index.php/Linksys_E3000
>
>  Honestly, reading this nightmare I would invest ~$65 in a TP-LINK
>  TL-WDR3600
>
>  It has similar performance, Atheros hardware and perfect dd-wrt/openwrt
>  support...
>
>  regards Jens
>  
 Calling that a nightmare is a real understatement. How did things get so
stupid? Anyway, I believe there are two separate problems here. The
router is almost certainly part of the problem, and Fedora 21 has a
problem that Fedora 20 doesn't. I will investigate this more thoroughly
and report back.

 Thanks everyone for the help.


Jim Lewis

[Jens Neu]

On 01/23/2015 05:46 PM, poma wrote:

>  http://www.dd-wrt.com/wiki/index.php/Linksys_E3000 
Honestly, reading this nightmare I would invest ~$65 in a TP-LINK TL-WDR3600

It has similar performance, Atheros hardware and perfect dd-wrt/openwrt 
support...

regards Jens

[poma]

On 23.01.2015 02:30, Jim Lewis wrote:
...
>    I use a LinkSys E3000 which I have had for a very long time. I
> checked
>  their site and looked at the Release Notes for firmware upgrades. No
>  mention of this issue and so I am hesitant to perform it (I did however
>  download the latest file). I got into their Live Chat and the guy said
>  since the unit is no longer in warranty I would have to pay to get
>  assistance. I thought about doing this, but he could not guarantee
>  success and the payment is not refundable. I thought that sucked and
>  told him so.
>  
>   So, does anyone have any ideas about how I might solve this? I am going
>  to be rather surprised if the problem is not the router. If it matters 
http://www.dd-wrt.com/wiki/index.php/Linksys_E3000

If you choose to upgrade with DD-WRT,
read everything written on a given link at least 10 times, consult with people on the
forum and good luck.
Of course you do so at your own risk and expense.

[Jim Lewis]

>  On 01/22/2015 05:30 PM, Jim Lewis wrote:
> >
> >   I just realized that my wireless computers can't ping each other.
> > Wireless to wired and vice versa is just fine. The IP addresses (DHCP)
> > are all on the same subnet. If I switch to wired the computer can then
> > ping a wired or wireless. The computers can all access the Internet at
> > any time (either wired or wireless). I did some research and have
> > determined the problem might be my router.
> >
> >    I use a LinkSys E3000 which I have had for a very long time. I
> > checked
> > their site and looked at the Release Notes for firmware upgrades. No
> > mention of this issue and so I am hesitant to perform it (I did however
> > download the latest file). I got into their Live Chat and the guy said
> > since the unit is no longer in warranty I would have to pay to get
> > assistance. I thought about doing this, but he could not guarantee
> > success and the payment is not refundable. I thought that sucked and
> > told him so.
> >
> >   So, does anyone have any ideas about how I might solve this? I am
> > going
> > to be rather surprised if the problem is not the router. If it matters
> > here is my hardware:
> >
> > Fedora 14 - wired desktop
> > Fedora 20 - wireless laptop
> > Fedora 21 - wireless laptop (or wired)
> > Fedora 21 - wireless laptop (or wired)
> > Ubuntu 12.04.2 LTS - wireless (practically unusable because of Gnome 3)
>
>  Are the wired and wireless connections on the same subnet? If so, you
>  may be having with the routing of packets. Simply yanking out a cable
>  doesn't guarantee that the default route gets changed (unless you're
>  using NetworkManager).
>
>  Consider: "A" has 192.168.1.10/24 on the wired NIC and 192.168.1.100/24
>  on the wireless (both NICs on the same subnet). "B" has 192.168.1.11/24
>  and 192.168.1.101/24 respectively. Now, "A" sends out a ping to "B".
>  Which NIC does it use? It will use the default route. Odds are that's
>  the wired NIC. Now, if you pull "A"s cable out, the default route is
>  still over the wire (unless NetworkManager or you manually change it).
>  Hence the outgoing ping never gets sent.
>
>  So, check the routes. On "A" with the wired cable hooked up, do a
>
>  	netstat -rn
>
>  as root and look for the line with the "UG" in it. The value under
>  "Iface" is which NIC is the default one. Now pull one of cables and
>  repeat the netstat command. See if the route changes to the other NIC.
>  If it does, you should be able to ping the other nodes. If it doesn't,
>  you'll need to drop the wireless connection and restart it (or change
>  the route manually to the other NIC) and try the ping again.
>
>  It's always dangerous to have two different physical NICs on the same
>  subnet because this sort of routing issue can occur. One way around it
>  is to use the two NICs in a mode 1 (failover) bonded pair. "bond0"
>  gets the IP and the network system will automatically fail over to the
>  other NIC if the primary goes down.
>  ----------------------------------------------------------------------
>  - Rick Stevens, Systems Engineer, AllDigital    ricks(a)alldigital.com -
>  - AIM/Skype: therps2        ICQ: 22643734            Yahoo: origrps2 -
>  -                                                                    -
>  -       "As for me, I aspire to be the Walmart Greeter in Hell."     -
>  ----------------------------------------------------------------------
>  
Hi Rick,

  I do not ever have 2 NICs enabled on the same subnet at the same time.
Whenever I want to switch from wired to wireless, or vice versa, I
always use NetworkManager to disable the current interface first before
enabling the other one. Note too that if this had been a mixed up NIC
problem the laptop would not have been able to ping anything. Wired
always works. I also always check ifconfig for the current IP.

 If I weren't such a wuss I would just go ahead and upgrade the firmware
on my router. That might actually solve the problem. It's currently at
version 1.0.02 and the latest is 1.0.06. However, I have seen these
updates fail so many times (mostly at IBM) I'm too scared to try it.


Jim Lewis