Re: Not able to ping other pcs in LAN.

On Tue, Apr 29, 2025 at 10:06:05AM +0700, Max Nikulin wrote: > On 28/04/2025 20:31, to...@tuxteam.de wrote: > > On Mon, Apr 28, 2025 at 01:12:17PM +, > > mailinglists.accustom...@aleeas.com wrote: > > > On Monday, April 28th, to...@tuxteam.de wrote: > > > > > > > > At some point, it'd been in

Re: Not able to ping other pcs in LAN.

On 28/04/2025 20:31, to...@tuxteam.de wrote: On Mon, Apr 28, 2025 at 01:12:17PM +, mailinglists.accustom...@aleeas.com wrote: On Monday, April 28th, to...@tuxteam.de wrote: At some point, it'd been interesting whether yours were IPv4 zeroconf "link-local" addresses, i.e. in the 169.254.0.

Re: Not able to ping other pcs in LAN.

d [...] - Another: Message-ID: <174576227925.7.18335587670536658966.695639...@aleeas.com> From: mailinglists.accustom...@aleeas.com ping: [hostname].local: Name or service not known. Note the ".local" domain? *If* the OP had explicitly set that up in a (heh) local DNS, I assume they would k

Re: Not able to ping other pcs in LAN.

; > > > > > Not particularly. > > > > > > Try this: > > > > > > sudo apt install tshark > > > sudo tshark -f 'port 5353' -c 4 -N dnt & > > > ping -c 4 whatever.local > > > > > > At least for me, it s

Re: Not able to ping other pcs in LAN.

On Mon, Apr 28, 2025 at 01:12:17PM +, mailinglists.accustom...@aleeas.com wrote: > On Monday, April 28th, to...@tuxteam.de > wrote: > > > > > > > That was my guess. By now I think it is irrelevant, since we > > advanced to the mDNS issue. At some point, it'd been interesting > > whether y

Re: Not able to ping other pcs in LAN.

On Monday, April 28th, to...@tuxteam.de wrote: > > > That was my guess. By now I think it is irrelevant, since we > advanced to the mDNS issue. At some point, it'd been interesting > whether yours were IPv4 zeroconf "link-local" addresses, i.e. > in the 169.254.0.0/16 range: I'd bet they are :

Re: Not able to ping other pcs in LAN.

On Mon, Apr 28, 2025 at 12:40:54PM +, mailinglists.accustom...@aleeas.com wrote: > On Monday, April 28th, to...@tuxteam.de wrote: > > > > > > > While it is a good idea to have tshark, we already know that > > the OP's machine > > > > - is trying to resolve via mDNS > > - that part is failing.

Re: Not able to ping other pcs in LAN.

On Monday, April 28th, to...@tuxteam.de wrote: > > > While it is a good idea to have tshark, we already know that > the OP's machine > > - is trying to resolve via mDNS > - that part is failing. Yeah, Thanks for understanding. There are couple of connection like 0.0.0.0:mdns and [::]:mdns that I

Re: Not able to ping other pcs in LAN.

On Monday, April 28th, Anssi Saari - anssi.sa...@debian-user.mail.kapsi.fi wrote: > > Do you have a firewall in any computer? mdns uses UDP port 5353 and that > would need to be allowed for it to work. Yes, I have enabled firewall on both systems. But So was in the previous system, and mDNS us

Re: Not able to ping other pcs in LAN.

mailinglists.accustom...@aleeas.com writes: > Hi all, > > I recently installed Debian on my old desktop, before this it was > running Ubuntu. So my issue is before installing debian I was able to > ping me other machine using ```ping hostname.local```, but after > installing

Re: Not able to ping other pcs in LAN.

> sudo apt install tshark > > sudo tshark -f 'port 5353' -c 4 -N dnt & > > ping -c 4 whatever.local > > > > At least for me, it shows the mdns requests being sent and the answers > > received. > > > > The good test again, now in two part

Re: Not able to ping other pcs in LAN.

t; Not particularly. > > Try this: > > sudo apt install tshark > sudo tshark -f 'port 5353' -c 4 -N dnt & > ping -c 4 whatever.local > > At least for me, it shows the mdns requests being sent and the answers > received. > The good test again, now in

Re: Not able to ping other pcs in LAN.

