I have the same problem, but after the latest update network-manager
icon disappeared. helps downgrading network-manager and network-manager-
gnome
--
network-manager After reboot network is totally broken
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you are a
On Sun, Oct 12, 2008 at 10:01:15AM -, Sergey Elin wrote:
> It seems hwaddress in interfaces ignored too:
>
> # cat /etc/network/interfaces
> auto lo
> iface lo inet loopback
>
> iface home inet static
> hwaddress ether 00:1E:8C:BA:A5:9A
> address 10.10.142.2
> netmask 255.2
On Thu, Oct 09, 2008 at 03:36:23PM -, Claudio Satriano wrote:
> ok.
>
> dns-nameservers works fine, but it seems that dns-search is ignored.
yes thats a known issue. pleaes retitle the bug and update description
so we can use this to track that.
- Alexander
--
network-manager After reboot
There was an upgrade of ifupdown a few days ago. It solved my problem.
--
network-manager After reboot network is totally broken
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
Thanks . It solved the problem.
On Wed, Oct 15, 2008 at 12:40 AM, Jeffrey Ratcliffe <
[EMAIL PROTECTED]> wrote:
> I worked around this by
>
> sudo apt-get remove network-manager
>
> and then adding
>
> auto eth0
> iface eth0 inet dhcp
>
> to my /etc/network/interfaces
>
> --
> network-manager Aft
I worked around this by
sudo apt-get remove network-manager
and then adding
auto eth0
iface eth0 inet dhcp
to my /etc/network/interfaces
--
network-manager After reboot network is totally broken
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you are a member
I am having the same problem. My /etc/network/interfaces output is
auto lo
iface lo inet loopback
auto dsl-provider
iface dsl-provider inet ppp
pre-up /sbin/ifconfig eth0 up # line maintained by pppoeconf
provider dsl-provider
auto eth0
iface eth0 inet manual
when I run sudo ifconfig -a I got
This is my /etc/network/interfaces
auto lo
iface lo inet loopback
auto usb0
iface usb0 inet static
address 192.168.0.200
netmask 255.255.255.0
network 192.168.0.0
up iptables -A POSTROUTING -t nat -j MASQUERADE -s 192.168.0.0/24 &
up echo 1 > /proc/sys/net/
Hi all,
This is something which is working for me after all the stuff I tried
yesterday.
This is using ethernet wired connection to an ADSL router
a. sudo ifconfig eth0 inet 192.168.1.2 netmask 255.255.255.0 broadcast
61.1.96.69
b. ping -c5 192.168.1.1
c. sudo route add default gw 192.168.
It seems hwaddress in interfaces ignored too:
# cat /etc/network/interfaces
auto lo
iface lo inet loopback
iface home inet static
hwaddress ether 00:1E:8C:BA:A5:9A
address 10.10.142.2
netmask 255.255.255.0
gateway 10.10.142.1
dns-nameservers 81.200.0.1
So
Since the latest update (Intrepid) I am not getting any network connection.
Among the reboots, I have seen this message:
* Starting NetworkManager... [fail]
[ 323.080645] pan0: Dropping NETIF_F_UO since no NETIF_F_HW_CSUM feature.
--
network-manager After reboot network is totally broken
https:
I have this problem too.
sudo dhclient
does at least get me a network connection.
--
network-manager After reboot network is totally broken
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
That was a bit quick, I hadn't actually rebooted.
When I rebooted, I came back to la-la land where nothing worked.
Then scanned a few manpages and came to know there is something called ifconfig
which does the same/similar thing as /etc/network/interfaces so tried that one
out.
sudo ifconfig
A slight update
Now this one is working atm but /etc/resolv.conf is still out
cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo i
Hi all,
Apologies for this one is going to be a long one.
I have a single ADSL router/modem and the basic way it works/worked is
that the router is the one which does all the authentication, I just
need to connect the power cable and I had connectivity.
With the recent updates firefox and pidg
ok.
dns-nameservers works fine, but it seems that dns-search is ignored.
Il giorno gio, 09/10/2008 alle 14.10 +, Alexander Sack ha scritto:
> On Thu, Oct 09, 2008 at 12:29:25PM -, Claudio Satriano wrote:
> > Ok, with "managed=true" NM now correctly detects my connection as
> > online.
> >
On Thu, Oct 09, 2008 at 12:29:25PM -, Claudio Satriano wrote:
> Ok, with "managed=true" NM now correctly detects my connection as
> online.
> However I'm not able to set up dns and default domain in NM, when I
> click on "OK" I got the "read only" error message.
>
> What I did therefore is see
Ok, with "managed=true" NM now correctly detects my connection as
online.
However I'm not able to set up dns and default domain in NM, when I
click on "OK" I got the "read only" error message.
What I did therefore is seeting up dns on /etc/resolv.conf
Claudio
Il giorno gio, 09/10/2008 alle 10.37
On Wed, Oct 08, 2008 at 09:50:45PM -, vista killer wrote:
> I have a different solution for my problem. I have to change in
> /etc/network/interfaces the eth0 to vnet0. I have found that now
> ifconfig commant give me that the name for my card is vnet0.
>
vnetX are not something network manag
On Tue, Oct 07, 2008 at 06:48:54PM -, vaughn wrote:
> Here's my interfaces file:
>
> auto lo
> iface lo inet loopback
>
> iface eth0 inet dhcp
> address 192.168.0.1
> netmask 255.0.0.0
>
> iface eth1 inet dhcp
> address 192.168.0.1
> netmask 255.0.0.0
> wireless-essid room3
>
> nm-system-se
On Tue, Oct 07, 2008 at 05:39:54PM -, brpaolo wrote:
> I had the same thing after today's update. After the first reboot, I had no
> connection any more. Now (after more reboots) I have a network connection,
> but Network Manager says I don't. Firefox starts offline. If I click on "Edit
> co
On Tue, Oct 07, 2008 at 05:38:57PM -, Ryan Ritterson wrote:
> my interfaces file was similar to Kadafi's, though I do not have a
> wireless interface.
if you have no wireless configuration you should be able to go for
"managed=true" in the config file the other comments refer to.
If you want
On Tue, Oct 07, 2008 at 03:36:19PM -, sheka wrote:
> my interfaces file
>
> auto lo
> iface lo inet loopback
>
> auto eth0
> iface eth0 inet dhcp
>
> networkmanager.conf
>
> [main]
> plugins=ifupdown,keyfile
>
> [ifupdown]
> managed=false
>
You have such a simple setup that you can easil
On Tue, Oct 07, 2008 at 02:23:43PM -, Kadafi wrote:
> Here are my /etc/network/interfaces :
>
> auto lo
> iface lo inet loopback
>
> auto eth0
> iface eth0 inet static
> address 192.168.2.136
> netmask 255.255.255.0
> gateway 192.168.2.1
>
> iface wlan0 inet static
> address 192.168.2.136
>
On Tue, Oct 07, 2008 at 10:20:31AM -, Claudio Satriano wrote:
> network-manager 0.7~~svn20081004t225044-0ubuntu1
>
> I got the same behaviour as in this bug report.
> Nevertheless I'm connected to the network, even if the NM applet shows up
> with a little cross, saying "No network connection
I have a different solution for my problem. I have to change in
/etc/network/interfaces the eth0 to vnet0. I have found that now
ifconfig commant give me that the name for my card is vnet0.
--
network-manager After reboot network is totally broken
https://bugs.launchpad.net/bugs/279262
You receiv
problem seems to be solved, as someone mentioned above.
my original /etc/network/interfaces read like this:
auto lo
iface lo inet loopback
iface eth0 inet static
address 192.168.2.136
netmask 255.255.255.0
gateway 192.168.2.1
iface wlan0 inet static
address 192.168.2.136
netmask 255.255.255.0
g
I have the same problem after the upgrade. My net is dead. Any solution
to solve this problem?
--
network-manager After reboot network is totally broken
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Setting my nm-system-settings.conf:
[ifupdown]
managed=true
Will make my resolv.conf completely empty. Trying to change the DNS will
give an error that the connection is read only.
--
network-manager After reboot network is totally broken
https://bugs.launchpad.net/bugs/279262
You received this
Thanks, Sokraates. Your hint helped me out. My interfaces file now is:
auto lo
iface lo inet loopback
# iface eth0 inet static
# address 192.168.1.9
# netmask 255.255.255.0
# gateway 192.168.1.1
auto eth0
--
network-manager After reboot network is totally broken
https://bugs.launchpad.net/bugs
I had exactly same problem as mentioned here.
--
network-manager After reboot network is totally broken
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
The way I worked around this was to change [ifupdown] manage=false to
true in the interfaces file. I then created a new connection "eth1"
within networkmanager copying the MAC address from the ifupdown (eth1)
entry or which ever one you are using to the new connection. I was able
to make it a sta
Same problem here (Kubuntu Intrepid), though I found a different
solution: I commented out the "iface XXX inet dhcp"-lines and now NM
works like a charm again.
Here's my /etc/network/interfaces, just to make it clear, what I mean:
# This file describes the network interfaces available on your sys
dhclient doesn't work because eth0 is up and show ipaddress, the problem seems
due to a dns trouble.
Sure i dunno why knetworkmanager applet show eth0 unmanaged.
Anyway, till now that network is working afert a pair of restart of network
icon is gray say unmanaged.
--
network-manager After rebo
My interfaces file looked like
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 192.168.0.167
netmask 255.255.255.0
gateway 192.168.0.1
auto eth1
#iface eth1 inet dhcp
auto eth2
#iface eth2 inet dhcp
auto ath0
#iface ath0 inet dhcp
auto wlan0
#iface wlan0 inet dhcp
af
You can temporarily use "sudo dhclient" to get a dhcp lease and be able
to access the network.
--
network-manager After reboot network is totally broken
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
Some things here, this my interfaces file:
auto lo
iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0
auto eth0
#iface eth0 inet dhcp
auto eth1
#iface eth1 inet dhcp
auto eth2
#iface eth2 inet dhcp
auto ath0
#iface ath0 inet dhcp
auto wlan0
#iface wlan0 inet dhcp
iface eth0 inet static
add
Here's my interfaces file:
auto lo
iface lo inet loopback
iface eth0 inet dhcp
address 192.168.0.1
netmask 255.0.0.0
iface eth1 inet dhcp
address 192.168.0.1
netmask 255.0.0.0
wireless-essid room3
nm-system-settings.conf
[main]
plugins=ifupdown,keyfile
[ifupdown]
manage=false
--
network-man
my interfaces file was similar to Kadafi's, though I do not have a
wireless interface.
A workaround to the problem is to simply removed the static section and
leave only the 'auto eth0' line, then reboot (some command may refresh
the interface without the reboot, but ifconfig eth0 down/up does not
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Confirmed
--
network-manager After reboot network is totally broken
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
I had the same thing after today's update. After the first reboot, I had no
connection any more. Now (after more reboots) I have a network connection, but
Network Manager says I don't. Firefox starts offline. If I click on "Edit
connections" and go to the wired connection and try to change somet
my interfaces file
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet dhcp
networkmanager.conf
[main]
plugins=ifupdown,keyfile
[ifupdown]
managed=false
--
network-manager After reboot network is totally broken
https://bugs.launchpad.net/bugs/279262
You received this bug notification be
I have this error too.
Upgraded to 8.10 beta earlier this week - upgraded this morning and now
have error were network manager says I am disconnected when in fact I am
not.
Wired interface is now named Ifupdown (eth0) - which is read only.
Firefox and Pidgin - both start offline
2.6.27-6-gene
Here are my /etc/network/interfaces :
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 192.168.2.136
netmask 255.255.255.0
gateway 192.168.2.1
iface wlan0 inet static
address 192.168.2.136
netmask 255.255.255.0
gateway 192.168.2.1
wireless-key ***
wireless-essid Br
Same here. The updates yesterday killed my ability to connect to a wired
network. When I click on the network manager, I get "device is
unmanaged"
--
network-manager After reboot network is totally broken
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you are a
network-manager 0.7~~svn20081004t225044-0ubuntu1
I got the same behaviour as in this bug report.
Nevertheless I'm connected to the network, even if the NM applet shows up with
a little cross, saying "No network connection".
As a side effect, Firefox always starts in offline mode, and I have to
m
I'm getting exactly the same behavior following todays update.
As of yesterday, I was hitting bug
https://bugs.launchpad.net/network-manager/+bug/256054, but on reboot this
morning, my manually defined IP settings where correctly remembered.
Unfortunately though, the networking isn't working and
also provide your complete /var/log/syslog taken _after_ reproducing
your bug.
--
network-manager After reboot network is totally broken
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
please post your /etc/network/interfaces and your /etc/NetworkManager
/nm-system-settings.conf.
Also consider to read /usr/share/network-manager/README.Debian.
** Changed in: network-manager (Ubuntu)
Sourcepackagename: None => network-manager
Status: New => Incomplete
--
network-manager
same here...
no networking at all since the update. etc/network/interfaces is ignored
with and without the ifupdown plugin.
--
network-manager After reboot network is totally broken
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you are a member of Ubuntu
Bugs,
As a workaround removed network-manager
sudo apt-get remove network-manager
And i started my network device with:
sudo ifup eth0
Hope this helps
--
network-manager After reboot network is totally broken
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you are
** Summary changed:
- After reboot network is totally broken
+ network-manager After reboot network is totally broken
** Tags added: network-manager
--
network-manager After reboot network is totally broken
https://bugs.launchpad.net/bugs/279262
You received this bug notification because you ar
52 matches
Mail list logo
