Link-local in SuSE 9.1?
I noticed in /etc/networks in SuSE 9.1, there's an entry for the link-local address range: "link-local 169.254.0.0" Does this mean that SuSE now supports link-local, as described at the location listed below? http://files.zeroconf.org/draft-ietf-zeroconf-ipv4-linklocal.txt I can't find any info about it for IPv4 in SuSE and there's very little mention of it for IPv6. tnx jk
James wrote regarding '[SLE] Link-local in SuSE 9.1?' on Thu, Aug 26 at 16:16:
I noticed in /etc/networks in SuSE 9.1, there's an entry for the link-local address range: "link-local 169.254.0.0"
Does this mean that SuSE now supports link-local, as described at the location listed below?
http://files.zeroconf.org/draft-ietf-zeroconf-ipv4-linklocal.txt
I can't find any info about it for IPv4 in SuSE and there's very little mention of it for IPv6.
Search the archives for "Subnet 169.254.0.0" - it was discussed just a few days ago. Instructions are in the FAQ. I'd do the search and post a link, but text-mode web searches aren't as fun as you'd think. --Danny, on an ssh link w/ no browser
Danny Sauer wrote:
James wrote regarding '[SLE] Link-local in SuSE 9.1?' on Thu, Aug 26 at 16:16:
I noticed in /etc/networks in SuSE 9.1, there's an entry for the link-local address range: "link-local 169.254.0.0"
Does this mean that SuSE now supports link-local, as described at the location listed below?
http://files.zeroconf.org/draft-ietf-zeroconf-ipv4-linklocal.txt
I can't find any info about it for IPv4 in SuSE and there's very little mention of it for IPv6.
Search the archives for "Subnet 169.254.0.0" - it was discussed just a few days ago. Instructions are in the FAQ. I'd do the search and post a link, but text-mode web searches aren't as fun as you'd think.
I remember seeing that thread, but didn't pay attention to it. However, I've read the archives, but they didn't tell me much, that I didn't already know. I known, for quite some time, what link-local is. My question was if it's now supported in SuSE. And if so, how? tnx jk
James wrote regarding 'Re: [SLE] Link-local in SuSE 9.1?' on Thu, Aug 26 at 17:35:
Danny Sauer wrote:
Does this mean that SuSE now supports link-local, as described at the location listed below? [...] Search the archives for "Subnet 169.254.0.0" - it was discussed just a few days ago. Instructions are in the FAQ. I'd do the search and
James wrote on Thu, Aug 26 at 16:16: [...] post a link, but text-mode web searches aren't as fun as you'd think.
I remember seeing that thread, but didn't pay attention to it. However, I've read the archives, but they didn't tell me much, that I didn't already know. I known, for quite some time, what link-local is. My question was if it's now supported in SuSE. And if so, how?
Quoting from the archive: http://lists.suse.com/archive/suse-linux-e/2004-Aug/2658.html ---
Yes, but I don't understand why it is configured on 9.1, even when I have used only a static address.
The idea is to make 9.1 zeroconf ready. http://www.zeroconf.org --- Presumably then, yes, the idea of having that line in there is to make SuSE 9.1 zeroconf ready. That doesn't exactly answer your question, though. I suppose. So, a google search later (zeroconf site:suse.com) returns several references to that discussion and a pdf: http://www.suse.com/en/business/products/server/sles/sles9_featurelist_techn... That pdf references SLP as part of the zeroconf support included in SLES9. I've got SLP installed on my "ftp install" here, so SuSE does support that part of the zeroconf platform. Regarding the network configuration, well, probably the easiest way to test that is to yank the network cable in your DHCP-enabled SuSE box, restart that interface, and see what IP it gets. I let mine go for about a minute before I got tired of waiting - it didn't get an address. Alright, lets try something else. find / -mount -type f -exec grep -H 169.254 '{}' \; Luckily, there's only about 29K files on this machine (NFS mounted /home)... Boy, this takes forever. Whoops! I need to stick a "-type f" in there. Argh. Still taking forever. Alright, the 9.0 box returned nothing. Let's try the same thing on a 9.1 box Doh! Grep needs '-H' to print the filename when it only has one file arg. Good thing I'm not busy this morning... Hey, there are a few results on the 9.1 box: /etc/sysconfig/network/scripts/ifup-route /etc/networks/link-local So, that network in mentioned in the script that brings up the routes. Right around line 110 is a section to add the correct route for the interface(s) defined in LINKLOCAL_INTERFACES. That variable is defined at the end of /etc/sysconfig/network/config to include all of the local interfaces. Oh, what's this just above that line, though? There's this block: --- ## Type: string("off","guess","auto-off","auto-manual","manual") ## Default: "off" # # !!!This feature is still not implemented. Leave it to 'off'!!! # What shall we do if there is no valid configuration? # off: do nothing, just fail # guess: try to guess the needed info (zeroconf) # auto-off: trigger automatic creation of a config file; if that fails, do # nothing, just fail # auto-manual: trigger automatic creation of a config file; if that fails, ask # user to provide configuration (via yast) # manual: ask user to provide configuration (via yast) # !!!This feature is still not implemented. Leave it to 'off'!!! FAILURE_ACTION=off --- According to the second-to-last line, "This feature is still not implemented". One day, though, it looks like there will be the option to "guess" and work with a zeroconf network. For now, though, your SuSE 9.1 machine can route traffic to and from machines on a zeroconf'd network, but can't get its own address in that manner. It also supports SLP. --Danny, who included the whole procedure so perhaps someone will be able to answer their own similar questions someday. :)
participants (2)
-
Danny Sauer
-
James Knott