On Sun, Apr 27, 2025 at 3:33 PM wrote: > > Hi, > > Here are the output of the cmnds that tomas suggested. ... with all the good stuff elided > Hope that helps. Not particularly. Try this: sudo apt install tshark sudo tshark -f 'port 5353' -c 4 -N dnt & ping -c 4

Re: Not able to ping other pcs in LAN.

On Monday, April 28th, Timothy M Butterworth timothy.m.butterwo...@gmail.com wrote: > Are you able to ping by IP address instead of host name? Yes, I am able to ping other machines in LAN through IPs. > Are you able to resolve the DNS name with dig? dig hostname.local NO, QU

Re: Not able to ping other pcs in LAN.

On Sun, Apr 27, 2025 at 12:12 PM wrote: > Hi all, > > I recently installed Debian on my old desktop, before this it was running > Ubuntu. So my issue is before installing debian I was able to ping me other > machine using ```ping hostname.local```, but after installing debian 12

Re: Not able to ping other pcs in LAN.

On Sun, Apr 27, 2025 at 04:56:26PM +, mailinglists.accustom...@aleeas.com wrote: > Hi, > > Here are the output of the cmnds that tomas suggested. Thanks for those. Another one which might be of interest (I suggest you don't obfuscate the IP addresses; otherwise it's on you to interpret them)

Re: Not able to ping other pcs in LAN.

On 27.04.2025 16:30 Uhr mailinglists.accustom...@aleeas.com wrote: > No, [hostname].local is not in /etc/hosts, So does in ubuntu machine. > As far as I know avahi should be resolving these. This is the case. Resolve should be done via mdns, which is handled by Avahi. Please use wireshark and sni

Re: Not able to ping other pcs in LAN.

On 27.04.2025 16:30 Uhr Andy Smith wrote: > Okay so I see why OP was saying so much about mdns and avahi. The > .local hostnames are meant to be autodiscovered, not present in hosts > file or DNS as such, and that's what the mdns4_minimal is for in > /etc/nsswitch.conf. mdns4 limits that to IPv4,

Re: Not able to ping other pcs in LAN.

in my previous mail. This is output I > > > get when I ping other machine: > > > > > > ping: [hostname].local: Name or service not known. where [hostname] > > > is a placeholder. > > > > No, no. Please show us exactly what you see, by copying from the

Re: Not able to ping other pcs in LAN.

. This is > > > output I get when I ping other machine: > > > > > > ping: [hostname].local: Name or service not known. where > > > [hostname] is a placeholder. > > > > No, no. Please show us *exactly* what you see, by copying from the > > termi

Re: Not able to ping other pcs in LAN.

On Sun, Apr 27, 2025 at 09:30:43AM -0600, Charles Curley wrote: > On Sun, 27 Apr 2025 13:57:55 + > mailinglists.accustom...@aleeas.com wrote: > > > Sorry I didn't mentioned output in my previous mail. This is output I > > get when I ping other machine: > > >

Re: Not able to ping other pcs in LAN.

On Sun, 27 Apr 2025 13:57:55 + mailinglists.accustom...@aleeas.com wrote: > Sorry I didn't mentioned output in my previous mail. This is output I > get when I ping other machine: > > ping: [hostname].local: Name or service not known. where [hostname] > is a placeholder.

Re: Not able to ping other pcs in LAN.

Hi, On Sun, Apr 27, 2025 at 10:09:34AM -0400, Eben King wrote: > On 4/27/25 09:57, mailinglists.accustom...@aleeas.com wrote: > > ping: [hostname].local: Name or service not known. where [hostname] is a > > placeholder. > > Is [hostname].local in /etc/hosts or otherwise f

Re: Not able to ping other pcs in LAN.

On 4/27/25 09:57, mailinglists.accustom...@aleeas.com wrote: Hi, Sorry I didn't mentioned output in my previous mail. This is output I get when I ping other machine: ping: [hostname].local: Name or service not known. where [hostname] is a placeholder. Is [hostname].local in /etc/

Re: Not able to ping other pcs in LAN.

Hi, Sorry I didn't mentioned output in my previous mail. This is output I get when I ping other machine: ping: [hostname].local: Name or service not known. where [hostname] is a placeholder. Thanks. On Sunday, Andy Smith - a...@strugglers.net wrote: > Hi, > > On Sun, Apr 27,

