Backtrack 4 Wireless Not Working [closed] - linux

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I'm trying to connect to my wireless network on Backtrack 4. I have a Dell Studio 1558.
ifconfig and ifup show the wlan0 interface is up.
I ran
/etc/init.d/networking start
/etc/init.d/wicd
in a terminal, but when I open the network manager (menu > internet > wcid network manager), it says that no wireless networks are found.
Is this a driver issue? Does anyone know how to get wireless working?

You can go and check the wcid network manager for the name of the wireless device if you have wlan0.
Try over terminal with
.
ifconfig wlan0 down
ifconfig wlan0 up

There have been wireless issues in BT4, either upgrade to BT5 or have a look here in the Backtrack forums as there's loads of information there such as this link on wireless issues in BT5 - http://www.backtrack-linux.org/forums/showthread.php?t=43597.
What do you see in /cat var/log/wicd/wicd.log?
What does airmon-ng report?

Related

Cannot connect to my raspberry pi anymore [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I wanted to use my android phone as a display for my Raspberry Pi 4B, so I searched the internet, found an instruction and copied the code into my Pi, I was connected to (via SSH). This is the code I put into /etc/network/interfaces:
iface usb0 inet static
address 192.168.42.42
netmask 255.255.255.0
network 192.168.42.0
broadcast 192.168.42.255
This sets the IP to a static one (192.168.42.42).
I rebooted and tried to SSH with IP 192.168.42.42, because I thought, this was the new IP for the Raspberry Pi.
Long story short, it doesn't work. I also tried some other IP's, I cant find the IP in NUTTY or with nmap.
How can I connect to my PI now? (I don't have a monitor or a crossover LAN cable)
I'm using an older MacBook Pro with Linux Mint 19
Where I got the code from: https://joshuawoehlke.com/android-raspberry-pi-display-over-usb/
You could take the SD card out of the Pi and put it in your Mac/Linux machine and correct/remove the /etc/network/interfaces file from the SD card.
Or, you could go to the SD card's /boot partition and touch ssh in that directory so that sshd starts and also create in that same directory a wpa_supplicant file to match a temporary WiFi hotspot you create on your phone or Mac. Then you can ssh into it over WiFi and whatever you want.

How can I connect to internet with wireless USB adapter in Fedora 20? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 8 years ago.
Improve this question
I am at the stage of learning Linux.
I have just installed Fedora20, but I cannot connect to internet with
my Wireless USB adapter....
Can anyone help me to use internet in Linux fedora 20?
This question is probably going to get migrated to somewhere like Super User, but just to give you a starting point, does the Wireless adapter register as an interface? Run ifconfig -a on the terminal and look out for a wlan0.
Then run ifconfig wlan0 up, and you can then do iw dev wlan0 scan to list access points that the card can see. You can then do some Googling about connecting a wireless card using wpa-supplicant.
If you can't see a wlan0 interface in ifconfig it could be that you don't have the drivers for your Wifi card. You'll need to Google which drivers are required and you might be able to get a kernel module or driver binary from somewhere on the internet.

predefined cell ID assignment for an ad-hoc wlan [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I have a debian/ubuntu boards that I connect them via an ad-hoc network with the following settings
board:~# cat /etc/network/interfaces
auto wlan0
iface wlan0 inet static
address 10.0.0.2
netmask 255.255.255.0
wpa-driver nl80211
wpa-conf /etc/wpa_supplicant.conf
board:~# cat /etc/wpa_supplicant.conf
# IBSS/ad-hoc network with WPA-None/TKIP.
ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
network={
ssid="adhoc_test"
mode=1
frequency=2412
proto=WPA
key_mgmt=WPA-NONE
pairwise=NONE
group=TKIP
psk="abcdefgh"
bssid=F8:D1:11:52:0C:4E
}
These configurations creates an ad-hoc wlan, however, the nodes often gets different cell ID so that they cannot communicate with each other. To prevent it I added bssid=F8:D1:11:52:0C:4E line, however, no node get this predefined cell ID when they get the cell ID.
My question is that how can I prevent nodes to get different cell IDs? why bssid line does not work in the ad-hoc mode?
P.S. I tried these settings on ubuntu and debian dist. that have 3.2 and 3.4 kernels. wpa_supplicant versions that I used were 0.7, 1.0, and 2.0 all did not work. For the chipset, I am using Atheros AR9271 chipset for the wifi module.
Use ap_scan=2 and remove the bssid= line from the configuration.
the problem was that previous versions of wpa_supplicant does not support the bssid, installing wpa_Supplicant 2.0 solved the problem!
I answered same question at https://superuser.com/questions/552935/while-using-ad-hoc-networking-how-to-i-force-nodes-to-use-the-same-cell-ids-bs/569860#569860
Simple version: after ad-hoc configuration:
sudo iwconfig ath0 ap 11:22:33:44:55:66

How to avoid mac in rhel6 changes on every reboot? [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I have a NVIDIA Corporation MCP61 Ethernet which mac address changes eveytime I reboot my box.
[root#sun etc]# dmesg |grep eth0
forcedeth 0000:00:07.0: ifname eth0, PHY OUI 0x732 # 1, addr 66:b6:95:ea:3e:29
udev: renamed network interface eth0 to eth3
udev: renamed network interface eth0 to eth1
This time it's 66:b6:95:ea:3e:29. How to avoid this?
This is offtopic for here, but its a known bug for a long time. See this extensive discussion at Ubuntu's bugtracker.
It also has a fix proposed some 10 years back.
I know its Ubuntu's bugtracker, but the problem is with the linux kernel drivers. The link there will lead you to some work arounds to solve the problem.

MAC address randomly changes when bringing interface up [closed]

Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
Every time I start my network interface, I get a different MAC address! If I try to force the MAC address value using
ifconfig usb0 hw ether AA:BB:DD..:FF
it will be again different after issuing
ifconfig usb0 up
What make this MAC address change? How can I stop this to happen and stick to HW burned MAC address?
I am using a panda board (omap4/armv7) on a angtrom distribution. The inteface is a smsc95xx USB 2.0 Ethernet.
Thanks,
Fabrice.
There is an issue with the smsc95xx driver.
[PATCH] smsc95xx: generate random MAC address once, not every ifup
There is also something in the work to get a 'repeatable' MAC generation going, but it didn't get much uptake:
Beagleboard xM smsc95xx MAC address from die id
Edit just searching for smsc95xx mac address gives a ton of competing patches, with some more explanations (the smc hub+NIC frequently doesn't have an EEPROM, so also no MAC)
MAC addresses are typically coded in the chipset, but mutable.
It might be that your distro is randomising it for security reasons.

Resources