Re: Image burn programs, Was: What is the purpose of mDNS

On 8/6/24 05:07, Thomas Schmitt wrote: Hi, Gene Heskett wrote: balenaetcher is purported to be smart enough to write an .iso and make it bootable. But no surprise, I dl the latest version and run it, select the iso file and it refuses to proceed to selecting the target device to write it to.

Image burn programs, Was: What is the purpose of mDNS

Hi, Gene Heskett wrote: > balenaetcher is purported to be smart enough to write an .iso and make it > bootable. But no surprise, I dl the latest version and run it, select the > iso file and it refuses to proceed to selecting the target device to write > it to. Maybe it thinks too much over the e

Re: What is the purpose of mDNS

On 8/6/24 02:04, to...@tuxteam.de wrote: On Mon, Aug 05, 2024 at 11:49:37PM -0500, David Wright wrote: On Sat 03 Aug 2024 at 11:26:38 (+0200), to...@tuxteam.de wrote: [...] It is part of Microsoft's promise that anyone can be sysadmin [...] Isn't that what modern networking is striving t

Re: dot internal and mDNS

On 5 Aug 2024 23:51 -0500, from deb...@lionunicorn.co.uk (David Wright): > Possibly because people aren't warned against using it unless they're > on a network that is already using it for Microsoft servers. It would > be simple to add such a warning to the screen below, and perhaps some > advice o

Re: Internet facing Firewalls mDNS UPnP SMB