Re: Not able to ping other pcs in LAN.

; > > Sorry I didn't mentioned output in my previous mail. This is output I get > > when I ping other machine: > > > > ping: [hostname].local: Name or service not known. where [hostname] is a > > placeholder. > > > Is [hostname].local in /etc/hosts or otherwise findable by DNS?

Re: Not able to ping other pcs in LAN.

Hi, On Sun, Apr 27, 2025 at 11:24:25AM +, mailinglists.accustom...@aleeas.com wrote: > my issue is before installing debian I was able to ping me other > machine using ```ping hostname.local```, but after installing debian > 12 I am not able to do that. Nowhere in your email have

Not able to ping other pcs in LAN.

Hi all, I recently installed Debian on my old desktop, before this it was running Ubuntu. So my issue is before installing debian I was able to ping me other machine using ```ping hostname.local```, but after installing debian 12 I am not able to do that. I am not expert in computer so kindly

Re: ssh/ping only works to some systems, not including mine unfortunately

On Wed, Jan 22, 2025 at 8:52 AM Greg Wooledge wrote: > On Wed, Jan 22, 2025 at 13:29:41 +, Chris Green wrote: > > I have a remote headless system (running bullseye, will be updating to > > bookworm when I'm next there) that can connect to some systems using > > ssh but not to others (to which

Re: ssh/ping only works to some systems, not including mine unfortunately

o which I can connect from everywhere else). > > > > It also can't ping the systems which it can't connect ssh to. > > > > I can't see any pattern in the systems to which it can connect or > > those which it can't connect to. It's connected via 4

Re: ssh/ping only works to some systems, not including mine unfortunately

an connect from everywhere else). > > What *actually* happens when you try? Show us the command you're > running and its full output. > Absolutely nothing until ssh times out, ping just pings away and reports 100% packet loss when I kill it. > If you need more details, try add

Re: ssh/ping only works to some systems, not including mine unfortunately

On Wed, Jan 22, 2025 at 09:13:35AM -0500, Greg Wooledge wrote: > On Wed, Jan 22, 2025 at 14:56:54 +0100, to...@tuxteam.de wrote: > > Yes, that would be totally useful. As has been stated in this > > list last days, ping actually does two things for you: > > > > - resol

Re: ssh/ping only works to some systems, not including mine unfortunately

On Wed, Jan 22, 2025 at 14:56:54 +0100, to...@tuxteam.de wrote: > Yes, that would be totally useful. As has been stated in this > list last days, ping actually does two things for you: > > - resolve the host's name to an IP address > - check connectivity to that host Wel

Re: ssh/ping only works to some systems, not including mine unfortunately

> It also can't ping the systems which it can't connect ssh to. > > I can't see any pattern in the systems to which it can connect or > those which it can't connect to. It's connected via 4G so it's > CGNATted. I connect to it (using ssh) via a rem

Re: ssh/ping only works to some systems, not including mine unfortunately

> ssh but not to others (to which I can connect from everywhere else). > > What *actually* happens when you try? Show us the command you're > running and its full output. > > If you need more details, try adding the -v option when you ssh. > > > It also can'

Re: ssh/ping only works to some systems, not including mine unfortunately

ually* happens when you try? Show us the command you're running and its full output. If you need more details, try adding the -v option when you ssh. > It also can't ping the systems which it can't connect ssh to. Again, seeing the *error message* from ping would be helpful.

ssh/ping only works to some systems, not including mine unfortunately

