Project

General

Profile

Bug #1007

Mystery network settings

Added by cpg over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
01/26/2013
Due date:
% Done:

0%


Description

At the moment (porting to Fedora 18), we are seeing hda-install autdetect the network properly.

The interesting bit is that the network settings are properly setup in the database.

And the hda-install message detecting the IP and the gateway properly. This is before reboot (in a NATed VM)

# ip route
default via 172.16.94.2 dev eth0  proto static 
172.16.94.0/24 dev eth0  proto kernel  scope link  src 172.16.94.138 

This HDA's profile is setup in amahi.org to come up as 19.2.168.32.44 which.

However, when it comes up, even though * the hda-settings, and * the network settings in /etc/sysconfig/network-settings/ifcfg-eth0

are 172.16.94.2/44 .. which are right ...
https://dl.dropbox.com/u/364883/Screenshots/mystery-network-settings-f18.png

The HDA actually has an IP/GW of 192.168.32.44/1
It's a coincidence that it matches the amahi.org settings ...

First, hda-ctl should use the NetworkManager API, not direct writing on to that file.

Second where are these settings it actually is runnin coming from? I do not see anywhere where these are set!

Also available in: Atom