> It looks very much like this bug is still present. 
> 

The reason I closed the bug is that I did add the changed error message
that you requested. The bug you reported against had no automatically
generated config files, you had to set them up yourself.

> It seems to me that it is caused by incorrect formatting of PPP 
> interfaces' subnets in the config file at debconf-time.

If there is a bug in the debconf autogeneration in the last upload then
that sucks! :(
Unfortunately I can't reproduce this (since I don't have PPP access).
Could you please help me out and debug this? I'll happily assist you
(should we meet on IRC?).
Maybe we should open a new bug for the PPP issue...

> PPP interfaces have no '/number-of-bits' when they get automatically
> added to the config file and this omission makes bandwidthd choke.

If I'm reading this right what you are saying is that the config holds
somthing like this:
subnet 10.185.0.0
When it should say something like this instead:
subnet 10.185.0.0 255.255.0.0

That would probably indicate that something is wrong in the route
parsing part....


The autoconfiguration in bandwidthd has two paths, if you have iproute2
(package "iproute" in Debian, command "ip") installed thats used,
otherwise it falls back to using ifconfig, route and friends. Do you
have iproute2 installed?

The following commands are used in the config script, could you run them
and see what info they spit out on your machine?

/sbin/ip link show | grep "UP" | sed -e "s/.*: \(.*\): <.*/\1/
/sbin/ip route show | grep -v ^default | cut -d" " -f1

/sbin/ifconfig | grep "Link encap:" | cut -d" " -f1
/sbin/route -n | grep ^[0-9] | grep -v ^0.0.0.0 | cut -d" " -f1

The full output of "ip l s", "ip r s", "ifconfig" and "route -n" might
also help if my sed/cut/grep parts are somehow wrong...


HTH.

Regards,
Andreas Henriksson

PS. Please feel free to open a new bug regarding the autoconfiguration
with PPP issues.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to