If I try to run the program in two separate machines AND I apply the rules above for the ppp0 connection (I have not removed it), I can no longer see any output from server.py but can still see packets arriving on Wireshark. If I try to run the program in two (client and server) separate machines (without applying the rules), I can see the packets arriving at eth1 in Wireshark, and the output on server.py. Ignoring the ppp0 interface and using two ethx interfaces: I cannot see any output from server.py after restarting the program.I can see the packets on Wireshark now arriving at eth1, the source address is the address of the WAN (172.16.20.2).Now we do not see the interfaces that we have seen from the previous. Now launch Wireshark from the command line. First of all, we need to see how many interfaces are there in our Linux PC. Sudo ip route add table local 172.16.20.1 dev ppp0 No Interfaces are listed in Wireshark: Step1. When I add the following rules to prevent this from happening: sudo ip route del table local 172.16.20.1 dev eth1 I assume the OS has detected the packet is for one of its local interface and does not send it through the 192.168.0.2 socket created. The script works fine but I cannot see the packet on Wireshark coming out of eth1 (I can only see it when I choose to capture on the lo interface).
Srv = socket.socket(socket.AF_INET, socket.SOCK_DGRAM) The problem I am having is if I send a packet using Python on the same machine: client.py import socketĬl = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)Ĭl.sendto("Hello", ("172.16.20.1", 5005))
I can verify that this device can reach 172.16.20.1 Ppp0 is connected to a device which has a PPP interface (192.168.0.1) and a WAN interface (172.16.20.2). I have a Linux machine where there are two interfaces:
0 kommentar(er)
