Odd networking issue

01 Jan 16 14:26, you wrote to All:

ji> I'm running a Pi 'B' and PiMAME software. I've got a Netgear USB ji> wireless dongle that I'm using for networking. It's at a fixed IP of ji> 10.1.1.71

ji> However, the network randomly (it seems) just...goes away.

ji> Example pinging it:

pinging it from where? what does a traceroute show? what does arp show?

)\/(ark

... Eddie's one of our prize students - we're giving him away next week.

Reply to
mark lewis
Loading thread data ...

I'm running a Pi 'B' and PiMAME software. I've got a Netgear USB wireless dongle that I'm using for networking. It's at a fixed IP of

10.1.1.71

However, the network randomly (it seems) just...goes away.

Example pinging it:

64 bytes from 10.1.1.71: icmp_seq=4235 ttl=64 time=36.645 ms 64 bytes from 10.1.1.71: icmp_seq=4236 ttl=64 time=59.978 ms 64 bytes from 10.1.1.71: icmp_seq=4237 ttl=64 time=81.130 ms 64 bytes from 10.1.1.71: icmp_seq=4238 ttl=64 time=100.393 ms 64 bytes from 10.1.1.71: icmp_seq=4239 ttl=64 time=18.336 ms 64 bytes from 10.1.1.71: icmp_seq=4240 ttl=64 time=42.556 ms Request timeout for icmp_seq 4241 Request timeout for icmp_seq 4242 Request timeout for icmp_seq 4243 Request timeout for icmp_seq 4244 Request timeout for icmp_seq 4245 Request timeout for icmp_seq 4246

This is with it just sitting at the main PiMAME menu.

Any thoughts?

Many thanks.

Jim

--
Orbiting inside the Roche Limit of sanity.
Reply to
jim

The simplest thing to do might be to change the dongle. With the widespread use of WiFi, you also may have some sort of interference problem.

Apropos of nothing, the inexpensive USB/WiFi dongles on my win7 machines seem to be more reliable than the expensive ones. ????

Reply to
Charlie

In message , jim writes

Not thought as such, but I've got a PiB+ sitting on a network using an Edimax WiFi dongle, and that is not dissimilar to what I see. Sometimes I get really fast pings, other times it can be over a second, sometimes no response (which can last for hours) I've got a cron job that pings the router every minute, and logs the results (along with the CPU and GPU temperatures).

From Yesterday's log (times are milli seconds):

1040 - 5.618 CPU temp=41.7 C GPU temp=42.2'C 1041 - 3.649 CPU temp=41.7 C GPU temp=41.7'C 1042 - 1335.856 CPU temp=41.2 C GPU temp=41.2'C 1043 - 17.311 CPU temp=42.2 C GPU temp=42.2'C 1044 - 19.257 CPU temp=42.8 C GPU temp=42.8'C 1045 - 19.300 CPU temp=42.2 C GPU temp=42.2'C 1046 - 165.862 CPU temp=42.8 C GPU temp=42.8'C 1047 - 13.649 CPU temp=43.3 C GPU temp=43.3'C 1048 - 21.424 CPU temp=43.3 C GPU temp=43.3'C 1049 - 927.680 CPU temp=42.2 C GPU temp=42.8'C 1050 - 12.454 CPU temp=42.8 C GPU temp=42.8'C

Adrian

--
To Reply : 
replace "bulleid" with "adrian" - all mail to bulleid is rejected 
 Click to see the full signature
Reply to
Adrian

Firewall behaviour?

Reply to
Rob Morley

Duplicate IP address somewhere?

--
Alan Adams, from Northamptonshire 
alan@adamshome.org.uk 
 Click to see the full signature
Reply to
Alan Adams

Nope, no firewall in action and I'm very sure that it isn't a duplicate IP.

I'm wondering if, as was suggested elsewhere, it's a Netgear thing. The dongle performs flawlessly on my W7 box though.

Since I have a need for a second dongle anyway, I'll get a new one for the Pi.

Any recommendations?

Jim

--
Orbiting inside the Roche Limit of sanity.
Reply to
jim

I had some issues with older broadcomm chipsets, and Linux.

Issues that sound similar - sudden lack of comms, for a few seconds.

--
If you tell a lie big enough and keep repeating it, people will  
eventually come to believe it. The lie can be maintained only for such  
 Click to see the full signature
Reply to
The Natural Philosopher

The US raspberry web site (Lady Ada, etc) mentions that there have been problems with various WiFi adapters. I've had better luck with the little cheap no name adapters than the common name brands.

The last really bad go around I had was an adapter that worked flawlessly in XP, sort of OK in early win 7, then more erratically with later 7 & 8. That adapter was a name brand "long range" adapter. The mfrs drivers were updated several times, each time improving things, but not quite fixing the problem. There was some sort of initialization/reset problem as far as we could tell. Sometimes just unplugging from one USB port and plugging into another worked. Disabling the driver, and re enabling it also sometimes worked.

Reply to
Charlie

ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.