I have a remote headless system (running bullseye, will be updating to bookworm when I'm next there) that can connect to some systems using ssh but not to others (to which I can connect from everywhere else). It also can't ping the systems which it can't connect ssh to. I can&#x

Re: Temporary failure in name resolution error when I try to ping Debian 12 / DomU running on top of the Devuan 5 host os / Dom0

; default qlen 1000 >link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever >inet6 ::1/128 scope host noprefixroute > valid_lft forever preferred_lft forever > > 2: sit0@NONE: mtu 1480 qdisc noop state DOWN group default qlen > 1000 >link/sit 0.0.0.0 brd 0.0.0.0 > > 3: enX0: mtu 1500 qdisc > pfifo_fast state UP group default > qlen 1000 >link/ether 00:16:3e:12:34:56 brd ff:ff:ff:ff:ff:ff >inet 192.168.1.10/24 brd 192.168.1.255 scope global enX0 > valid_lft forever preferred_lft forever >inet6 fe80::216:3eff:fe12:3456/64 scope link > valid_lft forever preferred_lft forever > > root@bookworm:~# ping google.it > ping: google.it: Temporary failure in name resolution > > > Where can be the error ? thanks. > > -- > Mario.

Re: Temporary failure in name resolution error when I try to ping Debian 12 / DomU running on top of the Devuan 5 host os / Dom0

quot;Successful vif-route ${command} for ${dev}." >> if [ "${command}" = "online" ] >> then >> success >> fi >> >> >> B) on the guest os (Debian 12) >> >> >> /etc/network/interfaces : >> >> source

Re: Temporary failure in name resolution error when I try to ping Debian 12 / DomU running on top of the Devuan 5 host os / Dom0

  link/ether 00:16:3e:12:34:56 brd ff:ff:ff:ff:ff:ff    inet 192.168.1.10/24 <http://192.168.1.10/24> brd 192.168.1.255 scope global enX0   valid_lft forever preferred_lft forever    inet6 fe80::216:3eff:fe12:3456/64 scope link   valid_lft forever preferred_lft forever root@book

Re: Temporary failure in name resolution error when I try to ping Debian 12 / DomU running on top of the Devuan 5 host os / Dom0

; > > this is what happens within the guest os (Debian 12) : > > > root@bookworm:~# ifup enX0 > > root@bookworm:~# ip a > > 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group > default qlen 1000 >link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 >inet 127.0.0.1/8 scope host lo > valid_lft forever preferred_lft forever >inet6 ::1/128 scope host noprefixroute > valid_lft forever preferred_lft forever > > 2: sit0@NONE: mtu 1480 qdisc noop state DOWN group default qlen > 1000 >link/sit 0.0.0.0 brd 0.0.0.0 > > 3: enX0: mtu 1500 qdisc > pfifo_fast state UP group default > qlen 1000 >link/ether 00:16:3e:12:34:56 brd ff:ff:ff:ff:ff:ff >inet 192.168.1.10/24 brd 192.168.1.255 scope global enX0 > valid_lft forever preferred_lft forever >inet6 fe80::216:3eff:fe12:3456/64 scope link > valid_lft forever preferred_lft forever > > root@bookworm:~# ping google.it > ping: google.it: Temporary failure in name resolution > > > Where can be the error ? thanks. > > -- > Mario. > -- Mario.

Temporary failure in name resolution error when I try to ping Debian 12 / DomU running on top of the Devuan 5 host os / Dom0

e:12:34:56 brd ff:ff:ff:ff:ff:ff inet 192.168.1.10/24 brd 192.168.1.255 scope global enX0 valid_lft forever preferred_lft forever inet6 fe80::216:3eff:fe12:3456/64 scope link valid_lft forever preferred_lft forever root@bookworm:~# ping google.it ping: google.it: Temporary failure in name resolution Where can be the error ? thanks. -- Mario.

Re: why would ping and traceroute give you different IP addresses?

On Tue, Aug 15, 2023 at 05:02:49AM +, Albretch Mueller wrote: > site="download.gluonhq.com" > date > time ping "${site}" -c 4 > time traceroute "${site}" > > $ site="download.gluonhq.com" > date > time ping "${site}" -c

why would ping and traceroute give you different IP addresses?

site="download.gluonhq.com" date time ping "${site}" -c 4 time traceroute "${site}" $ site="download.gluonhq.com" date time ping "${site}" -c 4 time traceroute "${site}" Mon 14 Aug 2023 11:54:19 PM UTC PING s3-website.us-east-1.amazonaw

Re: besides ping/nslookup, any other tools to resolve a hostname?

Hi, I just launched an ubuntu container in that namespace and installed dnsutils/iputils-ping to resolve the hostname issue. Thank you. On Sat, Mar 4, 2023 at 1:11 PM Rodrigo Cunha wrote: > I have bitnami/mysql container (debian OS) running on kubernetes. >> This container

Re: besides ping/nslookup, any other tools to resolve a hostname?

Greg Wooledge (12023-03-03): > Dedicated lookup tools: > > getent hosts > host > dnsqr It is important to know that host and dnsqr do actual DNS requests, and therefore ignore local configuration about other means of resolving hosts, including /etc/hosts. getent hosts is the dedicated command, t

Re: besides ping/nslookup, any other tools to resolve a hostname?

> > I have bitnami/mysql container (debian OS) running on kubernetes. > This container seems too restricted for system software, these following > commands are removed: > > sudo (so I can't su to root for apt) > ping > dig > nslookup > net-tools > It is a g

Re: besides ping/nslookup, any other tools to resolve a hostname?

On 04/03/2023 07:53, Ken Young wrote: Do you know any other way to resolve a hostname by manual  on this container? systemd-resolve However I am unsure concerning k8s containers. Some interpreters: python3 -c 'import socket as s, sys; print(s.gethostbyname(sys.argv[1]))' debian.net

Re: besides ping/nslookup, any other tools to resolve a hostname?

On Sat, Mar 04, 2023 at 08:53:39AM +0800, Ken Young wrote: > ping > dig > nslookup > net-tools > > Do you know any other way to resolve a hostname by manual on this > container? Dedicated lookup tools: getent hosts host dnsqr Utilities that resolve hostnames as a side ef

besides ping/nslookup, any other tools to resolve a hostname?

Hello, I have bitnami/mysql container (debian OS) running on kubernetes. This container seems too restricted for system software, these following commands are removed: sudo (so I can't su to root for apt) ping dig nslookup net-tools Do you know any other way to resolve a hostname by manua

Re: ping

t; root@joule:/home/root# /bin/ping -c 3 192.168.0.12 > > > > PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data. > > > > 64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms > > > > 64 bytes from 192.168.0.12: icmp_seq=2 ttl=64 time=0.114 ms &

Re: ping

On Sun, 13 Nov 2022, Greg Wooledge wrote: unicorn:~$ command -v ls ls But sure, the OP could provide the output of "command -v ping" in addition to "type ping". It couldn't hurt. command -V ping

Re: ping

On Sun, Nov 13, 2022 at 10:24:13PM -0500, Jeffrey Walton wrote: > On Sun, Nov 13, 2022 at 3:54 PM Klaus Singvogel > wrote: > > > > pe...@easthope.ca wrote: > > > root@joule:/home/root# /bin/ping -c 3 192.168.0.12 > > > PING 192.168.0.12 (192.168.0.12) 56(84

Re: ping

On Sun, Nov 13, 2022 at 3:54 PM Klaus Singvogel wrote: > > pe...@easthope.ca wrote: > > root@joule:/home/root# /bin/ping -c 3 192.168.0.12 > > PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data. > > 64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms > &

Re: ping

On Sun, Nov 13, 2022 at 09:05:03PM -0600, David Wright wrote: > On Sun 13 Nov 2022 at 14:50:58 (+), Andrew M.A. Cater wrote: > > On Sun, Nov 13, 2022 at 06:04:51AM -0800, pe...@easthope.ca wrote: > > > root@joule:/home/root# /bin/ping -c 3 192.168.0.12 > > > PING

Re: ping

On Sun 13 Nov 2022 at 14:50:58 (+), Andrew M.A. Cater wrote: > On Sun, Nov 13, 2022 at 06:04:51AM -0800, pe...@easthope.ca wrote: > > root@joule:/home/root# /bin/ping -c 3 192.168.0.12 > > PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data. > > 64 bytes from 192.168.0.

Re: ping

pe...@easthope.ca wrote: > root@joule:/home/root# /bin/ping -c 3 192.168.0.12 > PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data. > 64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms > 64 bytes from 192.168.0.12: icmp_seq=2 ttl=64 time=0.114 ms > 64 bytes from 192.168

Re: ping

On Sun, Nov 13, 2022 at 06:04:51AM -0800, pe...@easthope.ca wrote: > root@joule:/home/root# /bin/ping -c 3 192.168.0.12 > PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data. > 64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms > 64 bytes from 192.168.0.12: icmp_seq=2 ttl=6

Re: ping

On Sun, 13 Nov 2022 06:13:38 -0800 pe...@easthope.ca wrote: > root@joule:/home/root# /bin/ping -c 3 192.168.0.12 > PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data. > 64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms > 64 bytes from 192.168.0.12: icmp_seq=2 ttl=64 t

Re: ping

On 11/13/22 06:13, pe...@easthope.ca wrote: root@joule:/home/root# /bin/ping -c 3 192.168.0.12 PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data. 64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms 64 bytes from 192.168.0.12: icmp_seq=2 ttl=64 time=0.114 ms 64 bytes from

Re: ping

On 11/13/22 06:50, Andrew M.A. Cater wrote: On Sun, Nov 13, 2022 at 06:04:51AM -0800, pe...@easthope.ca wrote: root@joule:/home/root# /bin/ping -c 3 192.168.0.12 PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data. 64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms 64 bytes from

ping

root@joule:/home/root# /bin/ping -c 3 192.168.0.12 PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data. 64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms 64 bytes from 192.168.0.12: icmp_seq=2 ttl=64 time=0.114 ms 64 bytes from 192.168.0.12: icmp_seq=3 ttl=64 time=0.113 ms

Re: ping

On Sun, Nov 13, 2022 at 06:04:51AM -0800, pe...@easthope.ca wrote: > root@joule:/home/root# /bin/ping -c 3 192.168.0.12 > PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data. > 64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms > 64 bytes from 192.168.0.12: icmp_seq=2 ttl=6

ping

root@joule:/home/root# /bin/ping -c 3 192.168.0.12 PING 192.168.0.12 (192.168.0.12) 56(84) bytes of data. 64 bytes from 192.168.0.12: icmp_seq=1 ttl=64 time=0.079 ms 64 bytes from 192.168.0.12: icmp_seq=2 ttl=64 time=0.114 ms 64 bytes from 192.168.0.12: icmp_seq=3 ttl=64 time=0.113 ms

Re: QEMU guests can ping but can't access host

On Sat, 04 Sep 2021 18:08:18 -0500 "David Palacio" wrote: > I have compared my previous install nft ruleset and installed > packages list with the current install and found that firewalld > wasn't installed in the working system but ufw was. The nft ruleset > was nearly identical save for the mis

Re: QEMU guests can ping but can't access host

using to try to contact the host? > > > > I noticed the problem first with Windows Explorer to access the samba > > share. It simply timesout after a minute or two. Then I have tried > > ping and a browser. Pinging the host works and the host responds. > > Then I use

Re: QEMU guests can ping but can't access host

K, then that's not the issue. > > What program are you using to try to contact the host? > > I noticed the problem first with Windows Explorer to access the samba > share. It simply timesout after a minute or two. Then I have tried > ping and a browser. Pinging the host wor

Re: QEMU guests can ping but can't access host

s 10 QEMU guest with access > > to the host Samba shares in a previous Debian testing install. I > > copied the Windows 10 disk image over to the new Debian install and > > set it up to run again but it no longer could connect to the host. It > > can ping it and the host r

Re: QEMU guests can ping but can't access host

g install. I > copied the Windows 10 disk image over to the new Debian install and > set it up to run again but it no longer could connect to the host. It > can ping it and the host responds to the ping but any access attempt > to the host on a TCP port is dropped. This too happens to an

QEMU guests can ping but can't access host

again but it no longer could connect to the host. It can ping it and the host responds to the ping but any access attempt to the host on a TCP port is dropped. This too happens to any new virtual machine I create from scratch, including Linux VMs. I have no idea what has changed on the host. I

Re: ping gateway ok, ping any other local network address fails

rudu writes: > > To configure the printer, I first have to be able to ping it on the > local network, which every over computer can do. So all other peers on the LAN can get to the printer. > And they can print all right, so this desktop must have some network > misconfiguration

Re: ping gateway ok, ping any other local network address fails

On 4/9/21, rudu wrote: > > To configure the printer, I first have to be able to ping it on the > local network, which every over computer can do. > And they can print all right, so this desktop must have some network > misconfiguration of some sort, I guess ... > It seems l

Re: ping gateway ok, ping any other local network address fails

On 09.04.2021 21:37, deloptes wrote: Alexander V. Makartsev wrote: I don't see any reason why your computer could not ping the printer, since you can ping gateway IP and access the Internet from it. I suspect printer's IP address has changed somehow, or it is in powered off s

Re: ping gateway ok, ping any other local network address fails

On Vi, 09 apr 21, 11:41:56, rudu wrote: > > I paste here a few commands I passed when remotely connected to the > problematic machine (sorry for the french locale). You can always prepend 'LANG=C.UTF-8' to get the output in English. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebian

Re: ping gateway ok, ping any other local network address fails

On 2021-04-09 10:41, rudu wrote: Hi, First, I tried to understand why a single machine among others couldn't print on the local printer. So I tried to ping the printer and it failed. The machine could nevertheless surf the web with no problem ... I paste here a few commands I passed

Re: ping gateway ok, ping any other local network address fails

Alexander V. Makartsev wrote: > I don't see any reason why your computer could not ping the printer, > since you can ping gateway IP and access the Internet from it. > I suspect printer's IP address has changed somehow, or it is in powered > off state (some printers can po

Re: ping gateway ok, ping any other local network address fails

On 09.04.2021 19:09, rudu wrote: Le 09/04/2021 à 12:08, Alexander V. Makartsev a écrit : On 09.04.2021 14:41, rudu wrote: Hi, First, I tried to understand why a single machine among others couldn't print on the local printer. So I tried to ping the printer and it failed. The machine

Re: ping gateway ok, ping any other local network address fails

Le 09/04/2021 à 12:08, Alexander V. Makartsev a écrit : On 09.04.2021 14:41, rudu wrote: Hi, First, I tried to understand why a single machine among others couldn't print on the local printer. So I tried to ping the printer and it failed. The machine could nevertheless surf the web wi

Re: ping gateway ok, ping any other local network address fails

On Fri, Apr 09, 2021 at 11:41:56AM +0200, rudu wrote: > Hi, > > First, I tried to understand why a single machine among others couldn't > print on the local printer. > So I tried to ping the printer and it failed. > The machine could nevertheless surf the web with no proble

Re: ping gateway ok, ping any other local network address fails

On 09.04.2021 14:41, rudu wrote: Hi, First, I tried to understand why a single machine among others couldn't print on the local printer. So I tried to ping the printer and it failed. The machine could nevertheless surf the web with no problem ... I paste here a few commands I passed

ping gateway ok, ping any other local network address fails

Hi, First, I tried to understand why a single machine among others couldn't print on the local printer. So I tried to ping the printer and it failed. The machine could nevertheless surf the web with no problem ... I paste here a few commands I passed when remotely connected t

Router Can't ping instance

Hi, Recently I created debian 9.9 image in the Ubuntu openstack and I was able to create instance from the image.I assigned floating ip to the interface.I tried to ping floating ip from the router.It is unreachable.I can ping external/internal gateway from the router.It perfectly works on the

Re: systemd-networkd, bridge and containers: unable to ping host from guest

Hi. On Thu, Jul 11, 2019 at 05:37:43PM +0200, lanquil wrote: > On Thu 11 Jul 2019 at 16:51:50 +0200, john doe wrote: > > > > If you can, I would turn off iptables to see if iptables is the culprit. > > Ok, I have nftables.service active and stopping it I'm abl

Re: systemd-networkd, bridge and containers: unable to ping host from guest

On Thu 11 Jul 2019 at 16:51:50 +0200, john doe wrote: > > If you can, I would turn off iptables to see if iptables is the culprit. Ok, I have nftables.service active and stopping it I'm able to ping the host from the guest. So this was the problem. Thank you very much =) If I remem

Re: systemd-networkd, bridge and containers: unable to ping host from guest

Hi. On Thu, Jul 11, 2019 at 03:29:57PM +0200, lanquil wrote: > The problem I'm encountering is that in all guests (Debian and > Windows, DHCP or static IP configurations) I'm never able to ping the > host system. And the "tcpdump -pni br0 icmp" shows us wha

Re: systemd-networkd, bridge and containers: unable to ping host from guest

; qemu/virt-manager (Debian and Windows10 guest). > > The problem I'm encountering is that in all guests (Debian and Windows, DHCP > or static IP configurations) I'm never able to ping the host system. >From > the host I'm instead able to ping the guest. > In th

systemd-networkd, bridge and containers: unable to ping host from guest

ntering is that in all guests (Debian and Windows, DHCP or static IP configurations) I'm never able to ping the host system. From the host I'm instead able to ping the guest. In the guests everything else seems to work and I'm able to reach the internet as expected. Can someone k

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On Vi, 31 mai 19, 08:51:20, Greg Wooledge wrote: > On Fri, May 31, 2019 at 11:47:26AM +0200, Pascal Hambourg wrote: > > > https://wiki.debian.org/MergedUsr > > > > The wiki says this page does not exist yet. > > It's actually . Right, thanks (again) Greg for co

Re: Gmail problems (was Re: Ping as normal user)

On Fri 31 May 2019 at 14:33:42 +0100, mick crane wrote: > On 2019-05-31 14:01, rhkra...@gmail.com wrote: > > I guess I have to learn more about google > > mail, maybe either disabling their spam filter, or deciding to switch to > > an > > email provider (ideally free or cheap) who doesn't filter e

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

Hello, On Fri, May 31, 2019 at 08:48:36AM -0500, Jason wrote: > On Wed, May 29, 2019 at 11:46:50PM +, Andy Smith wrote: > > How did you install this system? […] > > One other person in this thread said they used (a script which > > ultimately uses) debootstrap. > > This system was installed

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On Wed, May 29, 2019 at 11:46:50PM +, Andy Smith wrote: > Hi Jason, > > On Wed, May 29, 2019 at 04:18:51PM -0500, Jason wrote: > > On Mon, May 27, 2019 at 08:12:32AM +0300, Andrei POPESCU wrote: > > > While I didn't mention it in this thread, ping had i

Re: Gmail problems (was Re: Ping as normal user)

On 2019-05-31 14:01, rhkra...@gmail.com wrote: I guess I have to learn more about google mail, maybe either disabling their spam filter, or deciding to switch to an email provider (ideally free or cheap) who doesn't filter email for me. (I guess when others mark something as spam, at least som

Gmail problems (was Re: Ping as normal user)

On Friday, May 31, 2019 07:26:54 AM Pascal Hambourg wrote: > Le 31/05/2019 à 13:16, rhkra...@gmail.com a écrit : > > I wanted to learn at least a little more about that, starting by looking > > back at the original post that mentioned that. I looked back about 10 > > posts but couldn't find it --

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On Fri, May 31, 2019 at 11:47:26AM +0200, Pascal Hambourg wrote: > > https://wiki.debian.org/MergedUsr > > The wiki says this page does not exist yet. It's actually .

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

t;problematic" package got that Important priority > already. A potential pitfall is closed. The priority in debian/control (and thus .dsc) is scheduled on salsa to be lowered to "optional" by the next package release. Whatever, the priority is not the problem with security. The lac

Re: Ping as normal user

Le 31/05/2019 à 13:16, rhkra...@gmail.com a écrit : On Thursday, May 30, 2019 10:55:57 PM Stefan Monnier wrote: $ getcap /bin/ping /bin/ping = cap_net_raw+ep I wanted to learn at least a little more about that, starting by looking back at the original post that mentioned that. I looked back

Re: Ping as normal user

On Thursday, May 30, 2019 10:55:57 PM Stefan Monnier wrote: > > $ getcap /bin/ping > > /bin/ping = cap_net_raw+ep I wanted to learn at least a little more about that, starting by looking back at the original post that mentioned that. I looked back about 10 posts but couldn'

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

On Fri, May 31, 2019 at 12:09:19PM +0200, Thomas Schmitt wrote: > > Not every filesystem supported by Debian > > implements extended attributes needed for capabilities. > > Off the top of my head it's NFS and JFFS2. > > It is about the filesystem which holds the /bin directory. I would deem it > e

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

because another higher-priority package depends on it; instead, the tools used to construct Debian installations will correctly handle package dependencies. In particular, this means that C-like libraries will almost never have a priority above optional [...]" The issue of incapable sy

Re: Ping as normal user (Was: Why /usr/sbin is not in my root $PATH ?)

Le 31/05/2019 à 08:38, Andrei POPESCU a écrit : On Mi, 29 mai 19, 23:29:21, Gene Heskett wrote: the default $PATH the installer sets up for $users, apparently does not include any of the sbin's, only /usr/bin and /bin. I've been fixing that for several generations of debian installs. It won't

  1   2   3   4   5   6   7   8   9   10   >