[SOLVED] Jessie can be pinged only if it pings first
DebianThis forum is for the discussion of Debian Linux.
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.
Debian Jessie connects via WICD on a WPA wireless network and can ping the whole network and the internet. But it can't be reached nor pinged unless it pings first any machine that want to established contact.
resolv.conf (if it matters) is
domain lan
search lan
nameserver 192.168.1.1
but systemd-resolved is inactive (I've tried to start/enable it without improvement). I also tried to install and enable/start resolvconf without improvement either.
but systemd-resolved is inactive (I've tried to start/enable it without improvement). I also tried to install and enable/start resolvconf without improvement either.
You can only have one network management system active at a time. Perhaps you're using NetworkManager?
"So the work-around is to insert a static entry in the ARP cache for all the other computers in the network that need to interact with the affected computer. For a Windows computer, "arp -h" gives an example of how to do that; for a Linux machine, "man arp" should tell you what you need to know. Also the affected computer needs to always have the same IP address, either a static IP address or a DHCP reservation, so that the static ARP entries are guaranteed to be correct. For me there aren't many other computers on my home network, so the work-around isn't much of a hardship. I did the work-around, and now both ping and Samba seem to work, hooray!"
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.