Hello, I will described here a problem that I had with OS4 for ages and more often since OS4.1.5. It seems a (bit) common problem as I read some posts about it.
Whatever my uses of internet (torrent, ftp, web...), I regularly got this error:
PING 192.168.0.1 (192.168.0.1): 56 data bytes ping: sendto: No buffer space available ping: wrote 192.168.0.1 64 chars, ret=-1
This the result of a ping to my router configured in OS4 as my primary dns server.
I thought that the fault could be my router but I have just tested it with my phone in wifi mode. I could download some files.
I would want to know if someone has found a solution for that. Here are some values stored in Envarc:roadshow/tcp do_timestamps = 0 do_win_scale = 0 mssdflt = 1460 recvspace = 65536 sendspace = 65536 (added recenttly to see if something would change :( ) use_mssdflt_for_remote = 0
Thanks for advices
Since a lot of months without an amiga to love, I was lost. Now I feel happiness again with a Sam Flex 800 .
Because that doesn't look like a misconfiguration but completely borked internet prefs... if it otoh drops only when you have heavy traffic then i'd check the cables from your miggy to the router.
I will test the cable even I don't think it is the culprit. When I stop all tools related to internet, do a netshutdown and an addnetinterface, all is working.
I often have this problem when there is a lot of traffic but not only, even when there is no traffic.
Tou wrote about borked internet prefs, could you tell me more ?
Since a lot of months without an amiga to love, I was lost. Now I feel happiness again with a Sam Flex 800 .
I will test the cable even I don't think it is the culprit. When I stop all tools related to internet, do a netshutdown and an addnetinterface, all is working.
Ah, there are "tools" running in the background...what kind of "tools"?
If it drops out and this case is not reproduceable, i'd start by not starting any of those "tools" and then one by one bringing them back and testing them if one of them is maybe the bad guy.
Quote:
Tou wrote about borked internet prefs, could you tell me more ?
Sure, you have "Internet" in your Prefs drawer. Your prefs which are used right now are already saved in a file.
What you can do is set up completely fresh preferences and try with those. Maybe one or some of your options don't like what one or some of your "tools" do?
Those roadshow env settings were intended to speed up the net connection, I still use them on the micro & x1000. As far as the ping test, I have the same IP, try 192.168.1.1, works here.
Look, only one leg, count em, one! X1000/PA6T@1800MHz/2Gb/Radeon 4850
I had plenty of memory but as soon I got the error, I will post here the output of memstat.
Sundown, I don't really understand what you want me to do. I couldn't ping to my router (192.168.0.1) but I can ping to my amiga (192.168.0.2) without problem.
My internet connections are blocked by the router, it is a local problem as the world wide connection is not stopped (tested by the download from my phone). At the beginning, I thought that was the "classic" ethernet problem and the remedy is to switch the router off and on. Here is not the case. The only mean to resolve the problem is to stop the interface (netshutdown) and to sart again (addnetinterface).
Since a lot of months without an amiga to love, I was lost. Now I feel happiness again with a Sam Flex 800 .
I had this "cannot ping my router" too when i started using Roadshow years back.
Please post DEVS:NetInterfaces/<your Interface> (Alternatively...are you using DHCP?)
Did you set the ip address of your amiga (.0.2) in the router? Because it looks a lot like it? (Normally hooked up computers don't start right after the router address, rather they have an address space with some numbers between, like .0.20) Could you change that so the router might be able to freely choose one address from it's ip address space and try again?
Another thing would be to enhance the number in the possible address space if it turns out to be too few (default should be around 200 possible addresses, like from .0.20 tp .0.200), so the router can skip addresses that are used for reasons whatsoever.
yescop wrote: Hello, I will described here a problem that I had with OS4 for ages and more often since OS4.1.5. It seems a (bit) common problem as I read some posts about it.
Whatever my uses of internet (torrent, ftp, web...), I regularly got this error:
PING 192.168.0.1 (192.168.0.1): 56 data bytes ping: sendto: No buffer space available ping: wrote 192.168.0.1 64 chars, ret=-1
SAM460? I had that problem a few times, usually when also doing lots of disk access. Chalked it down to a driver bug somewhere.
Number of pages in page cache: 0 Number of cache lines in page cache: 10 (should be 10) Number of empty lines in cache: 10 Number of full lines in cache: 0 Number of pages page cache claims to have allocated: 160 Number of pages page cache claims to have dropped (in cache): 0 Number of pages page cache claims to have dropped (from disk): 0
Raziel, i give you my interface configuration: device=ppc440ep_eth.device hardwaretype=Ethernet address=192.168.0.20 netmask=255.255.255.0
As you see, I change the amiga address to 0.20 (before set to 0.2). Moreover, as you wrote to me, I set in the router the ip of my amiga. I can tell why I change my ip to 0.20. When I tried to configure in the router the previous amiga ip, I had an ip error (0.2 not valid). Nevertheless, the router accepted this ip (strange). I used the DHCP from 0.5 to 0.240 more or less.
Now I will test again and hope that no error will occur.
Since a lot of months without an amiga to love, I was lost. Now I feel happiness again with a Sam Flex 800 .
Raziel, i give you my interface configuration: device=ppc440ep_eth.device hardwaretype=Ethernet address=192.168.0.20 netmask=255.255.255.0
As you see, I change the amiga address to 0.20 (before set to 0.2). Moreover, as you wrote to me, I set in the router the ip of my amiga.
I hope you have set it in the HOSTS tab and nowhere else?
Quote:
I can tell why I change my ip to 0.20. When I tried to configure in the router the previous amiga ip, I had an ip error (0.2 not valid). Nevertheless, the router accepted this ip (strange). I used the DHCP from 0.5 to 0.240 more or less.
If you use dhcp add a checkmark to DHCP in the first tab of your internet prefs, or add this line to your config
Sorry, I wasn'tso precise. when I wrote I used DHCP, I wanted to say that the router uses DHCP to any material connected and now configure my amiga ip to 0.20.
In internet prefs, I don't use DHCP and use ip fixed for my amiga. I did that to configure the ports associated to my amiga, essentially ports around 2700 for my torrent connections.
Since a lot of months without an amiga to love, I was lost. Now I feel happiness again with a Sam Flex 800 .
Here are my conclusions. I launched several ctorrents in shells without any problem. There were not any other program using internet. When I launch MuiOwb and the cpu is at 100% (heavy pages for example), the pourcentage of internet drop is very high.
I can't test with timberwolf as it is too slow on SAM 440.
Since a lot of months without an amiga to love, I was lost. Now I feel happiness again with a Sam Flex 800 .
I haven´t got internet drops, but all sorts of other strange behaviour on my XE when there was 100% cpu abnd lots of ram useage.
This isn´t exactly related to your problem, but if the drops accumulate while downloading stuff with a torrent i´d blame the torrent program probably doing forbidden stuff which shows itself in 100% cpu conditions.
Not really helpful i know, but i learned to blame any third party porgram first before blaming anything OS related (because the OS is so damn stable)
Raziel, Yes you could be right but I made this test.
I launched four ctorrents application and use muiOWB in 100% cpu condition. I used the same ctorrent and create an another 100% cpu conditions. I used ffmpeg to convert some videos or I copied big files or I just listed a big directory. In these conditions, I never obtained an internet drop.
It is for me an internet connection problem but I am right with you. I can't be sure that ctorrent is not the culprit.
Since a lot of months without an amiga to love, I was lost. Now I feel happiness again with a Sam Flex 800 .
PING 192.168.0.1 (192.168.0.1): 56 data bytes ping: sendto: No buffer space available ping: wrote 192.168.0.1 64 chars, ret=-1
That sounds like you are out of memory.
I don't think it's memory related. That message is a typical symptom of a locked-up driver or NIC. The driver has taken all of Roadshow's fixed number of buffers and isn't giving them back.
I tried such problem in the past: - on OS4 I could use HTTP, mails with no problem but FTP would always stop after a few kilobytes were transfered - on the same router, my PC didn't have any problem, even when using FTP but when I replaced the router everything worked again! Strange issue indeed :-/
Anyway, you can try to change the value of MTU in your netinterface file like: mtu=1492
I also noticed internet dropouts and I used Scout to look at the lib_OpenCnt of bsdsocket.library, and that value is just screwed up!
Normally it is 10 after I have my stack of programs running (AmIRC, SabreMSN, YAM, MUI-OWB) but then suddenly I noticed it dropped to 1 and later it became 0! Internet still worked though. But this morning internet had stopped working again and the opencnt was 65531, so about to flip over. BUT: I think it went backwards rather than forward, since it started at 10, then was 1 then 0 (with all programs still running).
Software developer for Amiga OS3 and OS4. Develops for OnyxSoft and the Amiga using E and C and occasionally C++