Re: IPv6 in the network, please
2004-11-10 15:46:03
Sorry to send this back to this list. But if people are having problems,
I would encourage them (as well as yourself) to come to the NOC (at any
IETF, this one or any future IETF). That way we can ask questions like
"What is your MAC address" and offer a solution as quick as possible.
In any case, the solution, as far as we can tell, is that your ability to
receive DHCP offers on your linux system is broken.
Here are the logs. If you have more issues, I highly encourage you to
either take the problem to a "Trouble with DHCP on linux list" or come to
the NOC to continue the exploration.
Cheers!
Nov 8 15:27:52 (none) dhcpd: DHCPDISCOVER from 00:05:4e:40:17:62 via
130.129.128.80
Nov 8 15:27:53 (none) dhcpd: DHCPOFFER on 130.129.134.174 to
00:05:4e:40:17:62 via 130.129.128.80
Nov 8 15:29:35 (none) dhcpd: DHCPDISCOVER from 00:05:4e:40:17:62 via
130.129.128.80
Nov 8 15:29:36 (none) dhcpd: DHCPOFFER on 130.129.134.174 to
00:05:4e:40:17:62 via 130.129.128.80
Nov 8 15:29:43 (none) dhcpd: DHCPDISCOVER from 00:05:4e:40:17:62 via
130.129.128.80
Nov 8 15:29:43 (none) dhcpd: DHCPOFFER on 130.129.134.174 to
00:05:4e:40:17:62 via 130.129.128.80
Nov 8 15:29:59 (none) dhcpd: DHCPDISCOVER from 00:05:4e:40:17:62 via
130.129.128.80
Nov 8 15:29:59 (none) dhcpd: DHCPOFFER on 130.129.134.174 to
00:05:4e:40:17:62 via 130.129.128.80
Nov 8 15:30:59 (none) dhcpd: DHCPDISCOVER from 00:05:4e:40:17:62 via
130.129.128.80
Nov 8 15:30:59 (none) dhcpd: DHCPOFFER on 130.129.134.174 to
00:05:4e:40:17:62 via 130.129.128.80
Nov 8 15:30:59 (none) dhcpd: DHCPDISCOVER from 00:05:4e:40:17:62 via
130.129.128.80
Nov 8 15:30:59 (none) dhcpd: DHCPOFFER on 130.129.134.174 to
00:05:4e:40:17:62 via 130.129.128.80
Nov 8 15:32:32 (none) dhcpd: DHCPDISCOVER from 00:05:4e:40:17:62 via
130.129.128.80
Nov 8 15:32:33 (none) dhcpd: DHCPREQUEST for 130.129.134.174
(130.129.16.20) from 00:05:4e:40:17:62 (silkesvarten) via 130.129.128.80
Nov 8 15:32:33 (none) dhcpd: DHCPACK on 130.129.134.174 to
00:05:4e:40:17:62 (silkesvarten) via 130.129.128.80
Nov 8 15:53:21 (none) dhcpd: DHCPRELEASE of 130.129.134.174 from
00:05:4e:40:17:62 (silkesvarten) via 130.129.128.80 (found)
Nov 8 15:53:32 (none) dhcpd: DHCPDISCOVER from 00:05:4e:40:17:62 via
130.129.128.80
Nov 8 15:53:33 (none) dhcpd: DHCPOFFER on 130.129.134.174 to
00:05:4e:40:17:62 (silkesvarten) via 130.129.128.80
Nov 8 15:53:33 (none) dhcpd: DHCPREQUEST for 130.129.134.174
(130.129.16.20) from 00:05:4e:40:17:62 (silkesvarten) via 130.129.128.80
Nov 8 15:53:33 (none) dhcpd: DHCPACK on 130.129.134.174 to
00:05:4e:40:17:62 (silkesvarten) via 130.129.128.80
Nov 8 16:17:19 (none) dhcpd: DHCPRELEASE of 130.129.134.174 from
00:05:4e:40:17:62 (silkesvarten) via 130.12
--Brett
On Wed, Nov 10, 2004 at 02:18:31PM -0500, JORDI PALET MARTINEZ wrote:
Agree, good job. Is working for me since over 10 minutes ago.
Not for me. But interestingly, I've never been able to get an IPv4
address (or any responses) to DHCP queries from dhcpcd-1.3.22_p4 on Linux
on the v4 network. However, I managed to get a response and an IPv4
address on the IETF61IPv6 network.
Stig
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: Why, technically, MIP and IPv6 can't be deployed, (continued)
- Re: Why, technically, MIP and IPv6 can't be deployed, Spencer Dawkins
- Re: Why, technically, MIP and IPv6 can't be deployed, Masataka Ohta
- Re: Why, technically, MIP and IPv6 can't be deployed, Francis Dupont
- Re: Why, technically, MIP and IPv6 can't be deployed, Masataka Ohta
Re: IPv6 in the network, please, Leif Johansson
IPv6 in the network, please, Jeff Young
RE: IPv6 in the network, please, matthew . ford
Re: IPv6 in the network, please, Carsten Bormann
Re: IPv6 in the network, please, Stig Venaas
Re: IPv6 in the network, please, Tim Chown
Re: IPv6 in the network, please, Pekka Savola
|
|
|