How to forward TCP/IP packet over UART connecton? - esp8266

On one end is my ESP8266-01 Wi-Fi module and on the other end is Beaglebone black (not wireless) and ESP module has only UART pins. I want to transfer IP packets over UART line so that I can see Beaglebone as and separate device (probably with it's own IP address).

Related

Questions of wireshark packet capturing(promiscuous vs monitor mode)

After setting up promiscuous mode on my wlan card, I started capturing packets with wireshark. But only broadcast packets or packets destined to my localhost were captured. I cannot find the reason why.
Also, after changing to monitor mode, captured packets all had 802.11 headers unlike promiscuous mode where Ethernet frames were captured. I know devices communicate with 802.11 protocols when wireless. But how is it possible that packets captured in wireshark is displayed in Ethernet frames? (when not in monitor mode)

USB Pcap Wireshark - ''1.1.3'' What this address mean?

I am exploring the world of USB packet capturing.
after a capture session from my USB SubZero device
I understand the data captured but don't understand the address.
Wireshark say '1.1.3' in the address and USB URB in other field.Is not a COM port like i hope it would be cause in effect
in device manager The SUBZERO is not recognized with a COM port and is under the AUDIO,GAMES... peripherics.
What to do if I want to send data to this address.

Wireshark Displayed Packets

I am a Wireshark learner and currently I am using Tshark to sniff my network packages. Currently my local IP is 192.168.0.114 and my collegue is 192.168.0.102.
However when I start capturing packets, I receive some packets with source IP 192.168.0.102 and destination IP 192.168.0.255. I am not the sender nor the receiverWhy am I seeing those packets? Here is my code just in case>
capture = pyshark.LiveCapture(interface='eth0')
capture.sniff(timeout=50)
capture
192.168.0.255 seems to by the broadcast IP address : 192.168.0.102 send this message to all other hosts on the network, your computer is receiving it as a member of this subnet.
The mask is probably 255.255.255.0 :)

Send udp message outside of subnet

i am trying to communicate with FPGA board, on which basic UDP protocol was implemented. i use windows 7 PC, python 2.7.6 32 bit.
my computer is connected to LAN network. automatically receives this IP (from ipconfig): IP 192.168.2.1, Subnet mask: 255.255.255.0
my board is connected to to my computer with a switch. IP of the board is fixed (in hardware code) - 192.168.4.10.
if i understand currectly - my computer and my board are on different subnets, because 2 of the 4 right ip sub-numbers are different.
when i send UDP packet - card does not receive it. when i manually force my computer to be the same ip (192.168.2.1) but 255.255.0.0 subnet mask, it does receive.
python code i use for sending is something like this:
import socket
UDP_IP = "192.168.4.10"
RECEIVE_PORT = 5005
SEND_PORT = 5005
MESSAGE = "Hello, World!"
sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
sock .bind(('', SEND_PORT))
sock.sendto(MESSAGE, (UDP_IP, RECEIVE_PORT))
what could be the reason?
is there any way i can fix this in code?
is there any way i can change my subnet mask in code?
what should i read to understand my problem?
Actually you should use "IP address alias" to have both of 192.168.2.1/255.255.255.0 and, say, 192.168.4.1/255.255.255.0 on a single Ethernet port on your PC:
http://www.unixwerk.eu/linux/redhat/ipalias.html
How to create an IP alias on Windows
What happened when you sent a UDP datagram to 192.168.4.10 from 192.168.2.1/255.255.255.0:
The network addresses of your PC and the destination were different: 192.168.4.0 vs 192.168.2.0
Therefore your PC assumed it had to ask the gateway router to appropriately deliver the datagram somewhere remote, and sent it to the router (the details on how to do so don't matter here)
I guess your router knew nothing about the 192.168.4.0 network and had to discard the datagram
What happened when you sent a UDP datagram to 192.168.4.10 from 192.168.2.1/255.255.0.0:
The network addresses of your PC and the destination agreed: 192.168.0.0
So your PC assumed it didn't have to bother the gateway router and could directly talk to it
Then the next step was to query the recipient's MAC address by ARP (Address Resolution Protocol.) It simply uses Ethernet broadcast to ask all the devices connected to your LAN who is the owner of 192.168.4.10
As there's no notion of subnet in ARP/Ethernet, your FPGA NIC simply replied something like "Yes, I have 192.168.4.10. Call me at d8:cb:8a:f0:0b:aa"
Your PC could send a UDP datagram to d8:cb:8a:f0:0b:aa
FYI: a similar process must have happened before your PC could talk to the gateway router.

Wireshark and wifi monitor mode failing

I want to sniff wifi packets with wireshark but monitor mode seems to fail. I'm using backtrack 5 and an alpha AWUS036H wifi usb card, i try to sniff my own box without encryption.
Here is what i'm doing to activate monitor mode :
root#root:~# airmon-ng start wlan0
wich seems to be working :
root#root:~# iwconfig mon0
mon0 IEEE 802.11bg Mode:Monitor Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:on
However when i start capturing on mon0 in wireshark i'm only getting broadcast packets.
In capture options the "capture packets in monitor mode" option is grayed out.
I do not understand what's going on. Any Ideas ?
What channel number is your mon0 interface set to?

Resources