Ubuntu
kdeadmin package

Syntax error in /etc/network/interfaces file

Bug #18069 reported by Thiago Barcelos on 2005-06-12

Affects		Status	Importance	Assigned to	Milestone
	kdeadmin (Ubuntu)	Fix Released	Medium	Jonathan Riddell

Bug Description

I have a Toshiba M35X notebook with built-in Ethernet support (Realtek chipset)
and WiFi (Atheros chipset). After installing Hoary, no network interfaces were
started, not even the default loopback device. After taking a look at the
/etc/network/interfaces file and trying to issue "ifup ath0" myself, I found out
that the last line of the file, corresponding to the regular ethernet interface
(eth0) had a syntax error: "iface eth0 inet" After that we would expect "dhcp"
or "static".
I believe that, for some reason, the hardware autodetection at install generated
this syntax error in the file.

Revision history for this message

Thiago Barcelos (thiago-barcelos) wrote on 2005-06-12:

/etc/network/interfaces file after Hoary installation Edit (403 bytes, text/plain)

Created an attachment (id=2715)
/etc/network/interfaces file after Hoary installation

Revision history for this message

Matt Zimmerman (mdz) wrote on 2005-06-23:

Please attach a copy of the /etc/network/interfaces file showing the problem

Revision history for this message

Matt Zimmerman (mdz) wrote on 2005-06-23:

Ah, you did already, thanks (was following the bug via email)

Revision history for this message

Colin Watson (cjwatson) wrote on 2005-06-26:

That's impressive; I can't find any code in netcfg capable of doing that. Could
you attach /var/log/installer/syslog to this bug, please? Thanks.

Revision history for this message

Thiago Barcelos (thiago-barcelos) wrote on 2005-06-27:

/var/log/installer/syslog file Edit (246.4 KiB, application/octet-stream)

Created an attachment (id=2842)
/var/log/installer/syslog file

ok, here it goes

Revision history for this message

Colin Watson (cjwatson) wrote on 2005-06-27:

I can't find anything here which could have caused this problem. Did you use any
network configuration tools after the installation?

If possible, it would be interesting to know whether a server installation
exhibits the same problem.

Revision history for this message

Thiago Barcelos (thiago-barcelos) wrote on 2005-07-06:

You got it; after reinstalling ubuntu I found out that the bug is related to knetworkconf, that
generates this syntax error in the file when I try to activate the ath0 interface.
Thanks very much for your support guys.
I will report the bug to the knetworkconf authors.

Revision history for this message

Colin Watson (cjwatson) wrote on 2005-07-06:

Thanks, reassigning.

Matt Zimmerman (mdz) on 2006-03-31

Changed in kdeadmin:
assignee:	nobody → jr

Rocco Stanzione (trappist) on 2006-04-14

Changed in kdeadmin:
status:	Unconfirmed → Confirmed

Revision history for this message

Luka Renko (lure) wrote on 2006-04-25:

I was able to reproduce the problem and I will look for proper fix.

Changed in kdeadmin:
status:	Confirmed → In Progress

Revision history for this message

Luka Renko (lure) wrote on 2006-04-28:

#10

knetworkconf has written partial line in /etc/network/interfaces if you had an interface manually configured or managed by network-manager. This is now respected and such interfaces are not written to /etc/network/interfaces unless you explicitly decide for their type (static/dhcp/bootp).

Changed in kdeadmin:
status:	In Progress → Fix Committed

Revision history for this message

Luka Renko (lure) wrote on 2006-04-29:

#11

kdeadmin (4:3.5.2-0ubuntu6) dapper; urgency=low

  * Add kubuntu_06_route_byte_order.patch to fix wrong gateway due to
    byte order on PPC (Malone: #23750)
  * Add kubuntu_07_unmanaged_if.patch to fix problem with unamanaged
    interface partially written to config file (Malone #18069)

-- Luka Renko <email address hidden> Fri, 28 Apr 2006 15:03:32 +0200