[App_rpt-users] New ACID release - BeagleBoard MAC Address
Kevin Walsh
w8khw1 at gmail.com
Fri Aug 26 05:01:42 UTC 2011
Hi Jim,
Thanks as always for the timely response.
My requirement has nothing to do with DHCP. I believe that was the
problem from the earlier post I mentioned, but that's not the problem
herre.
My BeagleBoard configuration is using a static IP address, the content
/etc/network/interfaces is posted below:
#Static IP configuration
auto lo
auto usb0
iface lo inet loopback
iface usb0 inet static
address 172.22.32.132
netmask 255.255.255.0
gateway 172.22.32.1
(Note - I attempted to add the hwaddress tag to force a fixed mac
address, but id didn't work.)
The problem is that when the mac address of a device changes, the
content of the arp table on my firewall can no longer talk to the
BeagleBoard - because the MAC address changed. (IP address equals MAC
address in arp lookup table, right?) If I clear the arp table on the
firewall and then attempt to contact the BeagleBoard at the above
static IP address, it will learn the new MAC address and associate the
new MAC with the static IP. That all works fine until the BeagleBoard
is re-started for whatever reason - and the whole problem above starts
again.
I would hate to have to put the BeagleBoard outside the firewall and
dedicate a static routable IP address to just this device.
Hope that helps explain the problem.
73,
Kevin
W8KHW
On Thu, Aug 25, 2011 at 11:16 AM, Jim Duuuude <telesistant at hotmail.com> wrote:
> This "somewhat misfeature" of Pickle (or at least the Ubuntu distro) was
> never intended. However when it was first pointed out to me a realized
> how much of an incredible blessing in disguise it was.
>
> The reason being is: Threre is NEVER, EVER, EVER, *ANY* reason
> why ANYONE should trust a "toy" router to even accurately keep track of
> much less observe static DHCP bindings. That is *JUST NOT* an acceptable
> way of assigning a "static" LAN IP address.
>
> Routers that allegedly support this "feature" (boy that's being nice)
> generally
> don't very well and/or stably. I have had NOTHING BUT HEADACHES over
> the year when people attempt to do this. PLEASE, DONT LET IT HAPPEN
> TO YOU.
>
> Just assign a *REAL*static LAN IP on the Pickle system. Use the netsetup
> script if you arent comfortable with editing files in the Ubuntu distro.
> Assign
> a LAN IP address that is outside the range that the router assigns DHCP
> addresses. Sometimes, in rare cases, some routers will, by default
> use the entire LAN range for assigning DHCP address. If so you
> will need to configure the router to change this behavior, and "create"
> a range of LAN addresses outside the routers range of DHCP addresses.
>
> Believe me, this small amount of extra work when setting up a system
> TOTALLY is worthwhile and WILL save you some major grief in the future.
>
> JIM WB6NIL
>
>> Date: Thu, 25 Aug 2011 02:21:19 -0400
>> From: w8khw1 at gmail.com
>> To: app_rpt-users at ohnosec.org
>> Subject: [App_rpt-users] New ACID release - BeagleBoard MAC Address
>>
>> Hi,
>>
>> I was wondering if the next pickle image might address the random MAC
>> address issue. I saw there was a thread earlier on the list about this
>> issue, but didn't find a resolution. I have found several references
>> to "patches" that will correct the problem, but haven't really had
>> time to dive into the issue. I did try setting a static MAC in the
>> network config, but that didn't seem to work by itself.
>>
>> The main issue I need to resolve is that I create a static NAT
>> translation through my firewall to the BeagleBoard (based on the IP
>> address). The firewall caches the MAC address associated with that IP
>> address in the arp table, so when the BeagleBoard is re-started (and
>> the MAC address changes) it will no longer work through the firewall
>> unless I clear the firewall's arp table.
>>
>> 73
>> Kevin
>> W8KHW
>>
>> On Mon, Aug 22, 2011 at 6:14 AM, Jim Duuuude <telesistant at hotmail.com>
>> wrote:
>> > Its there now.. and no, the ISO file generally does not
>> > change when a new release comes out.
>> >
>> > JIM
>> >
>> _______________________________________________
>> App_rpt-users mailing list
>> App_rpt-users at ohnosec.org
>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
More information about the App_rpt-users
mailing list