failure of dhcp - Networking

This is a discussion on failure of dhcp - Networking ; I cannot obtain IP address from a DHCP server. I use ndiswrapper. ifconfig eth0 down ifconfig wlan0 up iwconfig wlan0 essid SSID iwconfig wlan0 mode Managed iwconfig wlan0 channel 2 dhclient wlan0 no messages are printed. No IP is obtained. ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: failure of dhcp

  1. failure of dhcp

    I cannot obtain IP address from a DHCP server. I use ndiswrapper.

    ifconfig eth0 down
    ifconfig wlan0 up
    iwconfig wlan0 essid SSID
    iwconfig wlan0 mode Managed
    iwconfig wlan0 channel 2
    dhclient wlan0

    no messages are printed. No IP is obtained.
    after that /var/log/messages contains:

    dhclient:
    Listening on LPF/wlan0/
    Sending on LPF/wlan0/
    Sending on Socket/fallback
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
    No DHCPOFFERS received.
    No working leases in persistent database - sleeping.

    separated with: kernel: ndiswrapper (miniport_reset:68): wlan0 is
    being reset

    I can successfully connect to the network using Windows.


  2. Re: failure of dhcp

    bbla32@op.pl wrote:
    > I cannot obtain IP address from a DHCP server. I use ndiswrapper.
    >
    > ifconfig eth0 down
    > ifconfig wlan0 up
    > iwconfig wlan0 essid SSID
    > iwconfig wlan0 mode Managed
    > iwconfig wlan0 channel 2
    > dhclient wlan0
    >
    > no messages are printed. No IP is obtained.
    > after that /var/log/messages contains:
    >
    > dhclient:
    > Listening on LPF/wlan0/
    > Sending on LPF/wlan0/
    > Sending on Socket/fallback
    > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
    > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
    > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
    > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
    > DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
    > No DHCPOFFERS received.
    > No working leases in persistent database - sleeping.
    >
    > separated with: kernel: ndiswrapper (miniport_reset:68): wlan0 is
    > being reset
    >
    > I can successfully connect to the network using Windows.
    >


    What does a

    iwconfig wlan0

    report just before 'dhclient wlan0'?

    What is the WLAN access point at the other end of
    the wireless connection?

    --

    Tauno Voipio
    tauno voipio (at) iki fi

  3. Re: failure of dhcp

    On Wed, 14 Feb 2007 12:25:04 -0800, bbla32 wrote:

    > iwconfig wlan0 essid SSID
    > iwconfig wlan0 mode Managed


    In my experience, setting mode to Managed will reset the essid
    assignment..:

    iwconfig wlan0 mode Managed
    iwconfig wlan0 essid SSID

    > iwconfig wlan0 channel 2


    Why do you set the channel on the client?

    What's the output of "iwconfig wlan0" prior to "dhclient wlan0"?

    > I can successfully connect to the network using Windows.


    Proving what...?

    --
    Regards/mvh Joachim Mæland

    If everything seems under control, you're just not going fast enough.
    -Mario Andretti.


  4. Re: failure of dhcp

    > In my experience, setting mode to Managed will reset the essid
    > assignment..:


    here it didn't

    > > iwconfig wlan0 channel 2

    >
    > Why do you set the channel on the client?


    just in case..


    > What's the output of "iwconfig wlan0" prior to "dhclient wlan0"?



    # ifconfig eth0 down

    # iwconfig wlan0
    wlan0 IEEE 802.11b ESSIDff/any
    Mode:Auto Freq:2.412 GHz Access Point: Not-Assoc.
    Bit Rate: 54 Mb/s Tx-Power: 26 dBm Sensitivity=0/3
    RTS thr: 2432 B Fragment thr: 2432 B
    Encryption key: off
    Power Management: off
    Link Quality:0 Signal: 0 Noise: 0
    RX invalid nwid:0 Rx invalid crypt: 0 Rx inv. frag: 0
    Tx excessive retries: 0 Inv. misc:0 Missed beacon: 0

    # iwconfig wlan0 essid ESSID

    # iwconfig wlan0
    changed:
    ESSID: set correctly
    Mode: Managed Freq: 2.417 GHz (=channel 2)
    Access Point:
    Bit Rate: 11Mb/s
    Link Quality: 53/100 Signal: -62 dBm Noise: -96 dBm

    # iwconfig wlan0 mode Managed

    # iwconfig wlan0
    nothing changed

    # iwconfig wlan0 channel 2

    # iwconfig wlan0
    nothing changed

    # ifconfig
    wlan0: Link encap: Eterhent HWAddr
    inet6 addr: fe90::206:4fff:fe40:fb93/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric: 1
    RX packets: 591, TX: 37, errors: 0
    collisions: 0 txqueuelen:1000
    RX: 39 KiB, TX: 7.8 KiB
    Interrupt 10 Memory f4202000-f4202025




    >
    > > I can successfully connect to the network using Windows.

    >
    > Proving what...?


    That it is possible to connect to that AP using this card?


    Answering the previous post:
    > What is the WLAN access point at the other end of

    the wireless connection?

    It is my ISP, 802.11b, channel 2, no encryption, DHCP.
    I don't know more.


  5. Re: failure of dhcp

    On Wed, 14 Feb 2007 15:54:52 -0800, bbla32 wrote:

    >> In my experience, setting mode to Managed will reset the essid
    >> assignment..:

    >
    > here it didn't


    Your output says otherwise... But since you missed the point we wanted,
    who can tell?

    Please follow exactly these steps:

    iwconfig wlan0 mode Managed
    iwconfig wlan0 essid
    iwconfig wlan0

    And please give us the output of the last command..!

    >> Why do you set the channel on the client?

    >
    > just in case..


    At best, it doesn't matter, at worst, it will introduce errors. Please
    don't!

    What kind of WLAN card, (make, model and version), are you using, since
    you use ndiswrapper?

    BTW: So far, this looks more like a driver, wireless tools or association
    problem, not a DHCP problem.

    --
    Regards/mvh Joachim Mæland

    If everything seems under control, you're just not going fast enough.
    -Mario Andretti.


  6. Re: failure of dhcp

    > Please follow exactly these steps:
    >
    > iwconfig wlan0 mode Managed
    > iwconfig wlan0 essid
    > iwconfig wlan0


    exactly the same as before:

    wlan0 IEEE 802.11b ESSID:
    Mode:Managed Freq:2.417 GHz Access Point:
    Bit Rate: 11 Mb/s Tx-Power: 26 dBm Sensitivity=0/3
    RTS thr: 2432 B Fragment thr: 2432 B
    Encryption key: off
    Power Management: off
    Link Quality:53/100 Signal: -62 dBm Noise: -96 dBm
    RX invalid nwid:0 Rx invalid crypt: 0 Rx inv. frag: 0
    Tx excessive retries: 0 Inv. misc:0 Missed beacon: 0


    > What kind of WLAN card, (make, model and version), are you using, since
    > you use ndiswrapper?


    WALN card: Pentagram Hornet PCI WIFI Lite
    Chipset: Realtek 8185
    (rtl8180-sa2000 driver hangs the system; Realtek's Linux driver for
    8185 hangs the system too).
    Kernel: Fedora Core 6, 2.6.18.1, recompiled to enable 8 kB stacks
    (before it would hang with ndiswrapper too).
    ndiswrapper v. 1.31

    When systems starts, I have one failure:
    - starting HIDD: Can't open HIDP controlsocket: Address family not
    supported by protocol
    I don't know whether it's anything important.


    > BTW: So far, this looks more like a driver, wireless tools or association
    > problem, not a DHCP problem.


    What wireless tools?
    But iwconfig shows the card sends and receives, and it detects the
    available networks.


+ Reply to Thread