<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
This "somewhat misfeature" of Pickle (or at least the Ubuntu distro) was<br>never intended. However when it was first pointed out to me a realized<br>how much of an incredible blessing in disguise it was.<br><br>The reason being is: Threre is NEVER, EVER, EVER, *ANY* reason <br>why ANYONE should trust a "toy" router to even accurately keep track of<br>much less observe static DHCP bindings. That is *JUST NOT* an acceptable<br>way of assigning a "static" LAN IP address.<br><br>Routers that allegedly support this "feature" (boy that's being nice) generally<br>don't very well and/or stably. I have had NOTHING BUT HEADACHES over<br>the year when people attempt to do this. PLEASE, DONT LET IT HAPPEN<br>TO YOU.<br><br>Just assign a *REAL*static LAN IP on the Pickle system. Use the netsetup<br>script if you arent comfortable with editing files in the Ubuntu distro. Assign<br>a LAN IP address that is outside the range that the router assigns DHCP<br>addresses. Sometimes, in rare cases, some routers will, by default<br>use the entire LAN range for assigning DHCP address. If so you<br>will need to configure the router to change this behavior, and "create"<br>a range of LAN addresses outside the routers range of DHCP addresses.<br><br>Believe me, this small amount of extra work when setting up a system<br>TOTALLY is worthwhile and WILL save you some major grief in the future.<br><br>JIM WB6NIL<br><br><div>> Date: Thu, 25 Aug 2011 02:21:19 -0400<br>> From: w8khw1@gmail.com<br>> To: app_rpt-users@ohnosec.org<br>> Subject: [App_rpt-users] New ACID release - BeagleBoard MAC Address<br>> <br>> Hi,<br>> <br>> I was wondering if the next pickle image might address the random MAC<br>> address issue. I saw there was a thread earlier on the list about this<br>> issue, but didn't find a resolution. I have found several references<br>> to "patches" that will correct the problem, but haven't really had<br>> time to dive into the issue. I did try setting a static MAC in the<br>> network config, but that didn't seem to work by itself.<br>> <br>> The main issue I need to resolve is that I create a static NAT<br>> translation through my firewall to the BeagleBoard (based on the IP<br>> address). The firewall caches the MAC address associated with that IP<br>> address in the arp table, so when the BeagleBoard is re-started (and<br>> the MAC address changes) it will no longer work through the firewall<br>> unless I clear the firewall's arp table.<br>> <br>> 73<br>> Kevin<br>> W8KHW<br>> <br>> On Mon, Aug 22, 2011 at 6:14 AM, Jim Duuuude <telesistant@hotmail.com> wrote:<br>> > Its there now.. and no, the ISO file generally does not<br>> > change when a new release comes out.<br>> ><br>> > JIM<br>> ><br>> _______________________________________________<br>> App_rpt-users mailing list<br>> App_rpt-users@ohnosec.org<br>> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users<br></div> </div></body>
</html>