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
Related
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 6 years ago.
Improve this question
when I put this in the terminal
ifconfig eth0 69.69.69.69
the ip address in the terminal change but in the user interface not, I mean
initial state
my ip is 192.168.10.2
then a put in the terminal
ifconfig eth0 69.69.69.69
and this happens
terminal
properties
As we can see the properties didn't change.
what can I do for change that properties using the terminal or a bash?
You are probably using a Linux distribution that uses the NetworkManager daemon, and during installation it decided that eth0 should be configured via DHCP. So every time you manually setup its IP not using it (from a terminal in your case), NetworkManager will set it up again without noticing you within a few seconds or minutes.
To check if you have indeed NetworkManager running and managing eth0 setup, issue:
ps aux | grep -i networkmanager
If it is indeed running, look for more info about it, from Ubuntu for instance:
https://help.ubuntu.com/community/NetworkManager
...and then google around for "network manager manual setup ip".
PS:
I hate NetworkManager with a deep passion, gave up using it years ago and always uninstall it, managing my interfaces manually and/or the good old /etc/network/interfaces way. Noticeably (in my case) it can be a pure nuisance when multihoming and changing the interfaceS setup frequently. So if this is indeed your problem (90% sure) I can't help you much more with it. NetworkManager is good at managing one interface at a time, with one configuration (ex static or DHCP) for each interface. This satisfy 95% of user cases. But not mine.
i have try this in my computer and i have success
ifconfig eth0 192.168.218.110
if you want to chang the /etc/sysconfig/network-scripts/ifcfg-eth0 to chang the ip.
you can use vim edit chang thhis line:IPADDR=192.168.218.111
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 4 years ago.
Improve this question
I am trying to force the Wi-Fi adapter to use a specific channel while connecting to the access point which supports both 2.4 GHz and 5 GHz (WPA authentication).
I am using the following configuration:
OS: Raspbian
Model: Raspberry Pi 2 Model B
Wi-Fi Adapter: Edimax EW-7811UTC
Driver: 8812au
I also tried with a different Wi-Fi adapter: Asus USB-N53 using driver rt2800.
Tried with iwconfig which is giving SET failed on device wlan0 ; Operation not supported.
Also tried wpa_supplicant.
What extra arguments need to be given to the wpa_cli or wpa_supplicant utility so that the Wi-Fi adapter will connect only to the specific band?
look for your interface
sudo iwconfig
look at your channels
sudo iwlist {interface} channel
turn off wifi
sudo iwconfig {interface} power off
set your desired channel
sudo iwconfig {interface} channel {channel, ex. "23"}
set your desired frequency
sudo iwconfig {interface} freq {frequency, ex. "5.00G"}
turn on wifi
sudo iwconfig {interface} power on
You can't do that. The channel is selected automatically in the 2.4 or 5GHz band because the channel depends on your router: The router selects a channel and your client simply uses it. There is no way for the client to tell the router "please switch to band 13".
The 2.4 and 5GHz bands are usually selected by the network name; your router should offer two WLAN names.
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
My goal is to change the IP address of USB0.
The Beagle Bone Black run Debian.
I tryed to change /etc/network/interfaces such that default address is 192.168.7.3 instead of 192.168.7.2 as this:
iface usb0 inet static
address 192.168.7.3
netmask 255.255.255.0
network 192.168.7.0
gateway 192.168.7.1
After running
/etc/init.d/networking restart
It was still on 192.168.7.2.
I tryed rebotting, and yet is to no avail.
I tryed to change the IP address in /boot/uboot/scripts/setup-ubuntu-armhf-3.8.13-bone30.sh, but basicly this file overwrites /etc/network/interfaces.
Still after reboot the IP is still 192.168.7.2.
Edit:
Also tryed to change the IP in:
/media/Angstrom/usr/bin/g-ether-load.sh
/media/Angstrom/etc/udev/rules.d/udhcpd.rules
Which didn't work.
Tryed to change it in:
/opt/scripts/boot/am335x_evm.sh
And now the network is unreachable:
ssh: connect to host 192.168.7.3 port 22: Network is unreachable
I was having the same problem on:
BeagleBoard.org Debian Image 2017-03-19
The issue turned out to be "connmand" (read it again, it starts with coNN, not comm). It is a horribly named program as it is difficult to research as Google assumed you spelled something wrong.
connman automatically configures wired instances for dhcp despite what is listed in /etc/network/interfaces.
Recommend either disabling it, or adding your interface to be ignored:
/etc/connman/main.conf:
NetworkInterfaceBlacklist=SoftAp0,usb0,usb1,eth0
After doing that and restarting, my static IP configured for eth0 in /etc/network/interfaces started working.
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.
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?