8:31 a.m.
I'm trying to upgrade the software on my broadband router. The closest
instructions I could find to doing it are here:
http://markferry.net/Network.SpeedtouchUpgrade
Those instructions are Debian/Ubuntu specific, but I figured I ought to
be able to adapt them. However I'm not having any luck.
What I've done is:
yum install tftp-server
yum install dhcp
I've updated /etc/xinetd.d/tftp to look like this:
# default: off
# description: The tftp server serves files using the trivial file transfer \
# protocol. The tftp protocol is often used to boot diskless \
# workstations, download configuration files to network-aware printers, \
# and to start the installation process for some operating systems.
service tftp
{
socket_type = dgram
protocol = udp
wait = yes
user = root
server = /usr/sbin/in.tftpd
server_args = -s /var/lib/tftpboot
disable = no
per_source = 11
cps = 100 2
flags = IPv4
}
(i.e. all I changed was disable = no)
/var/lib/tftpboot contains the software file (ZZQIAA8.225.bli).
I edited
/etc/dhcp/dhcpd.conf
to look like this:
#
# DHCP Server Configuration file.
# see /usr/share/doc/dhcp*/dhcpd.conf.sample
# see 'man 5 dhcpd.conf'
#
authoritative;
use-host-decl-names on;
ddns-update-style none;
option domain-name "colin.demon.co.uk";
next-server 192.168.254.201;
filename "linux/pxelinux.0";
allow bootp;
subnet 192.168.254.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.254.255;
}
group {
host 192.168.254.254 { hardware ethernet 00:14:7F:F8:83:DD; }
}
iptables and iptables6 are disabled.
I start the dhcp service. Then I telnet to the router and issue the
upgrade
command. I then see the following in syslog:
Dec 28 14:14:45 susannah dhcpd: Internet Systems Consortium DHCP Server 4.2.0-P2
Dec 28 14:14:45 susannah dhcpd: Copyright 2004-2010 Internet Systems Consortium.
Dec 28 14:14:45 susannah dhcpd: All rights reserved.
Dec 28 14:14:45 susannah dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Dec 28 14:14:45 susannah dhcpd: Not searching LDAP since ldap-server, ldap-port and
ldap-base-dn were not specified in the config file
Dec 28 14:14:45 susannah dhcpd: Wrote 0 deleted host decls to leases file.
Dec 28 14:14:45 susannah dhcpd: Wrote 0 new dynamic host decls to leases file.
Dec 28 14:14:45 susannah dhcpd: Wrote 0 leases to leases file.
Dec 28 14:14:45 susannah dhcpd: Listening on LPF/eth0/00:30:48:7c:c2:1a/192.168.254.0/24
Dec 28 14:14:45 susannah dhcpd: Sending on LPF/eth0/00:30:48:7c:c2:1a/192.168.254.0/24
Dec 28 14:14:45 susannah dhcpd: Sending on Socket/fallback/fallback-net
Dec 28 14:14:45 susannah dhcpd: BOOTREQUEST from 00:14:7f:f8:83:dd via eth0: BOOTP from
dynamic client and no dynamic leases
Dec 28 14:14:46 susannah ntpd[1395]: Listen normally on 19 eth0 192.168.254.201 UDP 123
Dec 28 14:14:46 susannah dhcpd: BOOTREQUEST from 00:14:7f:f8:83:dd via eth0: BOOTP from
dynamic client and no dynamic leases
Dec 28 14:14:47 susannah ntpd[1395]: 0.0.0.0 06a8 08 no_sys_peer
Dec 28 14:14:47 susannah dhcpd: BOOTREQUEST from 00:14:7f:f8:83:dd via eth0: BOOTP from
dynamic client and no dynamic leases
Dec 28 14:14:48 susannah dhcpd: BOOTREQUEST from 00:14:7f:f8:83:dd via eth0: BOOTP from
dynamic client and no dynamic leases
That last message is repeated ad-inifinitum. Well, not quite. Eventually
the router restarts into mormal operation mode, and the software version
is unchanged. And the following lines of syslog appear (which I think
are of no consequence):
Dec 28 14:16:12 susannah kernel: [184505.335245] e1000e: eth0 NIC Link is Down
Dec 28 14:16:12 susannah NetworkManager[1213]: <info> (eth0): carrier now OFF
(device state 8, deferring action for 4 seconds)
Dec 28 14:16:12 susannah kernel: [184505.336405] e1000e 0000:06:00.0: eth0: Reset adapter
Dec 28 14:16:17 susannah NetworkManager[1213]: <info> (eth0): device state change: 8
-> 2 (reason 40)
Dec 28 14:16:17 susannah NetworkManager[1213]: <info> (eth0): deactivating device
(reason: 40).
Dec 28 14:16:17 susannah avahi-daemon[1233]: Withdrawing address record for
192.168.254.201 on eth0.
Dec 28 14:16:17 susannah avahi-daemon[1233]: Leaving mDNS multicast group on interface
eth0.IPv4 with address 192.168.254.201.
Dec 28 14:16:17 susannah avahi-daemon[1233]: Interface eth0.IPv4 no longer relevant for
mDNS.
Dec 28 14:16:17 susannah NetworkManager[1213]: <info> Updating /etc/hosts with new
system hostname
Dec 28 14:16:17 susannah nm-dispatcher.action: nm_dispatcher_action: Invalid connection:
'(null)' / 'connection setting not found' invalid: 1
Dec 28 14:16:18 susannah ntpd[1395]: Deleting interface #19 eth0, 192.168.254.201#123,
interface stats: received=0, sent=8, dropped=0, active_time=92 secs
Dec 28 14:16:18 susannah ntpd[1395]: 193.1.31.66 interface 192.168.254.201 -> (null)
Dec 28 14:16:18 susannah ntpd[1395]: 83.229.210.18 interface 192.168.254.201 -> (null)
Dec 28 14:16:18 susannah ntpd[1395]: 194.38.104.240 interface 192.168.254.201 ->
(null)
Dec 28 14:16:18 susannah ntpd[1395]: 85.17.207.62 interface 192.168.254.201 -> (null)
Dec 28 14:16:22 susannah kernel: [184514.608409] e1000e: eth0 NIC Link is Up 100 Mbps Full
Duplex, Flow Control: None
Dec 28 14:16:22 susannah kernel: [184514.608412] e1000e 0000:06:00.0: eth0: 10/100 speed:
disabling TSO
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> (eth0): carrier now ON (device
state 2)
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> (eth0): device state change: 2
-> 3 (reason 40)
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> Activation (eth0) starting
connection 'System eth0'
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> (eth0): device state change: 3
-> 4 (reason 0)
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> Activation (eth0) Stage 1 of 5
(Device Prepare) scheduled...
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> Activation (eth0) Stage 1 of 5
(Device Prepare) started...
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> Activation (eth0) Stage 2 of 5
(Device Configure) scheduled...
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> Activation (eth0) Stage 1 of 5
(Device Prepare) complete.
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> Activation (eth0) Stage 2 of 5
(Device Configure) starting...
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> (eth0): device state change: 4
-> 5 (reason 0)
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> Activation (eth0) Stage 2 of 5
(Device Configure) successful.
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> Activation (eth0) Stage 3 of 5
(IP Configure Start) scheduled.
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> Activation (eth0) Stage 2 of 5
(Device Configure) complete.
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> Activation (eth0) Stage 3 of 5
(IP Configure Start) started...
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> (eth0): device state change: 5
-> 7 (reason 0)
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> Activation (eth0) Stage 4 of 5
(IP4 Configure Get) scheduled...
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> Activation (eth0) Stage 3 of 5
(IP Configure Start) complete.
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> Activation (eth0) Stage 4 of 5
(IP4 Configure Get) started...
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> Activation (eth0) Stage 5 of 5
(IP Configure Commit) scheduled...
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> Activation (eth0) Stage 4 of 5
(IP4 Configure Get) complete.
Dec 28 14:16:22 susannah NetworkManager[1213]: <info> Activation (eth0) Stage 5 of 5
(IP Configure Commit) started...
Dec 28 14:16:22 susannah avahi-daemon[1233]: Joining mDNS multicast group on interface
eth0.IPv4 with address 192.168.254.201.
Dec 28 14:16:22 susannah avahi-daemon[1233]: New relevant interface eth0.IPv4 for mDNS.
Dec 28 14:16:22 susannah avahi-daemon[1233]: Registering new address record for
192.168.254.201 on eth0.IPv4.
Dec 28 14:16:23 susannah NetworkManager[1213]: <info> (eth0): device state change: 7
-> 8 (reason 0)
Dec 28 14:16:23 susannah NetworkManager[1213]: <info> Policy set 'System
eth0' (eth0) as default for IPv4 routing and DNS.
Dec 28 14:16:23 susannah NetworkManager[1213]: <info> Updating /etc/hosts with new
system hostname
Dec 28 14:16:23 susannah NetworkManager[1213]: <info> Activation (eth0) successful,
device activated.
Dec 28 14:16:23 susannah NetworkManager[1213]: <info> Activation (eth0) Stage 5 of 5
(IP Configure Commit) complete.
Dec 28 14:16:23 susannah nm-dispatcher.action: nm_dispatcher_action: Invalid connection:
'(null)' / 'connection setting not found' invalid: 1
Dec 28 14:16:23 susannah ntpd[1395]: Listen normally on 20 eth0 192.168.254.201 UDP 123
Dec 28 14:16:23 susannah dhcpd: Internet Systems Consortium DHCP Server 4.2.0-P2
Dec 28 14:16:23 susannah dhcpd: Copyright 2004-2010 Internet Systems Consortium.
Dec 28 14:16:23 susannah dhcpd: All rights reserved.
Dec 28 14:16:23 susannah dhcpd: For info, please visit https://www.isc.org/software/dhcp/
Dec 28 14:16:23 susannah dhcpd: Not searching LDAP since ldap-server, ldap-port and
ldap-base-dn were not specified in the config file
Dec 28 14:16:23 susannah dhcpd: Wrote 0 deleted host decls to leases file.
Dec 28 14:16:23 susannah dhcpd: Wrote 0 new dynamic host decls to leases file.
Dec 28 14:16:23 susannah dhcpd: Wrote 0 leases to leases file.
Dec 28 14:16:23 susannah dhcpd: Listening on LPF/eth0/00:30:48:7c:c2:1a/192.168.254.0/24
Dec 28 14:16:23 susannah dhcpd: Sending on LPF/eth0/00:30:48:7c:c2:1a/192.168.254.0/24
Dec 28 14:16:23 susannah dhcpd: Sending on Socket/fallback/fallback-net
Dec 28 14:16:38 susannah kernel: [184530.931245] e1000e: eth0 NIC Link is Down
Dec 28 14:16:38 susannah NetworkManager[1213]: <info> (eth0): carrier now OFF
(device state 8, deferring action for 4 seconds)
Dec 28 14:16:38 susannah kernel: [184530.932396] e1000e 0000:06:00.0: eth0: Reset adapter
Dec 28 14:16:40 susannah kernel: [184532.643532] e1000e: eth0 NIC Link is Up 100 Mbps Full
Duplex, Flow Control: None
Dec 28 14:16:40 susannah kernel: [184532.643536] e1000e 0000:06:00.0: eth0: 10/100 speed:
disabling TSO
Dec 28 14:16:40 susannah NetworkManager[1213]: <info> (eth0): carrier now ON (device
state 8)
So I THINK that the repeated BOOTREQUEST messages mean that the request
isn't being honoured, and the router keeps repeating the request until
it times out (that's all guesswork).
What might I try for a better result?
--
Colin Adams
Preston Lancashire
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
9:20 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/28/2010 08:31 AM, Colin Paul Adams wrote:
I edited
/etc/dhcp/dhcpd.conf
to look like this:
#
# DHCP Server Configuration file.
# see /usr/share/doc/dhcp*/dhcpd.conf.sample
# see 'man 5 dhcpd.conf'
#
authoritative;
use-host-decl-names on;
ddns-update-style none;
option domain-name "colin.demon.co.uk";
next-server 192.168.254.201;
filename "linux/pxelinux.0";
allow bootp;
subnet 192.168.254.0 netmask 255.255.255.0 {
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.254.255;
}
group {
host 192.168.254.254 { hardware ethernet 00:14:7F:F8:83:DD; }
}
I looked at /usr/share/doc/dhcp-4.2.0/dhcpd.conf.sample,
and saw the following:
"
# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.
subnet 10.254.239.32 netmask 255.255.255.224 {
range dynamic-bootp 10.254.239.40 10.254.239.60;
option broadcast-address 10.254.239.31;
option routers rtr-239-32-1.example.org;
}
"
If the above, in the sample file, is correct,
and your router is using BOOTP instead of DHCP,
I would think you need
"range dynamic-bootp ..."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAk0aADAACgkQyc8Kn0p/AZRzlACfeZe3M257Yjd7hJxLdIJDqHzt
srIAnjHnPolQVWotLGs7lw9E2Wsz8vjr
=Q7Av
-----END PGP SIGNATURE-----
10:02 a.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 12/28/2010 09:20 AM, Rick Sewill wrote:
On 12/28/2010 08:31 AM, Colin Paul Adams wrote:
> I edited
> /etc/dhcp/dhcpd.conf
> to look like this:
> #
> # DHCP Server Configuration file.
> # see /usr/share/doc/dhcp*/dhcpd.conf.sample
> # see 'man 5 dhcpd.conf'
> #
> authoritative;
> use-host-decl-names on;
> ddns-update-style none;
> option domain-name "colin.demon.co.uk";
> next-server 192.168.254.201;
> filename "linux/pxelinux.0";
> allow bootp;
> subnet 192.168.254.0 netmask 255.255.255.0 {
> option subnet-mask 255.255.255.0;
> option broadcast-address 192.168.254.255;
> }
> group {
> host 192.168.254.254 { hardware ethernet 00:14:7F:F8:83:DD; }
> }
Hmmm. I did a little more digging.
I found, in "man dhcpd.conf", the following:
BOOTP Support
Each BOOTP client must be explicitly declared in the dhcpd.conf file.
A very basic client declaration will specify the client network
interface's hardware address and the IP address to assign to that
client. If the client needs to be able to load a boot file from the
server, that file's name must be specified. A simple bootp client
declaration might look like this:
host haagen {
hardware ethernet 08:00:2b:4c:59:23;
fixed-address 239.252.197.9;
filename "/tftpboot/haagen.boot";
}
Could you instead of doing what I thought previously, replace
> group {
> host 192.168.254.254 { hardware ethernet 00:14:7F:F8:83:DD; }
> }
with something like the following...
host myrouter {
hardware ethernet 00:14:7F:F8:83:DD;
fixed-address 192.168.254.254;
filename "/var/lib/tftpboot/ZZQIAA8.225.bli";
}
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
iEYEARECAAYFAk0aCigACgkQyc8Kn0p/AZTTqgCdHDl7KvO+2RfFy2Eep3k/RFOL
v1UAoJYrZnNwME92MLP5o8vsH9Wn3dBt
=GgOI
-----END PGP SIGNATURE-----
11:10 a.m.
Rick> On 12/28/2010 09:20 AM, Rick Sewill wrote:
Rick> Hmmm. I did a little more digging.
Rick> Could you instead of doing what I thought previously, replace
> group {
> host 192.168.254.254 { hardware ethernet 00:14:7F:F8:83:DD; }
> }
Rick> with something like the following...
Rick> host myrouter {
Rick> hardware ethernet 00:14:7F:F8:83:DD;
Rick> fixed-address 192.168.254.254;
Rick> filename "/var/lib/tftpboot/ZZQIAA8.225.bli";
Rick> }
Thanks.
That's better, in the now one BOOTREQUEST gets answered with one
BOOTREPLY.
But then NetworkManager resets the ethernet port, and we go round and
round (very slowly).
Eventually I had to reset the router.
I think i will have to buy a new one.
--
users mailing list
users(a)lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
--
Colin Adams
Preston Lancashire
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
4:28 p.m.
On Tue, 2010-12-28 at 17:10 +0000, Colin Paul Adams wrote:
But then NetworkManager resets the ethernet port, and we go round
and
round (very slowly).
Where does NetworkManager usually get your address from? Another DHCP
server on the LAN? That might be a bit of a problem, in itself.
Try:
service NetworkManager stop
service network start
Then manually bring up your ethernet and tell it what address to use.
e.g. ifup eth0 192.168.1.1
... If I recall the last step correctly, there appears to be no help for
the ifup command, on my laptop. Be certain to give it the IP address
suitable for your computer, not mine.
Otherwise, it'd be the ifconfig command you use to temporarily tell it
what address to use.
e.g. ifconfig eth0 192.168.1.1
--
[tim@localhost ~]$ uname -r
2.6.27.25-78.2.56.fc9.i686
Don't send private replies to my address, the mailbox is ignored. I
read messages from the public lists.
3 a.m.
>>>> "Tim" == Tim
<ignored_mailbox(a)yahoo.com.au> writes:
Tim> On Tue, 2010-12-28 at 17:10 +0000, Colin Paul Adams wrote:
> But then NetworkManager resets the ethernet port, and we go
round
> and round (very slowly).
Tim> Where does NetworkManager usually get your address from?
Tim> Another DHCP server on the LAN? That might be a bit of a
Tim> problem, in itself.
No. It's a static IP-address and it's hard-coded in
/etc/sysconfig/networking/devices/ifcfg-eth0
Tim> Try: service NetworkManager stop service network start
I did that.
Tim> Then manually bring up your ethernet and tell it what address
Tim> to use. e.g. ifup eth0 192.168.1.1
No need for that step (?), as network brings it up automatically.
But this just cuts out the noise from NetworkManager, I think. So now I
get the bare-bones of the loop in syslog:
Dec 29 08:44:30 susannah kernel: [251002.713374] e1000e 0000:06:00.0: eth0: Reset adapter
Dec 29 08:44:39 susannah kernel: [251011.985405] e1000e: eth0 NIC Link is Up 100 Mbps Full
Duplex, Flow Control: None
Dec 29 08:44:39 susannah kernel: [251011.985409] e1000e 0000:06:00.0: eth0: 10/100 speed:
disabling TSO
Dec 29 08:44:40 susannah dhcpd: BOOTREQUEST from 00:14:7f:f8:83:dd via eth0
Dec 29 08:44:40 susannah dhcpd: BOOTREPLY for 192.168.254.254 to myrouter
(00:14:7f:f8:83:dd) via eth0
Dec 29 08:44:50 susannah kernel: [251022.871241] e1000e: eth0 NIC Link is Down
Dec 29 08:44:50 susannah kernel: [251022.872351] e1000e 0000:06:00.0:eth0: Reset adapter
which just repeats until I reset the router. I guess the router just
doesn't like what it's getting.
--
Colin Adams
Preston Lancashire
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
4874
days inactive
4875
days old
5 comments
3 participants
participants (3)
-
Colin Paul Adams -
Richard Sewill -
Tim