Hello all:
I'm using Bering 2.3, uClib 0.9 (Kernel 2.4.31), connected via Cable
Modem (Motorala Surfboard) to comcast. Relatively simple network,
two active interfaces (eth0, eth1) with a third installed (eth2) but
nothing connected at the moment. Everything seems to work just
great. All my "permanent" machines on the net have fixed addresses,
but I reserved a couple hundred for DHCP - my wife's work laptop
picks up an address just fine and sees everything on the net just
like it is supposed to.
Content of /etc/dnsmasq.conf:
omega# egrep -v "#.*|^$" /etc/dnsmasq.conf
domain-needed
bogus-priv
local=/private.network/
interface=eth1
expand-hosts
domain=private.network
dhcp-range=192.168.225.1,192.168.225.199,12h
Having just been burned by a hard drive going bad on the "family"
machine, I decided to put a file server on the network for some
redundancy and low-stress backups. For around $175 total I got a
Netgear SC101 "micro san" with two 200 GB Seagate drives, believing
the "just plug it in and it works". Well, it doesn't. I'm on my
second SC101 unit and it still isn't working right.
Ok, there is a LEAF question in here: The SC101 makes partitions
available by requesting DHCP addresses for them and performing some
sort of Windows SCSI driver magic to make them appear as lettered
drives on Windows boxes. Each of the drives gets a "root" partition
DCHP address when the SC101 boots, the requests additional ones for
each partition that is made. In looking at the daemon logs on my
Bering box it looks as if the SC101 is mucking with its MAC address
when requesting additional DHCP leases:
Jan 21 08:17:24 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 00:14:6c:0d:a4:e5
Jan 21 08:17:24 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.15
00:14:6c:0d:a4:e5
Jan 21 08:17:24 omega dnsmasq[4852]: DHCPREQUEST(eth1) 192.168.225.15
00:14:6c:0d:a4:e5
Jan 21 08:17:24 omega dnsmasq[4852]: DHCPACK(eth1) 192.168.225.15
00:14:6c:0d:a4:e5
Ok, the first "root" partition got "...15"; Then the SC101 puts a
"2" in the first MAC slot and makes another round of DHCP
negotiating, but for some reason doesn't like the Offers:
Jan 21 08:17:28 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0d:a4:e5
Jan 21 08:17:28 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.62
02:14:6c:0d:a4:e5
Jan 21 08:17:31 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0d:a4:e5
Jan 21 08:17:31 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.62
02:14:6c:0d:a4:e5
Jan 21 08:17:34 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0d:a4:e5
Jan 21 08:17:34 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.62
02:14:6c:0d:a4:e5
Jan 21 08:17:37 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0d:a4:e5
Jan 21 08:17:37 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.62
02:14:6c:0d:a4:e5
Jan 21 08:17:40 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0d:a4:e5
Jan 21 08:17:40 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.62
02:14:6c:0d:a4:e5
Jan 21 08:17:43 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 00:14:6c:0d:a4:e5
Jan 21 08:17:43 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.16
00:14:6c:0d:a4:e5
Jan 21 08:17:46 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 00:14:6c:0d:a4:e5
Jan 21 08:17:46 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.16
00:14:6c:0d:a4:e5
Jan 21 08:17:49 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 00:14:6c:0d:a4:e5
Jan 21 08:17:49 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.16
00:14:6c:0d:a4:e5
Jan 21 08:17:52 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 00:14:6c:0d:a4:e5
Jan 21 08:17:52 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.16
00:14:6c:0d:a4:e5
Jan 21 08:17:55 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 00:14:6c:0d:a4:e5
Jan 21 08:17:55 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.16
00:14:6c:0d:a4:e5
Jan 21 08:18:43 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0d:a4:e5
Jan 21 08:18:43 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.62
02:14:6c:0d:a4:e5
Jan 21 08:18:43 omega dnsmasq[4852]: DHCPREQUEST(eth1) 192.168.225.62
02:14:6c:0d:a4:e5
Jan 21 08:18:43 omega dnsmasq[4852]: DHCPACK(eth1) 192.168.225.62
02:14:6c:0d:a4:e5
OK, it finally accepted "62" - but look at the MAC addresses in the
DISCOVER broadcasts: they bounce between 00 and 02 in the first MAC slot.
Then it seems that the SC101 gave up on the addresses and started
requesting again:
Jan 21 08:19:17 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0d:a4:e5
Jan 21 08:19:17 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.63
02:14:6c:0d:a4:e5
Jan 21 08:19:20 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0d:a4:e5
Jan 21 08:19:20 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.63
02:14:6c:0d:a4:e5
Jan 21 08:19:23 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0d:a4:e5
Jan 21 08:19:23 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.63
02:14:6c:0d:a4:e5
Jan 21 08:19:26 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0d:a4:e5
Jan 21 08:19:26 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.63
02:14:6c:0d:a4:e5
Jan 21 08:19:29 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0d:a4:e5
Jan 21 08:19:29 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.63
02:14:6c:0d:a4:e5
Jan 21 08:20:01 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0d:a4:e5
Jan 21 08:20:01 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.63
02:14:6c:0d:a4:e5
Jan 21 08:20:01 omega dnsmasq[4852]: DHCPREQUEST(eth1) 192.168.225.63
02:14:6c:0d:a4:e5
Jan 21 08:20:01 omega dnsmasq[4852]: DHCPACK(eth1) 192.168.225.63
02:14:6c:0d:a4:e5
Finally, it appears to be happy:
Jan 21 08:53:42 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 00:14:6c:0d:a4:e5
Jan 21 08:53:42 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.15
00:14:6c:0d:a4:e5
Jan 21 08:53:42 omega dnsmasq[4852]: DHCPREQUEST(eth1) 192.168.225.15
00:14:6c:0d:a4:e5
Jan 21 08:53:42 omega dnsmasq[4852]: DHCPACK(eth1) 192.168.225.15
00:14:6c:0d:a4:e5 root-0
Jan 21 08:53:43 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0d:a4:e5
Jan 21 08:53:43 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.63
02:14:6c:0d:a4:e5
Jan 21 08:53:43 omega dnsmasq[4852]: DHCPREQUEST(eth1) 192.168.225.63
02:14:6c:0d:a4:e5
Jan 21 08:53:43 omega dnsmasq[4852]: DHCPACK(eth1) 192.168.225.63
02:14:6c:0d:a4:e5 root-1
root-0 and root-1 are the "root partitions" on the SC101.
The following is the log during an attempt to create a partition on
the SC101 named "fubar"
Jan 21 08:58:00 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0f:b0:fc
Jan 21 08:58:00 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.37
02:14:6c:0f:b0:fc
Jan 21 08:58:03 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0f:b0:fc
Jan 21 08:58:03 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.37
02:14:6c:0f:b0:fc
Jan 21 08:58:06 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0f:b0:fc
Jan 21 08:58:06 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.37
02:14:6c:0f:b0:fc
Jan 21 08:58:09 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0f:b0:fc
Jan 21 08:58:09 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.37
02:14:6c:0f:b0:fc
Jan 21 08:58:12 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0f:b0:fc
Jan 21 08:58:12 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.37
02:14:6c:0f:b0:fc
Jan 21 08:58:15 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 00:14:6c:0d:a4:e5
Jan 21 08:58:15 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.16
00:14:6c:0d:a4:e5
Jan 21 08:58:18 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 00:14:6c:0d:a4:e5
Jan 21 08:58:18 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.16
00:14:6c:0d:a4:e5
Jan 21 08:58:21 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 00:14:6c:0d:a4:e5
Jan 21 08:58:21 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.16
00:14:6c:0d:a4:e5
Jan 21 08:58:24 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 00:14:6c:0d:a4:e5
Jan 21 08:58:24 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.16
00:14:6c:0d:a4:e5
Jan 21 08:58:27 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 00:14:6c:0d:a4:e5
Jan 21 08:58:27 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.16
00:14:6c:0d:a4:e5
Jan 21 08:58:30 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0f:b0:fc
Jan 21 08:58:30 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.37
02:14:6c:0f:b0:fc
Jan 21 08:58:33 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0f:b0:fc
Jan 21 08:58:33 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.37
02:14:6c:0f:b0:fc
Jan 21 08:58:36 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0f:b0:fc
Jan 21 08:58:36 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.37
02:14:6c:0f:b0:fc
Jan 21 08:58:39 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0f:b0:fc
Jan 21 08:58:39 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.37
02:14:6c:0f:b0:fc
Jan 21 08:58:42 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0f:b0:fc
Jan 21 08:58:42 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.37
02:14:6c:0f:b0:fc
Jan 21 09:01:39 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0e:64:5d
Jan 21 09:01:39 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.64
02:14:6c:0e:64:5d
Jan 21 09:01:42 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0e:64:5d
Jan 21 09:01:42 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.64
02:14:6c:0e:64:5d
Jan 21 09:01:42 omega dnsmasq[4852]: DHCPREQUEST(eth1) 192.168.225.64
02:14:6c:0e:64:5d
Jan 21 09:01:42 omega dnsmasq[4852]: DHCPACK(eth1) 192.168.225.64
02:14:6c:0e:64:5d fubar
Jan 21 09:01:42 omega dnsmasq[4852]: DHCPREQUEST(eth1) 192.168.225.64
02:14:6c:0e:64:5d
Jan 21 09:01:42 omega dnsmasq[4852]: DHCPACK(eth1) 192.168.225.64
02:14:6c:0e:64:5d fubar
Jan 21 09:01:42 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 02:14:6c:0e:64:5d
Jan 21 09:01:42 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.64
02:14:6c:0e:64:5d
Jan 21 09:01:45 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 00:14:6c:0d:a4:e5
Jan 21 09:01:45 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.16
00:14:6c:0d:a4:e5
Jan 21 09:01:48 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 00:14:6c:0d:a4:e5
Jan 21 09:01:48 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.16
00:14:6c:0d:a4:e5
Jan 21 09:01:51 omega dnsmasq[4852]: DHCPDISCOVER(eth1) 00:14:6c:0d:a4:e5
Jan 21 09:01:51 omega dnsmasq[4852]: DHCPOFFER(eth1) 192.168.225.16
00:14:6c:0d:a4:e5
The MAC addresses are completely alien until it comes back around to
making requests for the "real" MAC again.
So does this look like a mis-configuration of my dnsmasq DHCP?
An incompatibility in the DHCP implementations between dnsmasq and the SC101?
Any ideas on where to start looking?
What else can I do for diagnosis purposes?
The Netgear Tech support has been *USELESS* on this problem, and the
SC101 has no diagnostics other than three leds on the front. There
is no external diagnostic software. While it will accept a "telnet
<sc101-dhcp-address> 80", it is not talking HTTP.
Sorry for the long post... log messages are dense!
TIA
Ken
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
------------------------------------------------------------------------
leaf-user mailing list: [email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-user
Support Request -- http://leaf-project.org/