On Tue, 06 Aug 2024 09:44:32 +1000 George at Clug wrote: > > (I do recall being taught programming using machine code, once I > reached an environment that used assembler, I only used machine code > for debugging. At that time I was also introduced to programming > using BASIC via punch cards.

Re: Internet facing Firewalls mDNS UPnP SMB

On 2024-08-06, George at Clug wrote: > To disable port forwarding would this be a better method? "ceinture et bretelles" (I let you translate) > # echo 0 > /proc/sys/net/ipv4/ip_forward > # cat /etc/sysctl.conf > # Uncomment the next line to enable packet forwarding for IPv4 > #net.ipv4.ip_forwa

Re: Internet facing Firewalls mDNS UPnP SMB

On 8/6/24 01:47, George at Clug wrote: On Monday, 05-08-2024 at 22:25 john doe wrote: On 8/5/24 12:50, George at Clug wrote: On Monday, 05-08-2024 at 17:25 Michel Verdier wrote: On 2024-08-04, George at Clug wrote: YOu realy need to be intimate with nftables, you might want to consider

Re: What is the purpose of mDNS

On Mon, Aug 05, 2024 at 11:49:37PM -0500, David Wright wrote: > On Sat 03 Aug 2024 at 11:26:38 (+0200), to...@tuxteam.de wrote: [...] > > It is part of Microsoft's promise that anyone can be sysadmin [...] > Isn't that what modern networking is striving to attain? Whoever "modern networking" i

Re: dot internal and mDNS

e.arpa was defined by IANA in 2018. If they go ahead with > .internal then I can only imagine it will be in addition to, not > instead of, home.arpa. > > > How could this affect mDNS and the use of .local? > > It won't. mDNS will continue using .local. > > If you u

Re: What is the purpose of mDNS

On Sat 03 Aug 2024 at 11:26:38 (+0200), to...@tuxteam.de wrote: > On Sat, Aug 03, 2024 at 06:56:42PM +1000, George at Clug wrote: > > What is the purpose of mDNS ?  > > > >  It seems to be for multicast?   > > It is not /for/ multicast IP, it /uses/ multicast for name

Re: Internet facing Firewalls mDNS UPnP SMB

On 6/8/24 08:05, George at Clug wrote: Is it possible to be aware of all the ports required by systems/services like "AWS / Cloudflare / etc", such that it is possible to ensure any firewalls that are put in place do not inhibit the features of these systems? In AWS you have a Virtual Priv

Re: Internet facing Firewalls mDNS UPnP SMB

On Monday, 05-08-2024 at 23:27 Dan Purgert wrote: > On Aug 04, 2024, George at Clug wrote: > > > > > > On Sunday, 04-08-2024 at 16:15 john doe wrote: > > > On 8/4/24 06:48, jeremy ardley wrote: > > > > > > > > On 4/08/2024 12:26 pm, George at Clug wrote: > > > >> > > > >> If I go to the local

Re: Internet facing Firewalls mDNS UPnP SMB

On Tue, 06 Aug 2024 09:44:32 +1000 George at Clug wrote: > This morning, after thinking on these things I realise I am wrong. > > I am showing both my ignorance and my stupidity. > > "Times have changed", "That was then, this is now". My compliments on your willingness to do so. It is not ea

Re: Internet facing Firewalls mDNS UPnP SMB

On Monday, 05-08-2024 at 22:25 john doe wrote: > On 8/5/24 12:50, George at Clug wrote: > > > > > > On Monday, 05-08-2024 at 17:25 Michel Verdier wrote: > >> On 2024-08-04, George at Clug wrote: > >> > >>> I think I finally have success (had to fix way too many typos). > >>> > >>> Please review,

Re: Internet facing Firewalls mDNS UPnP SMB

On Tuesday, 06-08-2024 at 04:12 Charles Curley wrote: > On Tue, 06 Aug 2024 01:12:08 +1000 > George at Clug wrote: > > > It would be nice if systems were not so complex that they required > > frontends to be usable. > > Perhaps it would be nice. But that's not the way of the world. I wrote >

Re: Internet facing Firewalls mDNS UPnP SMB

On Tue, 06 Aug 2024 01:12:08 +1000 George at Clug wrote: > It would be nice if systems were not so complex that they required > frontends to be usable. Perhaps it would be nice. But that's not the way of the world. I wrote 6502 assembly code and hand-assembled it way back when. I was very glad t

Re: Internet facing Firewalls mDNS UPnP SMB

On Monday, 05-08-2024 at 21:52 Michel Verdier wrote: > On 2024-08-05, George at Clug wrote: > > > Down below is the output of the translation commands for my Iptables > > commands. Interesting but again, I will need to learn what this means, > > it does not look self explanatory. But hopefully

Re: Internet facing Firewalls mDNS UPnP SMB

On Monday, 05-08-2024 at 22:25 john doe wrote: > On 8/5/24 12:50, George at Clug wrote: > > > > > > On Monday, 05-08-2024 at 17:25 Michel Verdier wrote: > >> On 2024-08-04, George at Clug wrote: > >> > >>> I think I finally have success (had to fix way too many typos). > >>> > >>> Please review,

Re: Internet facing Firewalls mDNS UPnP SMB

On Monday, 05-08-2024 at 23:27 Dan Purgert wrote: > On Aug 04, 2024, George at Clug wrote: > > > > > > On Sunday, 04-08-2024 at 16:15 john doe wrote: > > > On 8/4/24 06:48, jeremy ardley wrote: > > > > > > > > On 4/08/2024 12:26 pm, George at Clug wrote: > > > >> > > > >> If I go to the local

Re: Internet facing Firewalls mDNS UPnP SMB

On Aug 04, 2024, George at Clug wrote: > > > On Sunday, 04-08-2024 at 16:15 john doe wrote: > > On 8/4/24 06:48, jeremy ardley wrote: > > > > > > On 4/08/2024 12:26 pm, George at Clug wrote: > > >> > > >> If I go to the local coffee shop and connect my laptop to their WiFi, > > >> which incoming

Re: Internet facing Firewalls mDNS UPnP SMB

On 8/5/24 12:50, George at Clug wrote: On Monday, 05-08-2024 at 17:25 Michel Verdier wrote: On 2024-08-04, George at Clug wrote: I think I finally have success (had to fix way too many typos). Please review, and please comment if it can be improved. Don't fix typo and instead rewrite your

VM, wifi, NAT (was: Re: Internet facing Firewalls mDNS UPnP SMB)

On 05/08/2024 17:50, George at Clug wrote: I am also a bit concerned about the statement "table ip nat", I do not want [e.g. need] any Network Address Translation occurring. Re: VirtualBox (VB) and Window

Re: Internet facing Firewalls mDNS UPnP SMB

On 2024-08-05, George at Clug wrote: > Down below is the output of the translation commands for my Iptables > commands. Interesting but again, I will need to learn what this means, > it does not look self explanatory. But hopefully, like everything > computer related, it is usually not that compl

Re: Internet facing Firewalls mDNS UPnP SMB

On Monday, 05-08-2024 at 17:25 Michel Verdier wrote: > On 2024-08-04, George at Clug wrote: > > > I think I finally have success (had to fix way too many typos). > > > > Please review, and please comment if it can be improved. > > Don't fix typo and instead rewrite your rules with nftables > h

Re: Internet facing Firewalls mDNS UPnP SMB

On 2024-08-04, George at Clug wrote: > I think I finally have success (had to fix way too many typos). > > Please review, and please comment if it can be improved. Don't fix typo and instead rewrite your rules with nftables https://wiki.nftables.org/wiki-nftables/index.php/Moving_from_iptables_to

Re: Internet facing Firewalls mDNS UPnP SMB

On 2024-08-04, George at Clug wrote: > I do like the idea of blocking all outbound connections, and only > opening ports that are required for whatever services I want to use. I do the same. > For servers I often do, but for workstations, sadly I am often lazy and > default to allowing all outgo

Re: dot internal and mDNS

George at Clug wrote: > It is not iptables anymore, it is nftables. It is not 'reboot' or 'shutdown > -r now' it is 'systemctl reboot', it is not syslog it is journalctl. iptables still exists, and it calls nftables to do the work underneath. If you are using systemd, it's systemctl reboot,

Re: dot internal and mDNS

On Sunday 04 August 2024 09:54:07 am George at Clug wrote: > > > I have been traumatised by things changing. Just when I think I know > something, someone goes and changes it. > Yeah, I keep seeing things changed to something new, and wonder why the heck I need that... -- Member of the to

Re: dot internal and mDNS

On 5 Aug 2024 00:34 +1000, from c...@goproject.info (George at Clug): >> Standards don't tend to be abolished unless there's a good reason. >> There wasn't a standard before home.arpa. Since 2013 it's been "use >> your own globally unique registered domain, or else use home.arpa". The RFC specifyi

Re: dot internal and mDNS

On 4 Aug 2024 14:35 +0100, from j...@jretrading.com (Joe): > Exactly. I've run a DHCP server since about 2010, and used one of my > own domain names in my network since 2006. Using a domain name that you control has never been problematic. Or, well, for as long as DNS has been a thing at least (pr

Re: dot internal and mDNS

On Monday, 05-08-2024 at 00:19 Andy Smith wrote: > Hi, > > On Sun, Aug 04, 2024 at 11:54:07PM +1000, George at Clug wrote: > > On Sunday, 04-08-2024 at 22:59 Andy Smith wrote: > > > So I want to emphasise again that while standards are useful so > > > we're all on the same page, in this particu

Re: dot internal and mDNS

Hi, On Sun, Aug 04, 2024 at 11:54:07PM +1000, George at Clug wrote: > On Sunday, 04-08-2024 at 22:59 Andy Smith wrote: > > So I want to emphasise again that while standards are useful so > > we're all on the same page, in this particular case it's not a big > > deal, likely nothing terribly bad is

Re: dot internal and mDNS

On Sunday, 04-08-2024 at 22:59 Andy Smith wrote: > Hi, > > On Sat, Aug 03, 2024 at 10:08:55PM +, Andrew M.A. Cater wrote: > > > On 8/3/24 09:00, Andy Smith wrote: > > > > If you use .local for other things it can interfere with mDNS but > > > >

Re: Internet facing Firewalls mDNS UPnP SMB

On Sunday, 04-08-2024 at 18:48 Christofer C. Bell wrote: > On Sun, Aug 4, 2024 at 3:12 AM George at Clug wrote: > > > > > > > On Sunday, 04-08-2024 at 16:15 john doe wrote: > > > On 8/4/24 06:48, jeremy ardley wrote: > > > > > > > > On 4/08/2024 12:26 pm, George at Clug wrote: > > > >> > > > >

Re: dot internal and mDNS

On Sun, 4 Aug 2024 12:59:55 + Andy Smith wrote: > Hi, > > On Sat, Aug 03, 2024 at 10:08:55PM +, Andrew M.A. Cater wrote: > > > On 8/3/24 09:00, Andy Smith wrote: > > > > If you use .local for other things it can interfere with mDNS > > > > but

Re: dot internal and mDNS

Hi, On Sat, Aug 03, 2024 at 10:08:55PM +, Andrew M.A. Cater wrote: > > On 8/3/24 09:00, Andy Smith wrote: > > > If you use .local for other things it can interfere with mDNS but > > > picking almost anything else has very few repercussions (unless you > > &g

Re: Internet facing Firewalls mDNS UPnP SMB

On 4/8/24 16:11, George at Clug wrote: I do like the idea of blocking all outbound connections, and only opening ports that are required for whatever services I want to use. For servers I often do, but for workstations, sadly I am often lazy and default to allowing all outgoing traffic. Let

Re: Internet facing Firewalls mDNS UPnP SMB

On Sun, Aug 4, 2024 at 3:12 AM George at Clug wrote: > > > On Sunday, 04-08-2024 at 16:15 john doe wrote: > > On 8/4/24 06:48, jeremy ardley wrote: > > > > > > On 4/08/2024 12:26 pm, George at Clug wrote: > > >> > > >> If I go to the local coffee shop and connect my laptop to their WiFi, > > >> w

Re: Internet facing Firewalls mDNS UPnP SMB

On Sunday, 04-08-2024 at 16:15 john doe wrote: > On 8/4/24 06:48, jeremy ardley wrote: > > > > On 4/08/2024 12:26 pm, George at Clug wrote: > >> > >> If I go to the local coffee shop and connect my laptop to their WiFi, > >> which incoming and now outgoing ports should I have blocked to ensure >

Re: Internet facing Firewalls mDNS UPnP SMB

On 8/4/24 06:48, jeremy ardley wrote: On 4/08/2024 12:26 pm, George at Clug wrote: If I go to the local coffee shop and connect my laptop to their WiFi, which incoming and now outgoing ports should I have blocked to ensure that no nefarious people are able to communicate with my laptop The r

Re: Internet facing Firewalls mDNS UPnP SMB

you have specific needs to receive multicast (such as mDNS) you need to enable that for each case. - Finally block all other incoming connections.

Internet facing Firewalls mDNS UPnP SMB

​Hi, Thanks to all who have been explaining mDNS nssswitch, etc. I had not realised how 'chatty' our computers have become. If I go to the local coffee shop and connect my laptop to their WiFi, which incoming and now outgoing ports should I have blocked to ensure that no nefarious

Re: dot internal and mDNS

On 8/3/24 18:09, Andrew M.A. Cater wrote: On Sat, Aug 03, 2024 at 04:10:33PM -0400, gene heskett wrote: On 8/3/24 09:00, Andy Smith wrote: Hi, [Very interesting Stuff snipped about ICANN and domain suffixes] If you use .local for other things it can interfere with mDNS but picking almost

Re: dot internal and mDNS

On Sat, Aug 03, 2024 at 04:10:33PM -0400, gene heskett wrote: > On 8/3/24 09:00, Andy Smith wrote: > > Hi, > > [Very interesting Stuff snipped about ICANN and domain suffixes] > > > > If you use .local for other things it can interfere with mDNS but > > picking

Re: dot internal and mDNS

On 3 Aug 2024 22:22 +0100, from mick.cr...@gmail.com (mick.crane): > I was going to change everything yet again to home.arpa but now it might be > .internal? To use .home.arpa is absolutely fine if you don't need (or want) globally unique names. It has been properly assigned specifically for "non-

Re: dot internal and mDNS

ft did suggest .local back in the early 2000s and then go back on that. The RFC for mDNS standardised its use of .local in 2013. Once things end up in some Internet RFC that's a bit more weight than just a vendor suggesting it. Vendors do crazy things, like putting captive portals on the 1.1.1

Re: What is the purpose of mDNS

On 03/08/2024 21:08, Lee wrote: On Sat, Aug 3, 2024 at 6:51 AM George at Clug wrote: Hi, What is the purpose of mDNS ? "zero-configuration networking" seems to be the search term eg -https://en.wikipedia.org/wiki/Bonjour_(software) It seems to be for multicast? no, it _uses_

Re: dot internal and mDNS

On 2024-08-03 19:57, Michael Kjörling wrote: On 3 Aug 2024 12:59 +, from a...@strugglers.net (Andy Smith): I believe ICCAN are moving to possibly replacing .local, .home, .lan, .corp, .mail, .localdomain, (and possibly others) with .internal ? home.arpa was defined by IANA in 2018. If they

Re: dot internal and mDNS

ahead with .internal then I can only imagine it will be in addition to, not instead of, home.arpa. How could this affect mDNS and the use of .local? It won't. mDNS will continue using .local. If you use .local for other things it can interfere with mDNS but picking almost anything else has

Re: What is the purpose of mDNS

On Sat, Aug 3, 2024 at 6:51 AM George at Clug wrote: > > Hi, > > What is the purpose of mDNS ? "zero-configuration networking" seems to be the search term eg - https://en.wikipedia.org/wiki/Bonjour_(software) > It seems to be for multicast? no, it _uses_ multic

Re: dot internal and mDNS

nternal-tld-00.txt .home was _specifically_ for HNCP (see RFC 7788; just as .local is _specifically_ for mDNS) and RFC 7788 was updated by RFC 8375 (the reservation of .home.arpa) to use the more generic .home.arpa as a default. Assuming that there are no late showstoppers for the reservation of .internal, w

Re: dot internal and mDNS

n only imagine it will be in addition to, not instead of, home.arpa. > How could this affect mDNS and the use of .local? It won't. mDNS will continue using .local. If you use .local for other things it can interfere with mDNS but picking almost anything else has very few repercussions (

Re: What is the purpose of mDNS

ally assign themselves an address from 169.254.X.X/16 range (X.X is derived from the MAC address) They then multicast their hostname and IP address to everyone else on the LAN using mDNS. It is not a Microsoft only standard. It is defined in RFC 3927, "Dynamic Configuration of IPv4 Link-Local Add

Re: What is the purpose of mDNS

IPv4 clients will then automatically assign themselves an address from > 169.254.X.X/16 range (X.X is derived from the MAC address) > > They then multicast their hostname and IP address to everyone else on > the LAN using mDNS. > > It is not a Microsoft only standard. It is defined in

Re: dot internal and mDNS

offered as a recognised TLD that is preferred for use. The above domains are not recognised and are seen as potentially dangerous. Hence the proposal The presently recognised non-routable TLDs are .local (special case for mDNS) .localhost (no to be confused with localhost) .invalid .test The

Re: What is the purpose of mDNS

everyone else on the LAN using mDNS. It is not a Microsoft only standard. It is defined in RFC 3927, "Dynamic Configuration of IPv4 Link-Local Addresses." It is used on a wide variety of hosts including Linux.

Re: What is the purpose of mDNS

On Sat, Aug 03, 2024 at 06:56:42PM +1000, George at Clug wrote: > Hi, > > > What is the purpose of mDNS ?  > > >  It seems to be for multicast?   It is not /for/ multicast IP, it /uses/ multicast for name resolution. In a nutshell [1], it sends a "DNS" request t

What is the purpose of mDNS

Hi, What is the purpose of mDNS ?   It seems to be for multicast?   Does that mean its usage would be to say send video to a group of workstations all at the same time?  Like a corporate wide message from the CEO?   What other use?   It does not seem to be a unicast DNS system. That is a

dot internal and mDNS

I believe ICCAN are moving to possibly replacing .local, .home, .lan, .corp, .mail, .localdomain, (and possibly others) with .internal ? How could this affect mDNS and the use of .local? https://www.icann.org/en/public-comment/proceeding/proposed-top-level-domain-string-for-private-use-24-01

Re: MDNS?

On Fri, Feb 24, 2012 at 9:14 AM, Tony van der Hoff wrote: > > Hi, I'm trying to install WINE on my squeeze amd64 system. The configurator > throws up a message box: > >  It appears that libnss-mdns is installed on your system, >  but lib32nss-mdns is not. Please note that W

MDNS?

Hi, I'm trying to install WINE on my squeeze amd64 system. The configurator throws up a message box: It appears that libnss-mdns is installed on your system, but lib32nss-mdns is not. Please note that Wine will not be able to access the Internet unless you either install lib32nss-mdn

Re: mDNS and /etc/nsswitch.conf

Freddy Freeloader wrote: > Joey Hess wrote: > >BTW, this bug only affects system that have "search local" in > >/etc/resolv.conf. This causes mdns to be tried for _every_ dns lookup, > >which is bad. Details at http://bugs.debian.org/392813/ > > > > >

Re: mDNS and /etc/nsswitch.conf

John Hasler wrote: Joey Hess writes: Because you had libnss-mdns installed so apparently want to use it, and the change is not intended to make mdns be used for anything except for .local address resolution. kdnssd, education-standalone, libavahi-compat-libdnssd1, and avahi-daemon

Re: mDNS and /etc/nsswitch.conf

Joey Hess wrote: BTW, this bug only affects system that have "search local" in /etc/resolv.conf. This causes mdns to be tried for _every_ dns lookup, which is bad. Details at http://bugs.debian.org/392813/ Hmmm I don't have that specific line in my /etc/resolv.conf file

Re: mDNS and /etc/nsswitch.conf

Joey Hess writes: > Because you had libnss-mdns installed so apparently want to use it, and > the change is not intended to make mdns be used for anything except for > .local address resolution. kdnssd, education-standalone, libavahi-compat-libdnssd1, and avahi-daemon depend on libnss-m

Re: mDNS and /etc/nsswitch.conf

BTW, this bug only affects system that have "search local" in /etc/resolv.conf. This causes mdns to be tried for _every_ dns lookup, which is bad. Details at http://bugs.debian.org/392813/ -- see shy jo signature.asc Description: Digital signature

Re: mDNS and /etc/nsswitch.conf

Joey Hess wrote: > It would be helpful if you could provide as much information as possible > to [EMAIL PROTECTED] about this, including straces of programs > failing, the versions of all the involved packages, and details about > your dns setup. Also include details of any firewall setup you migh

Re: mDNS and /etc/nsswitch.conf

cess port 5353 at 224.0.0.251, a multicast > address, to resolve url's. > > This turned out to be related to the libnss-mdns package and > modifications made to /etc/nsswitch.conf when it is installed. This > was done without asking me if I wanted to use multicast DNS as the &

mDNS and /etc/nsswitch.conf

icast address, to resolve url's. This turned out to be related to the libnss-mdns package and modifications made to /etc/nsswitch.conf when it is installed. This was done without asking me if I wanted to use multicast DNS as the default protocol for resolving url's during the update.