ok. Thanks,
- Alexander
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Fix Released
--
fails to connect in feisty
https://bugs.launchpad.net/bugs/75237
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubu
My original problem was solved ages ago (see my post from 2007-01-05). I
left this bug open since other people used it to report unrelated
problems here.
--
fails to connect in feisty
https://bugs.launchpad.net/bugs/75237
You received this bug notification because you are a member of Ubuntu
Bugs,
Could you please check if this issue is still in latest gutsy network-
manager?
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Incomplete
--
fails to connect in feisty
https://bugs.launchpad.net/bugs/75237
You received this bug notification because you are a member of Ubuntu
I also have broken network manager with only wired networks in use. I
have two generic Ethernet cards that have always worked before, and
which are guaranteed Linux-supported by manufacturers (from Hoary till
Dapper have always worked).
I installed Herd 5 yesterday and updated to latest packages.
I also have broken network manager with only wired networks in use. I
have two generic Ethernet cards that have always worked before, and
which are guaranteed Linux-supported by manufacturers (from Hoary till
Dapper have always worked).
I installed Herd 5 yesterday and updated to latest packages.
I checked some more: My original problem is solved, network manager
connects my box reliably now.
My problem now is with firehol having a completely broken configuration
that breaks connectivity. This is #78017 for those interested.
--
fails to connect in feisty
https://launchpad.net/bugs/75237
I do not think I am still seeing the original issue:
network-manager used to not finish its IP configuration before. Nowadays
it does. Network configuration completes and looks sane (got the
expected IP, routes are set, resolv.conf is OK). BUT the configuration
does not work since the iptables fir
It turned out i was wrong. After I rebooted I had the same problem
again.
This is without any firewall installed.
I'm unable to do more testing as I've had to reinstall due to another
issue. sorry!
--
fails to connect in feisty
https://launchpad.net/bugs/75237
--
ubuntu-bugs mailing list
ubun
I am not using firestarter either! My impression reading this is that we
picked up a incompatibility between (some or all) iptable-based
firewalls and dhcp somewhere along the way.
--
fails to connect in feisty
https://launchpad.net/bugs/75237
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubunt
I'm not using Firestarter on any of my machines.
--
fails to connect in feisty
https://launchpad.net/bugs/75237
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Is anyone having this issue that isn't using Firestarter? If not, then I
will reassign this bug in a week or so.
--
fails to connect in feisty
https://launchpad.net/bugs/75237
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I can confirm that this issue is related to firewalling!
firehol works somewhat better than firestarter (or so it seems): It lets
me get a address and the interface comes up, but afterwards DNS requests
are blocked!
--
fails to connect in feisty
https://launchpad.net/bugs/75237
--
ubuntu-bugs
Got it to work again by removing Firestarter which in turn removed the
file "/etc/dhclient-exit-hooks" (if i remember correctly...)
--
fails to connect in feisty
https://launchpad.net/bugs/75237
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/u
Same thing here, even with the new avahi. There seems to be something
fishy with the dhcp scripts failing to return a sane value.
--
fails to connect in feisty
https://launchpad.net/bugs/75237
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubu
Attaching a log from my syslog
** Attachment added: "syslog"
http://librarian.launchpad.net/5371916/networkmanager.log
--
fails to connect in feisty
https://launchpad.net/bugs/75237
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bug
Didn't resolve the issue for me.
** Changed in: network-manager (Ubuntu)
Status: Fix Released => Confirmed
--
fails to connect in feisty
https://launchpad.net/bugs/75237
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Works again after latest avahi update.
** Changed in: network-manager (Ubuntu)
Status: Confirmed => Fix Released
--
fails to connect in feisty
https://launchpad.net/bugs/75237
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
I can confirm this on two machines running feisty current. I'm using the
network-manager-gnome.
** Changed in: network-manager (Ubuntu)
Status: Unconfirmed => Confirmed
--
fails to connect in feisty
https://launchpad.net/bugs/75237
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.c
18 matches
Mail list logo
