Hi All, I have a problem that has been ongoing since 12.3 with openSUSE not being able to resolve hostnames on LAN. I have this issue at home and at work where I cannot type in the name of a computer or device into Firefox or dolphin, I have to type in the IP. (i.e. https://freenas will not work but https://192.168.0.10 will work). Ubuntu works fine once samba is enabled. I also have samba enabled on openSUSE and it does not work. I have also tried turning off SUSE Firewall and rebooting but still no change. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 17/11/2014 12:10, Paul Groves a écrit :
Hi All,
I have a problem that has been ongoing since 12.3 with openSUSE not being able to resolve hostnames on LAN.
I have this issue at home and at work where I cannot type in the name of a computer or device into Firefox or dolphin, I have to type in the IP. (i.e. https://freenas will not work but https://192.168.0.10 will work).
Ubuntu works fine once samba is enabled. I also have samba enabled on openSUSE and it does not work. I have also tried turning off SUSE Firewall and rebooting but still no change.
try Dolphin or aother apps with smb://, not https jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I have tried that already. smb://freenas does not work smb://192.168.0.10 does
although if I go to network > samba shares > workgroup and click
freenas it works fine and shows the address smb://freenas but if i
click the address bar and hit enter it will not load
On 17 November 2014 12:10, jdd
Le 17/11/2014 12:10, Paul Groves a écrit :
Hi All,
I have a problem that has been ongoing since 12.3 with openSUSE not being able to resolve hostnames on LAN.
I have this issue at home and at work where I cannot type in the name of a computer or device into Firefox or dolphin, I have to type in the IP. (i.e. https://freenas will not work but https://192.168.0.10 will work).
Ubuntu works fine once samba is enabled. I also have samba enabled on openSUSE and it does not work. I have also tried turning off SUSE Firewall and rebooting but still no change.
try Dolphin or aother apps with smb://, not https
jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/17/2014 06:10 AM, Paul Groves wrote:
Hi All,
I have a problem that has been ongoing since 12.3 with openSUSE not being able to resolve hostnames on LAN.
I have this issue at home and at work where I cannot type in the name of a computer or device into Firefox or dolphin, I have to type in the IP. (i.e. https://freenas will not work but https://192.168.0.10 will work).
Ubuntu works fine once samba is enabled. I also have samba enabled on openSUSE and it does not work. I have also tried turning off SUSE Firewall and rebooting but still no change.
Do you have something to provided that, such as a DNS server or hosts file containing the names and addresses? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
If i add the hostnames to YaST > Hostnames and supply the ip address
it works fine. This appears to be default behaviour out of the box
that openSUSE cannot resolve LAN hostnames.
On 17 November 2014 12:48, James Knott
On 11/17/2014 06:10 AM, Paul Groves wrote:
Hi All,
I have a problem that has been ongoing since 12.3 with openSUSE not being able to resolve hostnames on LAN.
I have this issue at home and at work where I cannot type in the name of a computer or device into Firefox or dolphin, I have to type in the IP. (i.e. https://freenas will not work but https://192.168.0.10 will work).
Ubuntu works fine once samba is enabled. I also have samba enabled on openSUSE and it does not work. I have also tried turning off SUSE Firewall and rebooting but still no change.
Do you have something to provided that, such as a DNS server or hosts file containing the names and addresses?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/17/2014 12:24 PM, Paul Groves wrote:
If i add the hostnames to YaST > Hostnames and supply the ip address it works fine. This appears to be default behaviour out of the box that openSUSE cannot resolve LAN hostnames.
Why do you consider that odd? If the information isn't supplied ro the resolver (either from hosts file or from DNS -- see nsswitch.conf(5) -- then how are symbolic names going to be mapped to IP addresses, since IP addresses are the only thing that the network interface understands? The information has to come from somewhere and it can't come from the people who package Suse 'into the box' since they don't know about your, or mine, system and what's on the LAN. The information has to come from somewhere and its up to you to supply it. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/17/2014 12:24 PM, Paul Groves wrote:
If i add the hostnames to YaST > Hostnames and supply the ip address it works fine. This appears to be default behaviour out of the box that openSUSE cannot resolve LAN hostnames.
It can't resolve things it doesn't know about. If you can browse for the server, but not get to it directly with a host name then this is definitely the issue. You need to have some means of mapping host name to IP address. Your choices are DNS server, hosts file, lmhosts file or WINS server. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 11/17/2014 12:24 PM, Paul Groves wrote:
If i add the hostnames to YaST > Hostnames and supply the ip address it works fine. This appears to be default behaviour out of the box that openSUSE cannot resolve LAN hostnames.
Of course openSUSE can use a DNS resolver. It is such a basic necessity, everything would stop if it didn't work.
It can't resolve things it doesn't know about. If you can browse for the server, but not get to it directly with a host name then this is definitely the issue. You need to have some means of mapping host name to IP address. Your choices are DNS server, hosts file, lmhosts file or WINS server.
Not sure about the last two, but otherwise yup. -- Per Jessen, Zürich (7.6°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/17/2014 12:49 PM, Per Jessen wrote:
It can't resolve things it doesn't know about. If you can browse for
the server, but not get to it directly with a host name then this is definitely the issue. You need to have some means of mapping host name to IP address. Your choices are DNS server, hosts file, lmhosts file or WINS server. Not sure about the last two, but otherwise yup.
Yup to the last two as well. http://www.oreilly.com/openbook/samba/book/ch07_03.html -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/17/2014 12:55 PM, James Knott wrote:
On 11/17/2014 12:49 PM, Per Jessen wrote:
It can't resolve things it doesn't know about. If you can browse for
the server, but not get to it directly with a host name then this is definitely the issue. You need to have some means of mapping host name to IP address. Your choices are DNS server, hosts file, lmhosts file or WINS server. Not sure about the last two, but otherwise yup.
Yup to the last two as well. http://www.oreilly.com/openbook/samba/book/ch07_03.html
Also see: /etc/samba/lmhosts /usr/share/man/man5/lmhosts.5.gz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 11/17/2014 12:55 PM, James Knott wrote:
On 11/17/2014 12:49 PM, Per Jessen wrote:
It can't resolve things it doesn't know about. If you can browse for
the server, but not get to it directly with a host name then this is definitely the issue. You need to have some means of mapping host name to IP address. Your choices are DNS server, hosts file, lmhosts file or WINS server. Not sure about the last two, but otherwise yup.
Yup to the last two as well. http://www.oreilly.com/openbook/samba/book/ch07_03.html
Also see: /etc/samba/lmhosts /usr/share/man/man5/lmhosts.5.gz
Seems like lmhosts is only for samba then? Not that I care, just being curious. -- Per Jessen, Zürich (7.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/17/2014 01:16 PM, Per Jessen wrote:
Also see:
/etc/samba/lmhosts /usr/share/man/man5/lmhosts.5.gz Seems like lmhosts is only for samba then? Not that I care, just being curious.
It and WINS actually go back to before TCP/IP became popular. Back then, it was used with NetBIOS on DOS, Windows and OS/2. I came across those settings when I was doing 3rd level OS/2 support at IBM Canada. At that time, local LAN file sharing was not carried on IP. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
James Knott wrote:
On 11/17/2014 01:16 PM, Per Jessen wrote:
Also see:
/etc/samba/lmhosts /usr/share/man/man5/lmhosts.5.gz Seems like lmhosts is only for samba then? Not that I care, just being curious.
It and WINS actually go back to before TCP/IP became popular. Back then, it was used with NetBIOS on DOS, Windows and OS/2. I came across those settings when I was doing 3rd level OS/2 support at IBM Canada. At that time, local LAN file sharing was not carried on IP.
Ah yes, you're right, I forgot about that. lmhosts, that brings back some repres... forgotten memories. /Per -- Per Jessen, Zürich (7.1°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/17/2014 12:24 PM, Paul Groves wrote:
If i add the hostnames to YaST > Hostnames and supply the ip address it works fine.
When you do that, you're writing to the /etc/hosts file. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/17/2014 12:43 PM, James Knott wrote:
On 11/17/2014 12:24 PM, Paul Groves wrote:
If i add the hostnames to YaST > Hostnames and supply the ip address it works fine.
When you do that, you're writing to the /etc/hosts file.
To you and me "that's bleedin' obvious, ha'int it?' But is this another example of Yast obscuring things for the uninitiated? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am Montag, 17. November 2014, 11:10:00 schrieb Paul Groves:
[...] Ubuntu works fine once samba is enabled. [...]
What does "host freenas" say when using Ubuntu? Gruß Jan -- Enough research will tend to support your theory. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
when I use ubuntu, mac os 10.10, and windows 7 and I type
https://freenas or smb://freenas (or with \\ for Windoze)
ftp://freenas or ping freenas it works perfectly fine but not with
openSUSE. I have to type the IP address. As mentioned it is something
I have noticed since 12.3 when I switched to SUSE.
On 17 November 2014 20:38, Jan Ritzerfeld
Am Montag, 17. November 2014, 11:10:00 schrieb Paul Groves:
[...] Ubuntu works fine once samba is enabled. [...]
What does "host freenas" say when using Ubuntu?
Gruß Jan -- Enough research will tend to support your theory.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-17 22:16, Paul Groves wrote:
when I use ubuntu, mac os 10.10, and windows 7 and I type https://freenas or smb://freenas (or with \\ for Windoze) ftp://freenas or ping freenas it works perfectly fine but not with openSUSE. I have to type the IP address. As mentioned it is something I have noticed since 12.3 when I switched to SUSE.
It is a feature. For "names" to be accepted, something has to do the conversion. The standard method is to set up a domain name server (DNS). But not in Windows. It is a feature of Windows networks that you can reach machines by name, automatically apparently. Linux doesn't do the same, but you can configure samba to work similarly. If I recall correctly, this is done with a wins server. Try: wins support = Yes name resolve order = wins lmhosts hosts bcast in "/etc/samba/smb.conf" (unless there is another machine doing it; then use "wins server = ...whatever"). Then, probably, when using samba protocols (smb://, ) names may work. For http, I doubt it. Read this: http://www.oreilly.com/openbook/samba/book/ch07_03.html 7.3 Name Resolution with Samba -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 11/17/2014 10:24 PM, Carlos E. R. wrote:
It is a feature of Windows networks that you can reach machines by name,
It is one of the class of networks where each node broadcasts its name and binding. This is OK for a single LAN segment, but ... Oh, and it's also noisy. As you can imagine. I mean, heck, Ethernet is noisy enough with (r)ARP! (take an unfiltered look with ethershark on a non-switched segment some time) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/17/2014 10:56 PM, Anton Aylward wrote:
It is one of the class of networks where each node broadcasts its name and binding.
Here is a pretty good summary or name Broadcast mode and why its expensive in both network bandwidth and cpu time and not something you want. Better to turn it off and use WINS/DDNS or lmhosts https://www.samba.org/samba/docs/using_samba/ch07.html -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/17/2014 10:56 PM, Anton Aylward wrote:
I mean, heck, Ethernet is noisy enough with (r)ARP!
And there's also STP on other than low end consumer gear. Also router multicasts and more. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/18/2014 02:25 PM, James Knott wrote:
And there's also STP on other than low end consumer gear. Also router multicasts and more.
... which leads me to the question why the router couldn't/doesn't do the name resolution? Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/18/2014 09:52 AM, Bernhard Voelker wrote:
... which leads me to the question why the router couldn't/doesn't do the name resolution?
Does the router have the DNS information about the LAN? Does the router have a 'hosts' table filled in by the net admin giving the name -> ip address mappings? I suspect not. I'll grant you that now that routers have sophisticated micros in them they have a lot of computing power to spare, and i'll grant you that many commercial firewalls are in that boat too and do lots of things not associated with a typical Ranum-era firewall such as deep packet inspection, DLP and more, and could act as a DNS server. I'll even grant you that the home/smb class D-Llink and Linksys routers with wifi capability can do DHCP. But unless someone fill in their tables manually they don't know anything about address mapping. Now if you are using a Linux box loaded up with router software (along with squid, dhcp, possibly LDAP, and more) there's no reason it can't run DNS for the LAN as well. But once again someone has to explicitly fill in the tables for the LAN. Only you can ... No wait, that's forest fires isn't it? Only the network admin can fill in the tables. The IP 'noise I was talking about are a completely different thing from the Microsoft 'hosts' (or SMB hosts) "Broadcasting" their names and addresses to the LAN. ARP is about IP <-> MAC addresses, not names. The router protocols are about IP address routeing, not about names. Only DNS is about names and DNS requires someone to fill in the tables. Oh, and the SMB Broadcast is for a LAN segment only, its not routable. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-18 15:52, Bernhard Voelker wrote:
On 11/18/2014 02:25 PM, James Knott wrote:
And there's also STP on other than low end consumer gear. Also router multicasts and more.
... which leads me to the question why the router couldn't/doesn't do the name resolution?
They might, but they don't. Home class routers don't have a DNS server that you can configure, not that I have seen. They just act as cache for the ISP provided DNS, so that automatic network setup (dhcp) works. That is, they are forced to implement that feature. Configure names somehow is not a feature they are forced to have, and people don't ask for it, as "it works in Windows". Maybe one of the free flashable firmwares out there provides it. Dunno. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 11/18/2014 09:52 AM, Bernhard Voelker wrote:
On 11/18/2014 02:25 PM, James Knott wrote:
And there's also STP on other than low end consumer gear. Also router multicasts and more.
... which leads me to the question why the router couldn't/doesn't do the name resolution?
It could, if it had a DNS server. Commercial grade routers from Cisco, Adtran etc. do, as does my home router/firewall, which is just an old computer running Linux. All it takes to have a DNS server is a Linux box running dnsmasq, which is a caching DNS server. It reads a file, usually /etc/hosts, for local hosts and forwards requests for Internet hosts to the DNS server you normally use. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/18/2014 11:41 AM, James Knott wrote:
On 11/18/2014 09:52 AM, Bernhard Voelker wrote:
On 11/18/2014 02:25 PM, James Knott wrote:
And there's also STP on other than low end consumer gear. Also router multicasts and more.
... which leads me to the question why the router couldn't/doesn't do the name resolution?
It could, if it had a DNS server. Commercial grade routers from Cisco, Adtran etc. do, as does my home router/firewall, which is just an old computer running Linux.
All it takes to have a DNS server is a Linux box running dnsmasq, which is a caching DNS server. It reads a file, usually /etc/hosts, for local hosts and forwards requests for Internet hosts to the DNS server you normally use.
Yes, but somebody still has to generate that hosts file and load it into the router. The router doesn't magically go out and ask every IP device what its name is, what its aliases are. And anyway, the devices may be signing White Knights, and I don't mean "in satin". -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/18/2014 05:58 PM, Anton Aylward wrote:
Yes, but somebody still has to generate that hosts file and load it into the router. The router doesn't magically go out and ask every IP device what its name is, what its aliases are.
As the list in the Web-UI in a netgear router is correct, I assume it gets the names from the DHCP requests the clients are initiating. From /etc/sysconfig/network/dhcp: ## Type: string ## Default: AUTO # # specify a hostname to send ( -h option) # # specifies a string used for the hostname option field when dhcpcd sends DHCP # messages. Some DHCP servers will update nameserver entries (dynamic DNS). # Also, some DHCP servers, notably those used by @Home Networks, require the # hostname option field containing a specific string in the DHCP messages from # clients. # # By default the current hostname is sent ("AUTO"), if one is defined in # /etc/HOSTNAME. # Use this variable to override this with another hostname, or leave empty # to not send a hostname. # DHCLIENT_HOSTNAME_OPTION="AUTO" I also have such a netgear router - I have to look ... Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 11/18/2014 01:01 PM, Bernhard Voelker wrote:
On 11/18/2014 05:58 PM, Anton Aylward wrote:
Yes, but somebody still has to generate that hosts file and load it into the router. The router doesn't magically go out and ask every IP device what its name is, what its aliases are.
As the list in the Web-UI in a netgear router is correct, I assume it gets the names from the DHCP requests the clients are initiating. From /etc/sysconfig/network/dhcp:
Are you talking about the DHCP server on the Netgear or the DHCP server on the Linux host? You quoted the config file from the Linux host. IF, and its an IF, the host sends a name to the DHCP server then it must have been configured to do so. We're back to the issue of correct and complete configuration. This doesn't happen by magic. We're also talking about a DHCP server with this capability. If you are running a lo end smb/home server with built in DHCP and DNS proxy that isn't going to happen. If you are running a Linux box as the firewall, DHCP server, DNS server then you must have manually configured all the names. In which case we've gor the question of why dynamic addresses, why not static ones and static entries in the DNS? Yes, anything is possible, but the moment you start tying things down, adding constraints such as 'this is a server' and 'this is my home/office lan' and 'these are not machines that connect dynamically' and "there is a DNS server running on that machine' and 'all hosts have their resovler pointing to the same server', than this random "Yes But What If" speculation stops. DEAD. All that config file you quoted is meaningless if the Netgear gateway/firewall machine is set up like mine to do DHCP and to proxy/cache DNS to the ISP and all hosts have their resolved pointing to the Netgear, which is how I have mine set up. Yes, the netgear has a set of static assignments for my desktop, mail hub, voip, wifi and archive server. The names are in that table but that table doesn't "do" DNS. There names are there to remind me, in effect a comment field. All my Linux hosts have /etc/hosts files for the devices on the lcoal LAN. Could I have set it up differently? Possibly, but the DNS capability of the Netgear isn't like that of a full blown Linux host with the kind of capability inferred by the config file you quote. Could I do things differently? Yes. I've run a gateway/firewall based on a Linux box. I've run it with IpCop and with a Shorewall based firewall. I've tiered other "firewall in a package" LINUX Cds as well :-) They were a wonderful "learning experience". I enjoyed fiddling with then and learning about how the Linux IP stack differed from what I'd learnt from Commer. But the Netgear "just works" and doesn't tempt me to fiddle and consumes a lot less power. It also has a switch built in, which is nice. I got it originally for the switch and used it with the IPCop f/w, then thought "what the hell, why do I need the extra box". KISS. So yes, you could do it any number of ways, but don't expect the Netgear to be as capable as a full Linux box. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 18/11/2014 19:44, Anton Aylward a écrit :
So yes, you could do it any number of ways, but don't expect the Netgear to be as capable as a full Linux box.
yes and no :-) http://www.cjoint.com/14nv/DKsuExLdPG1_capture-0061.jpeg this is the dhcp account of my internet box (freebox). You can see the *name* of some connected devices is included. I don't know how. I certainly never did this myself. this don't mean you are wrong, this don't even mean this features are on the box itslef - the box is nothing more than a linux box tightly connected to a server (probably also linux box) at the other side of the wire, and I can't know what part do what task. and, by the way, it don't looks like I can type a name in firefox to have the connection. but this mean something on my linux box (openSUSE 13.1) did advertise the computer name at a moment or an other, and it's also possble for an iphone (bottom of the image, claire is my daughter that did not come home since september 20012 :-() there is always some magic in network :-)) jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-18 19:44, Anton Aylward wrote:
On 11/18/2014 01:01 PM, Bernhard Voelker wrote:
IF, and its an IF, the host sends a name to the DHCP server then it must have been configured to do so. We're back to the issue of correct and complete configuration. This doesn't happen by magic.
Magic aka YaST :-)
We're also talking about a DHCP server with this capability. If you are running a lo end smb/home server with built in DHCP and DNS proxy that isn't going to happen.
My cheap router does it :-)
In which case we've gor the question of why dynamic addresses, why not static ones and static entries in the DNS?
It is easier to configure all addresses and network settings, pseudo-dynamically, in the dhcp server. One central place. Then have all the machines to autoconfigure.
But the Netgear "just works" and doesn't tempt me to fiddle and consumes a lot less power. It also has a switch built in, which is nice. I got it originally for the switch and used it with the IPCop f/w, then thought "what the hell, why do I need the extra box". KISS.
Same here. But seeing the many capabilities my cheap router has, half of them which I do not use, and some I would like it doesn't have. Perhaps I could flash mine, but the router being a crucial part of my setup, I do not want to risk breaking it without having a replacement. ...replacement which I may have: the old router. So flashing it is something to consider at some point, specially after learning mine has holes. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 11/18/2014 02:46 PM, Carlos E. R. wrote:
We're also talking about a DHCP server with this capability. If you are running a lo end smb/home server with built in DHCP and DNS proxy that isn't going to happen. My cheap router does it :-)
According to my experience setting up Dynamic DNS on a Linux machine and DHCP server, first on the same machine then moving it to another linux machine, there is the matter of a cryptographic key that is required by Dynamic DNS that the DHCP server needs to know about. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-18 23:59, Anton Aylward wrote:
On 11/18/2014 02:46 PM, Carlos E. R. wrote:
According to my experience setting up Dynamic DNS on a Linux machine and DHCP server, first on the same machine then moving it to another linux machine, there is the matter of a cryptographic key that is required by Dynamic DNS that the DHCP server needs to know about.
dnsmasq is smaller and does both tasks, coordinately :-) -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 2014-11-18 17:58, Anton Aylward wrote:
On 11/18/2014 11:41 AM, James Knott wrote:
Yes, but somebody still has to generate that hosts file and load it into the router. The router doesn't magically go out and ask every IP device what its name is, what its aliases are. And anyway, the devices may be signing White Knights, and I don't mean "in satin".
It can handle over addresses and names via dhcp, and add those relationships to the dns server. The dnsmasq daemon can do it. Of course, you still need to assign names to machines, or have it assign arbitrary-automatic names it chooses. It is possible. As a matter of fact, my router finds out the names of windows machines it serves via dhcp. And of some android devices. My Linux machines are on fixed addresses, so I don't see them in that list - but still, there is a protocol for that naming, and the local dns server could find them out, too. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 11/18/2014 01:28 PM, Carlos E. R. wrote:
As a matter of fact, my router finds out the names of windows machines it serves via dhcp.
What is your router? -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-18 19:45, Anton Aylward wrote:
On 11/18/2014 01:28 PM, Carlos E. R. wrote:
As a matter of fact, my router finds out the names of windows machines it serves via dhcp.
What is your router?
A TP-Link. TD-W8970. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 11/18/2014 02:24 PM, Carlos E. R. wrote:
On 2014-11-18 19:45, Anton Aylward wrote:
On 11/18/2014 01:28 PM, Carlos E. R. wrote:
As a matter of fact, my router finds out the names of windows machines it serves via dhcp.
What is your router?
A TP-Link. TD-W8970.
Is it flashed with WRT? http://wiki.openwrt.org/toh/tp-link/td-w8970 Which version? Its a very nice device but I don't see anything in the spec that make me think its DHCP server communicates with a DNS server. If this is a windows only then that has nothing to do with the DHCP server issuing changes to a Dynamic DNS server as an earlier post by Bernard Voelker implied. I've set that up for a Linux based DHCP/DBS and it requires the DHCP server knowing the cryptographic key for the DNS server. I don't see anything in the w8970 spec that indicates this capability. Souping up names for Windows machines that are broadcasting their names and addresses, as I mentioned earlier, is quite another matter. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-18 23:59, Anton Aylward wrote:
Is it flashed with WRT? http://wiki.openwrt.org/toh/tp-link/td-w8970
Which version?
Nope, the original firmware plus an update.
Its a very nice device but I don't see anything in the spec that make me think its DHCP server communicates with a DNS server.
It does not. I did not say it does. I said that it finds the names of the devices the internal dhcp server feeds. Same as the one in this photo from jdd: http://www.cjoint.com/14nv/DKsuExLdPG1_capture-0061.jpeg but in text only.
Souping up names for Windows machines that are broadcasting their names and addresses, as I mentioned earlier, is quite another matter.
It doesn't get them via broadcast. And it remembers the names for ages. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
Op dinsdag 18 november 2014 19:28:46 schreef Carlos E. R.:
As a matter of fact, my router finds out the names of windows machines it serves via dhcp. And of some android devices. My Linux machines are on fixed addresses, so I don't see them in that list - but still, there is a protocol for that naming, and the local dns server could find them out, too.
I did not read the whole thread, but maybe this is covered by the mdns protocol (multicast dns), also called zeroconf (RFC 6762). -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-19 00:06, Freek de Kruijf wrote:
I did not read the whole thread, but maybe this is covered by the mdns protocol (multicast dns), also called zeroconf (RFC 6762).
It could be. I guess that ubuntu sets it up differently. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 11/18/2014 01:28 PM, Carlos E. R. wrote:
It can handle over addresses and names via dhcp, and add those relationships to the dns server. The dnsmasq daemon can do it.
HO! That's a bit of a cheat, isn't is, because dnsmasq is a DHCP server, DNS server, uses NAPTR records which allows the use of regular-expression-based rewriting of domain names which can then be used as URIs. That's a bit more than the 'traditional' BIND/DNS and since its all 'internal', eliminates the need for RFC2136 style communication between the separate DHCP and DNS servers. Calling dnsmasq a dns server is a bit like calling a a Ferrari an internal combustion engine on wheels. It is, but there's a good deal more to it! -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2014-11-19 00:20, Anton Aylward wrote:
On 11/18/2014 01:28 PM, Carlos E. R. wrote:
It can handle over addresses and names via dhcp, and add those relationships to the dns server. The dnsmasq daemon can do it.
HO! That's a bit of a cheat, isn't is, because dnsmasq is a DHCP server, DNS server, uses NAPTR records which allows the use of regular-expression-based rewriting of domain names which can then be used as URIs. That's a bit more than the 'traditional' BIND/DNS and since its all 'internal', eliminates the need for RFC2136 style communication between the separate DHCP and DNS servers. Calling dnsmasq a dns server is a bit like calling a a Ferrari an internal combustion engine on wheels. It is, but there's a good deal more to it!
LOL. But it works, and it is quite simple to setup. What I don't know is how to tell it that a certain IP is the 'MX', say. Maybe it is possible, maybe not. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Maybe a stupid question but ... are you sure, that avahi-daemon.service is enabled and running? On 11/17/2014 01:10 PM, Paul Groves wrote:
Hi All,
I have a problem that has been ongoing since 12.3 with openSUSE not being able to resolve hostnames on LAN.
I have this issue at home and at work where I cannot type in the name of a computer or device into Firefox or dolphin, I have to type in the IP. (i.e. https://freenas will not work but https://192.168.0.10 will work).
Ubuntu works fine once samba is enabled. I also have samba enabled on openSUSE and it does not work. I have also tried turning off SUSE Firewall and rebooting but still no change.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJUbBIQAAoJEH8sJoKRFRU5/OcP/1VqiQkHWCL8e0np0wBR8E5C 8ZWDg9vcmZl4SdbHJ4qkLSgAe8/NK0GZWJNsCJlBOG4ZoRfQrWBtWtMgQM1LuL7u bYfL7hJXF/PsSFNeWIZ5D2f1CpHMWx2aX/7tyNQr4rRKiiRLxMsAwNb7vDpaTsrC IzBHc4E9ALE81GmMwjV8ZC3GOaDZOsrqEVb7RqC5bs52IDhRJh3xPuq/8SprpFHK imGlc/lAWVqFlVZ4bv6Jh2rsRF5qLwNYXM42p31S3qhnkauGeGLWdtfbzCoUHhKc k8qYAnKzfTKhG3uS/W6wgPnkyiZa1g8SImH2J18+oJXAq2n/MRDh/ic9lC/BGKVA +Ua2H94QRrjAPhyI1xWtMgP5W8fB2kAjT4CqTSmaEKfAnybrDsF1Z+B4c54b/kBM Ml9NTpcLQeskTatLQDY3BlL685+jPeD9AwHCKVXbb+AQoN7JT6nPTuyMo7bcfY0Y Xh50sE1lTGQMqP+Rb5YZbRhuCASuQdHKKmpU+qBQH78PonA73F2937VnioKBaKwG EMKR8TdaRZLFYAykjNXybhaNdO8cqIckBAIDL9xRwDGp2ULL0QtlXNGVjIadVfGn 6LZWnickrKyXf6G/ai9nC4uDUkohqwsmZ8toUi6NC694ek83ra9ntiF7knDea2tA S6opIJNfPP4P0OvhuBxh =QulD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
avahi-daemon is Enabled and Active
avahi-dnsconfd is Disables and Inactive
On 19 November 2014 04:33, Carlos E. R.
On 2014-11-19 04:44, Ico Petrov wrote:
Hello,
Maybe a stupid question but ... are you sure, that avahi-daemon.service is enabled and running?
No, it is a fair question, worth checking out. :-)
-- Cheers / Saludos,
Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (10)
-
Anton Aylward -
Bernhard Voelker -
Carlos E. R. -
Freek de Kruijf -
Ico Petrov -
James Knott -
Jan Ritzerfeld -
jdd -
Paul Groves -
Per Jessen