FreeBSD MIPS and RB133c

[Oleksandr Tymoshenko]

On 10/05/2011 5:59 PM, Erik Moe wrote:
>
> On May 10, 2011, at 7:36 PM, Oleksandr Tymoshenko wrote:
>
>> On 10/05/2011 7:58 AM, Erik Moe wrote:
>>
>>>>> Using tcpdump, after RouterBoot finishes loading the kernel, I see one DHCP request coming from the RouterBoard using mac 00:0c:42:1e:9a:88 and then there is nothing after that.  I don't see any packets at all.
>>>>>
>>>>>    192.168.11.2.23224>   192.168.11.15.61904: [udp sum ok] UDP, length 21
>>>>> 09:24:05.839921 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 32)
>>>>>    192.168.11.15.61904>   192.168.11.2.23224: [udp sum ok] UDP, length 4
>>>>> 09:24:05.840980 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 328)
>>>>>    0.0.0.0.bootpc>   broadcasthost.bootps: [udp sum ok] BOOTP/DHCP, Request from 00:0c:42:1e:9a:88 (oui Unknown), length 300, xid 0xd8aaeeff, Flags [none] (0x0000)
>>>>> 	  Client-Ethernet-Address 00:0c:42:1e:9a:88 (oui Unknown)
>>>>> 	  Vendor-rfc1048 Extensions
>>>>> 	    Magic Cookie 0x63825363
>>>>> 	    DHCP-Message Option 53, length 1: Release
>>>>> 	    Client-ID Option 61, length 7: ether 00:0c:42:1e:9a:88
>>>>> 	    Vendor-Class Option 60, length 9: "Mikroboot"
>>>>> 	    Parameter-Request Option 55, length 2:
>>>>> 	      Subnet-Mask, Default-Gateway
>>>>> 	    END Option 255, length 0
>>>>> 	    PAD Option 0, length 0, occurs 32
>>>>>
>>>>> Thanks,
>>>>> Erik
>>>>>
>>>> Unfortunately the mac address is hardcoded for this driver (in sys/mips/adm5120/if_admsw.c):
>>>>
>>>> 389         /* XXXMIPS: fix it */
>>>> 390         enaddr[0] = 0x00;
>>>> 391         enaddr[1] = 0x0C;
>>>> 392         enaddr[2] = 0x42;
>>>> 393         enaddr[3] = 0x07;
>>>> 394         enaddr[4] = 0xB2;
>>>> 395         enaddr[5] = 0x4E;
>>>>
>>>>
>>>> Luiz
>>>>
>>>
>>>
>>> That's not the main issue I have, the fact that the mac address is hardcoded.  The issue is once the RouterBoot loads and boots the kernel, I'm not seeing the kernel sending any DHCP/BOOTB requests down the wire, even though from the console log it is acting like it is.
>>
>> Tcpdump session above - are those only packets during the session? Were
>> there proper DHCP replies that were ignored? Could you show full log?
>
>
> This is all the DHCP traffic, but this is coming from the Routerboot bios.  There is a Discover, Offer, Request and ACK.  Then the Routerboot tftps the kernel and starts to boot.  Then right after the "Sending DHCP Discover packet from interface admsw0 (00:0c:42:07:b2:4e)" message I see the DHCP Release, but that's coming from the Routerboot.

Try this hack:
http://people.freebsd.org/~gonzo/patches/admsw-hack.diff