Lan connection problem -

[Bob Goodwin]

On 02/09/16 17:02, Tom Rivers wrote:
> On 2/9/2016 3:46 PM, Bob Goodwin wrote:
>>
>> I can work around the problem by 
>> having my router powered from a UPS 
>> and being careful not to reboot the 
>> router. Once the router reboots the 
>> various wireless devices I have, 
>> printer, video cameras, etc. need 
>> their ac power "recycled" to get them 
>> connected to the LAN again. Very 
>> inconvenient at this time of year 
>> since some of these devices are in 
>> another building ...
>>
>> When this happens I can not ping 
>> those devices, normally I should be 
>> able to connect to the cameras with 
>> the browser and reboot them when some 
>> glitch occurs but now when I lose the 
>> LAN connection I have to visit them 
>> and pull the plug. The printer is 
>> near at hand and toggling the power 
>> switch gets it back on.
>
> I would make note of the MAC addresses 
> on each of the devices and check your 
> router to see if those devices are 
> connected via wireless link after it 
> reboots.  Also, you may be able to 
> check the DHCP log of the router to 
> see if requests are being made for IP 
> addresses by any of the devices. 
> Sometimes is will have a table of 
> devices that have secured IP addresses 
> and list their associate MAC addresses.
>
> If they are shown as connected via 
> wireless and are also in the DHCP 
> table, then try nmap and see what 
> results you get.
>
>
> Tom
.

I have gone over the mac's and static 
dhcp addresses carefully, notypos or 
such there.

Neither journalctl or the router logs 
show anything at the times when it fails 
to connect or ping those addresses, 
those that connect do show, but no clue 
about the ones that don't.


[root at Box10 bobg]# ping -c 3 192.168.1.52
PING 192.168.1.52 (192.168.1.52) 56(84) 
bytes of data.
 From 192.168.1.10 icmp_seq=1 
Destination Host Unreachable
 From 192.168.1.10 icmp_seq=2 
Destination Host Unreachable
 From 192.168.1.10 icmp_seq=3 
Destination Host Unreachable

--- 192.168.1.52 ping statistics ---
3 packets transmitted, 0 received, +3 
errors, 100% packet loss, time 1999ms
pipe 3


All this stuff just worked for several 
years until one day last week, I've lost 
track of the exact date since it was 
just an annoyance at the time ...

Now to add to the confusion I just tried 
an F23 portable that doesn't get updated 
as often and it connects to the camera 
192.168.1.52 that this box10 can't as 
shown above. I will try booting another 
computer to Fedora 22 and see if it 
still works as before ... I suspect that 
perhaps something may have changed in 
network manager?

Bob

-- 
Bob Goodwin - Zuni, Virginia, USA
http://www.qrz.com/db/W2BOD
box10  FEDORA-23/64bit LINUX XFCE POP3