"connect: No buffer space available" in my local network area
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
"connect: No buffer space available" in my local network area
I'm running mandrake 10 and KDE 3.2.2.. I have a NIC (eth0) connected to a network ADSL modem and a virtual NI (eth0:1) connected to my Laptop win2000k..
Just After my linux box starts the network seems to work perfectly, but after some minutes, I can't reach my Laptop and my localhost.. I can see it:
ping localhost
connect: No buffer space available
ping 192.168.0.66 (my laptop)
connect: No buffer space available
ping 82.50.10.12 (my PPP0 address)
connect: No buffer space available
It's very strange, beacuse if I type...
ping google.com
PING google.com (216.239.57.99) 56(84) bytes of data.
64 bytes from 216.239.57.99: icmp_seq=1 ttl=239 time=1679 ms
64 bytes from 216.239.57.99: icmp_seq=2 ttl=239 time=2191 ms
netstat -nr
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.100.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.100.1 0.0.0.0 UG 0 0 0 ppp0
iptables -nvL
Chain INPUT (policy ACCEPT 1010K packets, 530M bytes)
pkts bytes target prot opt in out source destination
3 84 ACCEPT all -- * * 192.168.0.99 192.168.0.1
0 0 ACCEPT all -- * * 192.168.0.66 192.168.0.1
Chain FORWARD (policy ACCEPT 7931 packets, 7312K bytes)
pkts bytes target prot opt in out source destination
Chain OUTPUT (policy ACCEPT 1133K packets, 464M bytes)
pkts bytes target prot opt in out source destination
notice: I've a boot-script that allow ip forwarding to 2 LAN-IP: 192.168.0.99 (my laptop) and 192.168.0.66 (for friends that sometimes usa my LAN). My Linux is the gateway (192.168.0.1) with eth0:1 interface.
I don't understand very well this output, can you explain me it?
and try to ping localhost, your ppp IP and other sites.
You will not be able to ping your LAN (192.168.x.x). If you are able to ping to localhost, the ppp IP for extended period of time, we may assume that the virtual interface is creating this problem...
And I think it's not the problem... This configuration worked until a few days ago... Then I had a problem with some configuration file.. KDE didn't start because DCOP config in my home/user/ seemed to be disappeared! .. To solve this problem I've
cp home/usr2/.DCOP_server_myhost__0 /home/user/
After this, KDE started ok, But I don't know if this could be the problem: because my internet connection didn't start, in the meanwhile I worked around my network settings..
And, over all.. I don't know what DCOP is..
I have too many variables in this problem!!!
Last edited by SpaceCowboy; 08-06-2004 at 04:04 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.