OpenWrt Forum Archive

Topic: Cannot get an ip address on a Buffalo WBR-G54 with Kamikaze 7.06

The content of this topic has been archived on 1 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Post #1
lstep
20 Jun 2007, 20:37

I'm trying to make kamikaze 7.06 work on my WBR-G54 router, but my DHCP server doesn't recognize Kamikaze's DHCPs requests!
I can flash it as I wish (on 192.168.11.1 when I unplug/plug the power supply). It works perfectly (it boots and the router has an ip address) with a witehrussian openwrt, dd-wrt and even the original Buffalo firmware.

It seems that kamikaze's policy is now to get its ip address from a DHCP server, but I couldn't find a DHCP server that "sees" the request. I'm on Linux and tried different servers (even different machines), and the requests (DHCP DISCOVER, as seen with ethereal) are "invisible" to the server :-(
I'm pretty sure the DHCP server is correctly configured.

It wouldn't be a problem if the failsafe mode would work with the WBR-G54, but that's not the case, so I don't have failsafe mode possibility. And there's no serial pin connectors on the WBR-G54 easily accessible (that doesn't require soldering).

Using tcpdump, I keep getting these requests, but absolutely no reply from anyone :-(

21:14:22.981983 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 00:90:4c:49:00:2a, length: 277

Using tethereal, I can get the content/description of the DHCP DISCOVER packets sent by Kamikaze:

Frame 1 (323 bytes on wire, 323 bytes captured)
    Packet Length: 323 bytes
    Capture Length: 323 bytes
    [Protocols in frame: eth:vlan:ip:udp:bootp]
Ethernet II, Src: 00:90:4c:49:00:2a (00:90:4c:49:00:2a), Dst: ff:ff:ff:ff:ff:ff (ff:ff:ff:ff:ff:ff)
    Destination: ff:ff:ff:ff:ff:ff (ff:ff:ff:ff:ff:ff)
        Address: ff:ff:ff:ff:ff:ff (ff:ff:ff:ff:ff:ff)
        .... ...1 .... .... .... .... = Multicast: This is a MULTICAST frame
        .... ..1. .... .... .... .... = Locally Administrated Address: This is NOT a factory default address
    Source: 00:90:4c:49:00:2a (00:90:4c:49:00:2a)
        Address: 00:90:4c:49:00:2a (00:90:4c:49:00:2a)
        .... ...0 .... .... .... .... = Multicast: This is a UNICAST frame
        .... ..0. .... .... .... .... = Locally Administrated Address: This is a FACTORY DEFAULT address
    Type: 802.1Q Virtual LAN (0x8100)
802.1Q Virtual LAN
    000. .... .... .... = Priority: 0
    ...0 .... .... .... = CFI: 0
    .... 0000 0000 0001 = ID: 1
    Type: IP (0x0800)
Internet Protocol, Src: 0.0.0.0 (0.0.0.0), Dst: 255.255.255.255 (255.255.255.255)
    Version: 4
    Header length: 20 bytes
    Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
        0000 00.. = Differentiated Services Codepoint: Default (0x00)
        .... ..0. = ECN-Capable Transport (ECT): 0
        .... ...0 = ECN-CE: 0
    Total Length: 305
    Identification: 0x0000 (0)
    Flags: 0x00
        0... = Reserved bit: Not set
        .0.. = Don't fragment: Not set
        ..0. = More fragments: Not set
    Fragment offset: 0
    Time to live: 64
    Protocol: UDP (0x11)
    Header checksum: 0x79bd [correct]
    Source: 0.0.0.0 (0.0.0.0)
    Destination: 255.255.255.255 (255.255.255.255)
User Datagram Protocol, Src Port: 68 (68), Dst Port: 67 (67)
    Source port: 68 (68)
    Destination port: 67 (67)
    Length: 285
    Checksum: 0x752c [correct]
Bootstrap Protocol
    Message type: Boot Request (1)
    Hardware type: Ethernet
    Hardware address length: 6
    Hops: 0
    Transaction ID: 0x79d6fb0d
    Seconds elapsed: 0
    Bootp flags: 0x0000 (Unicast)
        0... .... .... .... = Broadcast flag: Unicast
        .000 0000 0000 0000 = Reserved flags: 0x0000
    Client IP address: 0.0.0.0 (0.0.0.0)
    Your (client) IP address: 0.0.0.0 (0.0.0.0)
    Next server IP address: 0.0.0.0 (0.0.0.0)
    Relay agent IP address: 0.0.0.0 (0.0.0.0)
    Client MAC address: 00:90:4c:49:00:2a (00:90:4c:49:00:2a)
    Server host name not given
    Boot file name not given
    Magic cookie: (OK)
    Option: (t=53,l=1) DHCP Message Type = DHCP Discover
        Option: (53) DHCP Message Type
        Length: 1
        Value: 01
    Option: (t=61,l=7) Client identifier
        Option: (61) Client identifier
        Length: 7
        Value: 0100904C49002A
        Hardware type: Ethernet
        Client MAC address: 00:90:4c:49:00:2a (00:90:4c:49:00:2a)
    Option: (t=60,l=11) Vendor class identifier = "udhcp 1.4.2"
        Option: (60) Vendor class identifier
        Length: 11
        Value: 756468637020312E342E32
    Option: (t=55,l=9) Parameter Request List
        Option: (55) Parameter Request List
        Length: 9
        Value: 0103060C0F1C28292A
        1 = Subnet Mask
        3 = Router
        6 = Domain Name Server
        12 = Host Name
        15 = Domain Name
        28 = Broadcast Address
        40 = Network Information Service Domain
        41 = Network Information Service Servers
        42 = Network Time Protocol Servers
    End Option

I don't see anything wrong with these packets. I don't understand why they're not taken into account by any DHCP server. The only 'noticeable' thing, is that the packet has VLAN (1) information set (which I guess is normal, as the 4-ports hub on the WBR-G54 is set like this).

Does anybody see something strange that would explain why these DHCP requests are not seen? I don't know what I can try, I'm totally stuck :-(

Thanks for any help,
Luc

Post #2
axelilly
2 Jul 2007, 15:54

Were you ever able to get this problem resolved?

Post #3
mt6561
2 Jul 2007, 19:41

I setted up DHCP server on VLAN 1 (eth0.1), added BOOTP capability and it works! My WBR-G54 got IP, and I can ping it.

But - nothing more. All TCP and UDP ports are closed, and I can't change firmware. How can I debrick my device? Is there JTAG/RS323 cable pinouts?

Post #4
lstep
2 Jul 2007, 23:56
mt6561 wrote:

I setted up DHCP server on VLAN 1 (eth0.1), added BOOTP capability and it works! My WBR-G54 got IP, and I can ping it.

But - nothing more. All TCP and UDP ports are closed, and I can't change firmware. How can I debrick my device? Is there JTAG/RS323 cable pinouts?

How did you set a VLAN with a value 1 ? On Linux, vconfig can only create VLANs starting at 2.

(Last edited by lstep on 3 Jul 2007, 09:03)

Post #5
gagravarr
31 Oct 2007, 13:10

I think it a vlan configuration issue in kamikaze

I've managed to get into my WBR-G54, but only over wifi. What I did was download the source for Kamikaze 7.09, and build my own version of it. During the build process, once it had created "build_mipsel/root/etc/", I copied in two files. One was a passwd file with the password set (so I could ssh in), the second was expanded uci defaults, which turned on the wifi.

Once I load that on via tftp, I can ssh into the WBR-G54 over wifi. However, I can't seem to get any of the wired stuff to work. Now I need to figure out what the vlan settings ought to be.

If anyone wants to play, you can download my trx file from http://gagravarr.org/misc/openwrt-kamik … uashfs.trx . It'll come up on 192.168.1.9, root password is "password", with ssh enabled (but takes a little while to start). SSID is "NEW_AP"

Nick

The discussion might have continued from here.