Results 1 to 8 of 8

Thread: Yet Another Networking Issue Thread!

  1. #1
    Just burned his ISO
    Join Date
    Oct 2010
    Posts
    3

    Default Yet Another Networking Issue Thread!

    I don't know if my other thread got deleted or it just didnt post...
    So Ill post this one more time

    Ive got an HP pavilion dv6000; brand new out of the box
    It has an Intel Wifi Link 1000 bgn wireless adapter...

    I cant get networking to start!

    In BT4 starting networking results in this:
    Code:
    Configuring network interfaces...Internet Systems Consortium DHCP Client V3.1.1
    Copyright 2004-2008 Internet Systems Consortium.
    All rights reserved.
    For info, please visit http://www.isc.org/sw/dhcp/
    
    Listening on LPF/eth0/60:eb:69:23:65:e0
    Sending on   LPF/eth0/60:eb:69:23:65:e0
    Sending on   Socket/fallback
    DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
    DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
    DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
    DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
    DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
    No DHCPOFFERS received.
    No working leases in persistent database - sleeping.
    if-up.d/mountnfs[eth0]: waiting for interface eth1 before doing NFS mounts
    if-up.d/mountnfs[eth0]: waiting for interface eth2 before doing NFS mounts
    if-up.d/mountnfs[eth0]: waiting for interface ath0 before doing NFS mounts
    if-up.d/mountnfs[eth0]: waiting for interface wlan0 before doing NFS mounts
    eth1: ERROR while getting interface flags: No such device
    Internet Systems Consortium DHCP Client V3.1.1
    Copyright 2004-2008 Internet Systems Consortium.
    All rights reserved.
    For info, please visit http://www.isc.org/sw/dhcp/
    
    SIOCSIFADDR: No such device
    eth1: ERROR while getting interface flags: No such device
    eth1: ERROR while getting interface flags: No such device
    Bind socket to interface: No such device
    Failed to bring up eth1.
    eth2: ERROR while getting interface flags: No such device
    Internet Systems Consortium DHCP Client V3.1.1
    Copyright 2004-2008 Internet Systems Consortium.
    All rights reserved.
    For info, please visit http://www.isc.org/sw/dhcp/
    
    SIOCSIFADDR: No such device
    eth2: ERROR while getting interface flags: No such device
    eth2: ERROR while getting interface flags: No such device
    Bind socket to interface: No such device
    Failed to bring up eth2.
    ath0: ERROR while getting interface flags: No such device
    Internet Systems Consortium DHCP Client V3.1.1
    Copyright 2004-2008 Internet Systems Consortium.
    All rights reserved.
    For info, please visit http://www.isc.org/sw/dhcp/
    
    SIOCSIFADDR: No such device
    ath0: ERROR while getting interface flags: No such device
    ath0: ERROR while getting interface flags: No such device
    Bind socket to interface: No such device
    Failed to bring up ath0.
    SIOCSIFFLAGS: No such file or directory
    Internet Systems Consortium DHCP Client V3.1.1
    Copyright 2004-2008 Internet Systems Consortium.
    All rights reserved.
    For info, please visit http://www.isc.org/sw/dhcp/
    
    SIOCSIFFLAGS: No such file or directory
    SIOCSIFFLAGS: No such file or directory
    Listening on LPF/wlan0/00:26:c7:8c:b2:dc
    Sending on   LPF/wlan0/00:26:c7:8c:b2:dc
    Sending on   Socket/fallback
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    send_packet: Network is down
    receive_packet failed on wlan0: Network is down
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
    send_packet: Network is down
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
    send_packet: Network is down
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
    send_packet: Network is down
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
    send_packet: Network is down
    No DHCPOFFERS received.
    No working leases in persistent database - sleeping.
    if-up.d/mountnfs[wlan0]: waiting for interface eth1 before doing NFS mounts
    if-up.d/mountnfs[wlan0]: waiting for interface eth2 before doing NFS mounts
    if-up.d/mountnfs[wlan0]: waiting for interface ath0 before doing NFS mounts
    done.
    iwconfig outputs this:
    Code:
    iwconfig
    lo        no wireless extensions.
    
    eth0      no wireless extensions.
    
    wmaster0  no wireless extensions.
    
    wlan0     IEEE 802.11bgn  ESSID:""
              Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated
              Tx-Power=0 dBm
              Retry min limit:7   RTS thr:off   Fragment thr:off
              Encryption key:off
              Power Management:off
              Link Quality:0  Signal level:0  Noise level:0
              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
              Tx excessive retries:0  Invalid misc:0   Missed beacon:0
    ifconfig outputs this:
    Code:
    eth0      Link encap:Ethernet  HWaddr 60:eb:69:23:65:e0
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
              Interrupt:33 Base address:0xc000
    
    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:0 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
    and ifconfig wlan0 up gives me this:
    Code:
    SIOCSIFFLAGS: No such file or directory
    I can only assume thats because it isnt listed under ifconfig in the first place.

    Anyone give me a hand?

  2. #2
    Super Moderator lupin's Avatar
    Join Date
    Jan 2010
    Posts
    2,943

    Default Re: Yet Another Networking Issue Thread!

    Quote Originally Posted by exploitz View Post
    I can only assume thats because it isnt listed under ifconfig in the first place.
    You assume? If you Googled the error message you might be able to do more than assume.

    Perhaps you should also do some reading on how to configure a wireless card under Linux.
    Capitalisation is important. It's the difference between "Helping your brother Jack off a horse" and "Helping your brother jack off a horse".

    The Forum Rules, Forum FAQ and the BackTrack Wiki... learn them, love them, live them.

  3. #3
    Just burned his ISO
    Join Date
    Oct 2010
    Posts
    3

    Default Re: Yet Another Networking Issue Thread!

    Ive had networking properly configured on my old PC.. but I havent used BT in a long while now, yet alone even booted into any linux distro lately.

    I followed a tutorial here:
    Quick HOWTO : Ch13 : Linux Wireless Networking - Linux Home Networking

    and it asked me to restart the wpa_supplicant service, but when I tried I got service not found.. I am no linux guru so I really don't know what to do now.

    I feel like I was pretty close with that guide.. Lupin, was that what I needed to do?

  4. #4
    Member
    Join Date
    Dec 2007
    Location
    The Netherlands
    Posts
    267

    Default Re: Yet Another Networking Issue Thread!

    It's listed under iwconfig, so that's a good sign. It might also be listed under ifconfig, but only if you use the -a switch.
    Anyhow, starting the networking sends out some dhcp packets, which is great for wired networks, but won't work for shit on your wireless card (because it is not associated to an access point yet).

    Anyhow, backtrack has a wireless gui (Wicd I think it's called), so try that.

  5. #5
    Just burned his ISO
    Join Date
    Oct 2010
    Posts
    3

    Default Re: Yet Another Networking Issue Thread!

    Ive started wicd and when it loads it only says something about not finding any networks.

    There are about 15 networks around me.. so I know something is up.

    Any other ideas...?

  6. #6
    Member
    Join Date
    Dec 2007
    Location
    The Netherlands
    Posts
    267

    Default Re: Yet Another Networking Issue Thread!

    Try iwconfig wlan0 up (from memory, It's been a while)
    Student Systems Administration and Network Engineering, second year.
    Don't PM me with questions, unless very specific. Otherwise, use the forums so everyone can potentially benefit from it.

  7. #7
    Just burned his ISO
    Join Date
    Oct 2010
    Location
    Australia
    Posts
    13

    Default Re: Yet Another Networking Issue Thread!

    I'm new to linux, but I've quickly learnt not to trust wicd.

    Reboot and try:

    ifconfig wlan0 up
    airodump-ng wlan0

    airodump-ng is another way of scanning for networks and more importantly it doesn't rely on wicd.

    What do you get when you try?: lshw -C network

  8. #8
    Just burned his ISO
    Join Date
    Oct 2010
    Location
    Australia
    Posts
    13

    Default Re: Yet Another Networking Issue Thread!

    Quote Originally Posted by Citruspers View Post
    Try iwconfig wlan0 up (from memory, It's been a while)
    Your close the correct command is ifconfig wlan0 up

Similar Threads

  1. Networking Issue & Other Minor Issues
    By Killians31 in forum Beginners Forum
    Replies: 8
    Last Post: 03-24-2010, 10:14 PM
  2. No networking on eee pc 901
    By hacktivist in forum OLD BackTrack 4 NON working hardware
    Replies: 4
    Last Post: 06-29-2009, 12:24 PM
  3. my first thread
    By lovergirlxoxo in forum OLD Newbie Area
    Replies: 4
    Last Post: 05-15-2009, 07:36 PM
  4. Airodump-ng Issue + Aireplay-ng Issue
    By whiteice in forum OLD Newbie Area
    Replies: 1
    Last Post: 11-05-2008, 05:47 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •