This bug was fixed in the package cntlm - 0.92.3-0ubuntu0.1
---
cntlm (0.92.3-0ubuntu0.1) precise-proposed; urgency=low
* Backport 0.92.3-1ubuntu1 to Precise as an SRU (LP: #1009436):
- Properly handle non-HTTP/1.1 keep-alive (LP: #1009436, #257210)
- Support SHOUTcast (ICY)
Booted up with network cable unplugged.
Started Firefox and entered a URL and pressed Enter.
The message '502 connection timed out. Cntlm proxy failed to complete the
request' appeared.
Plugged in network cable, waited for 'Connection Established' to appear.
Clicked Refresh in Firefox.
Web page lo
** Branch linked: lp:ubuntu/precise-proposed/cntlm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/825593
Title:
cntlm does not work at reboot
To manage notifications about this bug go to:
https://bu
Hello Edoardo, or anyone else affected,
Accepted cntlm into precise-proposed. The package will build now and be
available at http://launchpad.net/ubuntu/+source/cntlm/0.92.3-0ubuntu0.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
** Description changed:
+ [SRU] The debdiff attached to LP: #1009436 backports
+ cntlm-0.92.3-1ubuntu1 from Quantal to Precise.
+
+ [IMPACT]
+ Cntlm does not start if the parent proxy is unavailable.
+
+ [Test Case]
+ Cntlm should be correctly configured and network proxy applied system wide as
debdiff for Precise attached to LP: #1009436
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/825593
Title:
cntlm does not work at reboot
To manage notifications about this bug go to:
https://bugs.lau
** Also affects: cntlm (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/825593
Title:
cntlm does not work at reboot
To manage notifications
I believe this is fixed in the version published in quantal. The fix was
r280 upstream.
** Changed in: cntlm (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/8
Hi Stefano,
I just want to give you an update on my trouble shooting effort today.
I found out that the execution of '/etc/network/if-up.d/' is not
reliable all the time. From one boot to another boot I get different
result.
Practically I have 3 interfaces, lo, eth00, and eth10.
On some boot, I
Oke, I will modify my '/etc/network/if-up.d/' script.
I have asked the David Kubicek to fork a process to monitor the ifup
event and act accordingly. Since I'm a newbie in linux, I don't have
experience in linux programing :(.
In regards with my issue in Config 2, I check the source code of cntlm
Yup, obviously my workaround isn't much help when you have two
interfaces. I suggest locally editing the ifup.d script, I don't think
restarting is an appropriate response for everyone.
Even better, work on improving cntlm :)
Sorry, I can't understand what your issue with "config 2" is. Was the
p
Hi Stefano,
Thank you so much for your quick response :).
I have just installed the cntlm 0.91rc6 a couple of days ago via
aptitude, so it should have your fix in '/etc/network/if-up.d/' (I will
verify this on Mon. when I get back to the office). But from the boot
log, I do notice the 2nd round p
> Does the cntlm service started too early on reboot?
Yes, this sounds like LP: #358298, which I worked around by adding an
ifup.d script for.
Unfortunately, cntlm requires connectivity to its parent proxy at
startup. It would be preferable if it didn't and just returned 500s
until it could conta
13 matches
Mail list logo
