Your message dated Sat, 25 Jun 2011 13:44:05 +0200
with message-id <[email protected]>
and subject line Re: Bug#586706: Does it still appear in squeeze/testing?
has caused the Debian Bug report #586706,
regarding dhcp3-server: option routers in dhcpd.conf
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
586706: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586706
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dhcp3-server
Version: 3.1.1-6+lenny4
Severity: normal

I've tried to apply two routers for option routers for my subnet in dhcpd.conf. 
Below
i just encountered possible situations and results of "ip route show" on client 
machine after "--"
on next line. So:

1) option routers 192.168.73.1, 129.125.35.16;
--
192.168.73.0/24 dev eth0  proto kernel  scope link  src 192.168.73.13
127.0.0.0/8 dev lo  scope link

2) option routers 192.168.73.1;
--
192.168.73.0/24 dev eth0  proto kernel  scope link  src 192.168.73.13
127.0.0.0/8 dev lo  scope link
default via 192.168.73.1 dev eth0

3) option routers 129.125.35.16, 192.168.73.1;
--
192.168.73.0/24 dev eth0  proto kernel  scope link  src 192.168.73.13
127.0.0.0/8 dev lo  scope link

4) option routers 129.125.35.16;
--
192.168.73.0/24 dev eth0  proto kernel  scope link  src 192.168.73.13
127.0.0.0/8 dev lo  scope link
default via 192.168.73.16 dev eth0

So, when there are morte than two routers system see none of them. It 
condtradict to documentation on 
dhcp-options manual page.

-- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.31-020631-generic (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages dhcp3-server depends on:
ii  debconf [debconf-2.0]     1.5.24         Debian configuration management sy
ii  debianutils               2.30           Miscellaneous utilities specific t
ii  dhcp3-common              3.1.1-6+lenny4 common files used by all the dhcp3
ii  libc6                     2.7-18lenny4   GNU C Library: Shared libraries
ii  lsb-base                  3.2-20         Linux Standard Base 3.2 init scrip

dhcp3-server recommends no packages.

Versions of packages dhcp3-server suggests:
pn  dhcp3-server-ldap             <none>     (no description available)

-- debconf information:
* dhcp3-server/new_auth_behavior:
* dhcp3-server/interfaces: eth1
  dhcp3-server/new_next-server_behaviour:
* dhcp3-server/config_warn:



--- End Message ---
--- Begin Message ---

On Saturday, 25. June 2011, Sergey Ivanov wrote:
> 2011/6/25 Peter Marschall <[email protected]>:
> I guess that before proceed developers should be able to reproduce
> error locally whenever it's possible. I know you are not package
> mainter. But at least your word is more ponderable than mine.

The problem is often time ;-)
There are a lot of bugs to deal with, and sometimes, it is not exactly 
easy to reproduce the error, because the configuration maybe special.

So, especially for older bugs, I consider it OK to ask the original sbmitter 
for help.

Anyway: (see below)

> No, no. I mean try to reproduce error on new system. If on squeze
> error doesn't exist anymore - don't see reasons to hold this
> bug-report. But if you want also to support oldstable then why you ask
> me to check on squeze? All i can do - to check on lenny with today
> version.

I tested your problem with testing.
Result: the first router listed in the option is used for the default route.

This is not the absolute correct result, but it shows the problem in your 
report is fixed.

As the other problem (only first router for default route) is already reported 
in bug #629632, I do not see a reason to keep this bug here open.

Best regards
Peter

-- 
Peter Marschall
[email protected]


--- End Message ---

Reply via email to