bridging wlan0 in ad-hoc mode linux - ubuntu-14.04

I am facing some problem in adding wlan0 interface to Bridge in “Ad-hoc” mode. While same is working well in “managed” mode. Although adding wlan in managed mode was not straight forward but googling, I found some workaround for managed mode:
$sudo iw dev wlan0 set 4addr off
$sudo iw dev wlan0 set 4addr on
$sudo brctl addbr br0
$sudo brctl addif br0 wlan0
While running same sequence of commands for “ad-hoc” mode goes as follows:
$sudo iw dev wlan0 set 4addr off
$sudo iw dev wlan0 set 4addr on
command failed: Operation not supported (-95)
$sudo brctl addbr br0
$sudo brctl addif br0 wlan0
can't add wlan0 to bridge br0: Operation not supported
Wireless adaptor is from Intel and below is the machine info where I am running commands:
Ubuntu 14.04.4 LTS with Linux xxxx 3.13.0-78-generic #122-Ubuntu SMP Mon Feb 1 23:11:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Any help is highly appreciated.
Thanks in advance.

Related

hcitool lescan returns an I/O error on Manjaro

I'm trying to connect MX Master 3 to my computer.
OS: Manjaro 21.2.1 Qonos
Kernel: x86_64 Linux 5.10.89-1-MANJARO
Computer: Dell XPS 7390
I tried:
sudo hcitool lescan
which gives:
Set scan parameters failed: Input/output error
rfkill list all gives:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
and hcitool dev gives:
Devices:
hci0 84:1B:77:B4:B4:D1
Things I have already tried:
hciconfig hci0 down
hciconfig hci0 up
sudo systemctl restart bluetooth.service
sudo systemctl restart dbus.service
Inside bluetoothctl:
menu scan
transport le
back
scan on
This resolved the problem.

SSH on Raspberry Pi3

I install "ubuntu-17.04-desktop-amd64" and "qt-opensource-linux-x64-5.8.0" on on my laptop.
I wrote an application with Qt 5.8 for windows. It works fine in windows and Ubuntu.
IP address of raspberry ("hostname -I"): 169.254.181.63
Enable SSH:
In raspberry: from Preferences menu of Rasbian.
In Ubuntu:
sudo service ssh status
....
.... Starting OpenBSD Secure Shell server.
.... Server listening on 0.0.0.0 port 22.
.... Server listening on :: port 22.
.... Started OpenBSD Secure Shell server.
I connect raspberry pi to laptop with Ethernet cable.
I create new device (Generic Linux Device) in "Tools -> Options…-> Devices tab"
Host name: 169.254.181.63
SSH port:22
Username: pi
Password: 1 (set by me)
Result test:
Device test: SSH connection: Network unreachable.
In Ubuntu:
ssh pi#169.254.181.63
ssh: connect to host 169.254.181.63 port 22: Network is unreachable
I edit the interface file to set the network configuration in raspberry:
sudo nano /etc/network/interfaces
Update:
source-directory /etc/network/interfaces.d
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 192.168.100.100
netmask 255.255.255.0
allow-hotplug wlan0
iface wlan0 inet manual
Update:
But after reboot raspberry and execute "hostname -I", I have "192.168.100.100 169.254.181.63"
You should configure a static IP in this way (see this link):
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 192.168.100.100
network 192.168.100.0
netmask 255.255.255.0
broadcast 192.168.200.25
You've to move address, netmask, etc. below the line iface eth0 inet static.
Check if your correct IP address is correct and use command in terminal. Open the terminal use this command and find the exact ip address:
cd /var/misc
cat misc
Copy this IP address and use this command:
ssh pi#ip_address
change the order. put the settings under iface eth0 not the lo.
iface eth0 inet manual
address 192.168.200.100
network 192.168.100.0
netmask 255.255.255.0
broadcast 192.168.200.25

connecting open vswitch with two virtual machines

