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
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.
On Mon, Apr 28, 2025 at 10:32:26AM -0400, Lee wrote:
[...]
> > - is trying to resolve via mDNS
>
> How do we know that? Has the OP sent you a private message showing
> the mdns requests going out to the network?
> If no then I would say we don't know if their machine is trying to do
> mdns or
On Mon, Apr 28, 2025 at 12:20 AM tomas wrote:
>
> On Sun, Apr 27, 2025 at 11:36:17PM +0200, Geert Stappers wrote:
> > On Sun, Apr 27, 2025 at 04:28:48PM -0400, Lee wrote:
> > > On Sun, Apr 27, 2025 at 3:33 PM wrote:
>
> [...]
>
> > > > Hope that helps.
> > >
> > > Not particularly.
> > >
> > > Try
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
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 :
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.
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
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
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 debian 12 I am not abl
On Sun, Apr 27, 2025 at 11:36:17PM +0200, Geert Stappers wrote:
> On Sun, Apr 27, 2025 at 04:28:48PM -0400, Lee wrote:
> > On Sun, Apr 27, 2025 at 3:33 PM wrote:
[...]
> > > Hope that helps.
> >
> > Not particularly.
> >
> > Try this:
> >
> > sudo apt install tshark
> > sudo tshark -f 'port 53
On Sun, Apr 27, 2025 at 04:28:48PM -0400, Lee wrote:
> 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
Sad, but True
> > Hope that helps.
>
> Not particularly.
>
> Try this:
>
> sudo a
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 whatever.local
At least for
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, QUERY: 1, AN
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 I
> am not able t
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)
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
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,
Hi,
Here are the output of the cmnds that tomas suggested.
user@localhost:~$ip addr show
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 forev
On Sun, 27 Apr 2025 17:47:19 +0200
wrote:
> 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 pin
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:
> >
> > ping: [hostname].local: Name or
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.
No, no. Please show u
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 findable by DNS?
Okay so
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/hosts or
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, 2025 at 11:24:2
Hi,
No, [hostname].local is not in /etc/hosts, So does in ubuntu machine. As far as
I know avahi should be resolving these.
Thanks
On Sunday, April 27th, Eben King - e...@gmx.us wrote:
>
> On 4/27/25 09:57, mailinglists.accustom...@aleeas.com wrote:
>
> > Hi,
> >
> > Sorry I didn't ment
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 you shown t
27 matches
Mail list logo
