Where is this 169.254.0.0/16 network coming from when I build a system via autoinstall? I don't have it defined in my config file, but it magically appears whenever I use autoinstall to build a SLES9 machine. I don't have this problem using autoinstall and SLES8. Also, would this phantom network have something to do with my gateway not working when the machine comes up? I have the gateway defined in the config file, but it never seems to make it over to the system at the end of the install. Here's a netstat from a freshly built machine: teeth:~ # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.150.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo Here's the network portion of the config file: <networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>srttel.com</domain> <hostname>teeth</hostname> <nameservers config:type="list"> <nameserver>10.150.1.3</nameserver> </nameservers> <searchlist config:type="list"> <search>srttel.com</search> <search>srtnet.com</search> <search>ndak.net</search> <search>minot.com</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>10.150.1.255</broadcast> <device>eth0</device> <ipaddr>10.150.1.111</ipaddr> <netmask>255.255.255.0</netmask> <network>10.150.1.0</network> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>eth0</device> </module_entry> </modules> <routing config:type="list"> <route> <destination>default</destination> <device>eth0</device> <gateway>10.150.1.1</gateway> <netmask>255.255.255.0</netmask> </route> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> Is there a way to keep this network from appearing? Is this network the reason why my gateway doesn't show up? I could put something in the post-install to clean this mess up, but that seems like a hack. Surely there is an elegant way to fix this. Thanks. -j
This is Zeroconf, it is configured by default and has nothing to do with your autoyast configuration. http://en.wikipedia.org/wiki/Zeroconf Anas Jon Thorson wrote:
Where is this 169.254.0.0/16 network coming from when I build a system via autoinstall? I don't have it defined in my config file, but it magically appears whenever I use autoinstall to build a SLES9 machine. I don't have this problem using autoinstall and SLES8.
Also, would this phantom network have something to do with my gateway not working when the machine comes up? I have the gateway defined in the config file, but it never seems to make it over to the system at the end of the install.
Here's a netstat from a freshly built machine:
teeth:~ # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.150.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
Here's the network portion of the config file:
<networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>srttel.com</domain> <hostname>teeth</hostname> <nameservers config:type="list"> <nameserver>10.150.1.3</nameserver> </nameservers> <searchlist config:type="list"> <search>srttel.com</search> <search>srtnet.com</search> <search>ndak.net</search> <search>minot.com</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>10.150.1.255</broadcast> <device>eth0</device> <ipaddr>10.150.1.111</ipaddr> <netmask>255.255.255.0</netmask> <network>10.150.1.0</network> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>eth0</device> </module_entry> </modules> <routing config:type="list"> <route> <destination>default</destination> <device>eth0</device> <gateway>10.150.1.1</gateway> <netmask>255.255.255.0</netmask> </route> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking>
Is there a way to keep this network from appearing? Is this network the reason why my gateway doesn't show up? I could put something in the post-install to clean this mess up, but that seems like a hack. Surely there is an elegant way to fix this.
Thanks.
-j
Ok, so I'll live with that network existing. Any idea as to why my default route isn't being configured? Thanks. -j On Wed, 2005-01-05 at 15:32 -0500, Anas Nashif wrote:
This is Zeroconf, it is configured by default and has nothing to do with your autoyast configuration.
http://en.wikipedia.org/wiki/Zeroconf
Anas
Jon Thorson wrote:
Where is this 169.254.0.0/16 network coming from when I build a system via autoinstall? I don't have it defined in my config file, but it magically appears whenever I use autoinstall to build a SLES9 machine. I don't have this problem using autoinstall and SLES8.
Also, would this phantom network have something to do with my gateway not working when the machine comes up? I have the gateway defined in the config file, but it never seems to make it over to the system at the end of the install.
Here's a netstat from a freshly built machine:
teeth:~ # netstat -rn Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 10.150.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
Here's the network portion of the config file:
<networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>srttel.com</domain> <hostname>teeth</hostname> <nameservers config:type="list"> <nameserver>10.150.1.3</nameserver> </nameservers> <searchlist config:type="list"> <search>srttel.com</search> <search>srtnet.com</search> <search>ndak.net</search> <search>minot.com</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>10.150.1.255</broadcast> <device>eth0</device> <ipaddr>10.150.1.111</ipaddr> <netmask>255.255.255.0</netmask> <network>10.150.1.0</network> <startmode>onboot</startmode> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>eth0</device> </module_entry> </modules> <routing config:type="list"> <route> <destination>default</destination> <device>eth0</device> <gateway>10.150.1.1</gateway> <netmask>255.255.255.0</netmask> </route> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking>
Is there a way to keep this network from appearing? Is this network the reason why my gateway doesn't show up? I could put something in the post-install to clean this mess up, but that seems like a hack. Surely there is an elegant way to fix this.
Thanks.
-j
On Wed, Jan 05, 2005 at 03:15:46PM -0600, Jon Thorson wrote: Hi,
Jon Thorson wrote:
Where is this 169.254.0.0/16 network coming from when I build a system via autoinstall? I don't have it defined in my config file, but it magically appears whenever I use autoinstall to build a SLES9 machine. I don't have this problem using autoinstall and SLES8.
<offtopic> Change the Variable LINKLOCAL_INTERFACES in /etc/sysconfig/network/config. The Script, which is used here, is /etc/sysconfig/network/scripts/ifup-route. </offtopic> frank -- /usr/sbin/thinkd: killed by signal 14, rebooting ERROR: unknown file format: /var/brain/memory thinkd aborted. no brain services available
On Wed, Jan 05, 2005 at 03:15:46PM -0600, Jon Thorson wrote:
Ok, so I'll live with that network existing. Any idea as to why my default route isn't being configured?
Here's the network portion of the config file:
<networking> ... <routing config:type="list"> <route> <destination>default</destination> <device>eth0</device> <gateway>10.150.1.1</gateway> <netmask>255.255.255.0</netmask> </route> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking>
Well, look at the docs: http://www.suse.de/~nashif/autoinstall/9.1/html/CreateProfile.Network.html#C... <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway>192.168.1.240</gateway> <netmask>-</netmask> </route> </routes> </routing> -- Martin Vidner, developer SuSE CR, s.r.o. e-mail: mvidner@suse.cz Drahobejlova 27 tel:+420-296542373 190 00 Praha 9, Czech Republic http://www.suse.cz
participants (4)
-
Anas Nashif -
Frank Hollmann -
Jon Thorson -
Martin Vidner