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 -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
