[ previous ] [ next ] [ threads ]
 From:  "Jimmy Bones (Omega)" <mhottie at gmail dot com>
 To:  joey young <joey underscore young at hotmail dot com>, m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] DHCP issue on 1.2stable
 Date:  Tue, 11 Oct 2005 03:46:58 -0400
Joey -

Not off at all, I did run into this problem a few times. I forgot to release
my IP address, and for some reason (even though I am using the same MAC addr
on the WAN NIC and the same MAC on the modem) I could not receive an IP
addr. It took almost 20-30 minutes for them to finally re-issue my IP addr.
I thought this initially was the problem, but after waiting for quite
sometime, calling them to clear my ip addr, etc. I realized that aside from
this, with 1.2 it would never renew. As soon as I changed back to 1.2b7 and
rebooted, my ip was renewed right away. So I am pretty sure at this point it
is a problem specifically with 1.2. I'll provide more detailed logs, etc, if
someone needs them.



On 10/10/05, joey young <joey underscore young at hotmail dot com> wrote:
> Jimmy -
> I may be off but mine did this several times as I was upgrading through
> the
> versions. What I found was happening was that my Time Warner cable modem
> would not release the MAC address from the previous unit. I think in your
> situation it is the same MAC address but the cable modem can't get a
> dynamic
> address from your ISP and the unit won't assign any LAN addresses. What I
> found to work was to either unplug my cable modem for about 30-minutes and
> put everything back together or call the support line and have them force
> a
> reset to clear the MAC address so that it would work again. One time I
> called support and they were questioning why my cable modem would not
> release two different MAC addresses. They should one have one at a time
> but
> a hard reset from the support guys cleared everything up.
> Good luck -
> Joey Young
> Email: Joey underscore Young at hotmail dot com
> -----Original Message-----
> From: Jimmy Bones (Omega) [mailto:mhottie at gmail dot com]
> Sent: Monday, October 10, 2005 9:29 PM
> To: m0n0wall at lists dot m0n0 dot ch
> Subject: [m0n0wall] DHCP issue on 1.2stable
> From another forum;
> Hey - Monowall (m0n0wall) 1.2 stable was released the other day. I have
> been
> using 1.2b7 for awhile now with FreeBSD 5.3 as it's base w/o any issues on
> a
> fairly high volume network.
> So now I changed to 1.2 stable that went back to the FreeBSD 4.11 branch,
> and my cable modem will not acquire an IP addr from the DHCP server. (RCN
> Cable)
> If I plug/unplug my cable modem, I keep getting this line in the syslog
> serve;
> /kernel: arp: 00:0x:xx:xx:xx:xx is using my ip address
> <><>
> !
> And I think this has to do with why it won't assign an IP. dhclient keeps
> timing out. Changed back to 1.2b7 and ip came right away.
> Any ideas?
> Thanks!
> (Note: In first /kernel msg that is my cable modem MAC, and the client
> macs
> were changed for the post)
> 2005/10/1021:44:21.47M/kernel: arp: 00:xx:xx:xx:xx:xx is using my ip
> address <> <>!
> 2005/10/1021:44:39.98Mdhclient: listening on bpf/rl0/00:ff:ff:ff:ff:fe
> 2005/10/1021:44:39.98Mdhclient
> : sending on bpf/rl0/00:ff:ff:ff:ff:fe
> 2005/10/1021:44:39.98Mdhclient: sending on socket/fallback
> 2005/10/1021:44:39.98Mdhclient: dhcpdiscover on rl0 to<>
> <> port 67 interval 5
> 2005/10/1021:44:44.31Mdhclient: dhcpdiscover on rl0 to<>
> <> port 67 interval 13
> 2005/10/1021:44:57.33Mdhclient: dhcpdiscover on rl0 to
> <> <> port 67
> interval 21
> 2005/10/1021:45:18.33Mdhclient: dhcpdiscover on rl0 to<>
> <> port 67 interval 18
> 2005/10/1021:45:36.33Mdhclient: dhcpdiscover on rl0 to
> <> <> port 67
> interval 4
> 2005/10/1021:45:40.33Mdhclient: no dhcpoffers received.
> 2005/10/1021:45:40.33Mdhclient: no working leases in persistent
> database - sleeping.