Ubuntu

Network interface changes after upgrading feisty to gutsy

Bug #131541 reported by darx
6
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

I upgraded feisty to gutsy tribe 4 and my wireless interface changed from eth0 to eth1. I don't know much about linux so I can't be sure if this is a security vulnerability. It could be if there was interface specific configurations or something prior to dist-upgrade.

I'm tagging this a a security vulnerability.

ProblemType: Bug
Architecture: i386
Date: Fri Aug 10 13:22:27 2007
DistroRelease: Ubuntu 7.10
NonfreeKernelModules: fglrx
Package: hal 0.5.9.1-1ubuntu2
PackageArchitecture: i386
SourcePackage: hal
Uname: Linux 2WIRE 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

Tags: apport-bug
Revision history for this message
darx (rabidphage) wrote :
Revision history for this message
Matthew Tighe (tighem) wrote :

Can you attach the output /etc/network/interfaces, uname -r, and ifconfig -a.

I wouldn't think a name change would be a security issue, but eth0=>eth1 is a little strange.

Revision history for this message
darx (rabidphage) wrote : Re: [Bug 131541] Re: Network interface changes after upgrading feisty to gutsy

/etc/network/interfaces has the ssid and wireless key in it. asking for that
is a stupid security issue isn't it?

uname -r 2.6.22-14-generic

On 22/02/2008, Matthew Tighe <email address hidden> wrote:
>
> Can you attach the output /etc/network/interfaces, uname -r, and
> ifconfig -a.
>
> I wouldn't think a name change would be a security issue, but
> eth0=>eth1 is a little strange.
>
> ** Changed in: ubuntu
> Status: New => Incomplete
>
>
> --
> Network interface changes after upgrading feisty to gutsy
> https://bugs.launchpad.net/bugs/131541
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Revision history for this message
Christopher Griffiths (chris) wrote :

Both versions of Ubuntu listed are no longer supported; the current version of Ubuntu supported editions do not have this issue or the bug is just not reproducible on my system.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.