I'm running an Open VSwitch on a VirtualBox VM,
i want to connect 2 VMs that are running on VirtualBox into OpenVswitch. i did these things:
1)first i made an VM running ubuntu (lubuntu), and installed ovs using the following command
sudo apt-get install openvswitch-switch
2)after that i defined 2 adapter on vm and determine them as Internal Network cause vms want to connect to these machine internally from virtual box
but how can i connect 2 virtualbox's VMs that are running on separate subnets (10.1.1.1 and 10.1.2.1) using this OVS?
the diagram is as follow:
http://www.gliffy.com/go/publish/image/10986491/L.png
I don't think you need to use OVS in this case, though you can achieve this by providing gateway ip.
Say suppose you have create internal network with subnet 192.170.10.0/24 as internal1 and other internal2 with subnet 192.170.20.0/24
Configuration on VM1:
auto eth0
iface eth0 inet static
address 192.170.10.10
network 192.170.10.0
netmask 255.255.255.0
broadcast 192.170.10.255
gateway 192.170.10.20
Configuration on VM2:
auto eth0
iface eth0 inet static
address 192.170.20.10
network 192.170.20.0
netmask 255.255.255.0
broadcast 192.170.20.255
gateway 192.170.20.20
Configuration on OVS:
auto eth0
iface eth0 inet static
address 192.170.10.20
network 192.170.10.0
netmask 255.255.255.0
broadcast 192.170.10.255
gateway 192.170.10.20
auto eth1
iface eth1 inet static
address 192.170.20.20
network 192.170.20.0
netmask 255.255.255.0
broadcast 192.170.20.255
gateway 192.170.20.20
Using above configuration you can ping between VMs on different subnet
However if you still want to use OVS, here is way to configure.
Configuration on VM1:
auto eth0
iface eth0 inet static
address 192.170.10.10
network 192.170.10.0
netmask 255.255.255.0
broadcast 192.170.10.255
Configuration on VM2:
auto eth0
iface eth0 inet static
address 192.170.20.10
network 192.170.20.0
netmask 255.255.255.0
broadcast 192.170.20.255
Configuration on OVS:
Set interface to load to manual in /etc/network/interfaces
auto eth0
iface eth0 inet manual
auto eth1
iface eth1 inet manual
Create Two bridges
sudo ovs-vsctl add-br vm1-br
sudo ovs-vsctl add-br vm2-br
Add respective ports.
sudo ovs-vsctl add-port vm1-br eth0
sudo ovs-vsctl add-port vm2-br eth1
Bridge the bridges using patch interface
sudo ovs-vsctl add-port vm1-br patch1
sudo ovs-vsctl set interface patch1 type=patch
sudo ovs-vsctl set interface patch1 options:peer=patch2
sudo ovs-vsctl add-port vm1-br patch2
sudo ovs-vsctl set interface patch2 type=patch
sudo ovs-vsctl set interface patch2 options:peer=patch1
Bring up the bridges
sudo ifconfig vm1-br up
sudo ifconfig vm-br up
Set the IP Address
sudo ifconfig vm1-br 192.170.10.20/24
sudo ifconfig vm2-br 192.170.20.20/24
Now you can ping between VMs

Packet looping on interfaces attached to linux bridge

I have added two ethernet interfaces on a linux bridge. I started seeing too many packets on the both connected interfaces by using tcpdump.
The tcpdump message is:
IP 0.0.0.0 > 224.0.0.1: igmp quer v2
The machine is virtual machine & has centos OS 6.3 installed.
What is the reason both the interfaces are getting flooded with the igmp packets continiously? Its sort of loop. How to solve this?
The procedure I followed:
brctl addbr mybr
brctl addif mybr eth0
brctl addif mybr eth1
ifconfig mybr up

signal strength adhoc mode ubuntu

Are there any possible ways to measure signal strength while two ubuntu machines are running in ad hoc mode. I have tried with iwspy command but it shows me error as follows.
root#dibya-notebook:~/Desktop# iwspy wlan0
wlan0 Interface doesn't support wireless statistic collection
root#dibya-notebook:~/Desktop# iwspy wlan0 wlan0 Interface doesn't support wireless
statistic collection
The above error is because your iwspy is not activated on your interface. If I remember correctly you can activate it specifying target IP address and NIC interface as,
sudo iwspy wlan0 <IP addr>
Also you can de-activate it by sudo iwspy wlan0 off.

Resources