Ah, I just realized if I had checked that earlier, this would have
solved my issue!
As you can see in the other answer, I just didn't realize that there is
a default network.
Thanks for the help! :)
Am 16.04.2018 um 23:29 schrieb Bob McMahon:
I'd look at three things on both ends
* ipta
It seems that I still have much to learn.
I uses the wifi as default network and that's why the modem couldn't
connect!
Changing the modem to the default network solved the problem and it now
works as expected.
Sorry for bothering you guys and thanks for your help!
Am 16.04.2018 um 23:20
I'd look at three things on both ends
- iptables -L (or firewall settings)
- routing tables (ip route show all)
- arp tables (arp -n) and the mac addresses (ifconfig)
to verify the end/end path. Also, if there are switches in the middle
dumping the switch address tables may be required
If memory serves me right, Marcel wrote:
> Hey Bruce,
>
> thanks for the fast reply.
>
> Actually I'm using a Python script and therefor I get the IP of the
> interface using netifaces.
>
> I also checked that using ifconfig while running the script and netstat
> -an showed the same IP.
>
> Her
Hey Bruce,
thanks for the fast reply.
Actually I'm using a Python script and therefor I get the IP of the
interface using netifaces.
I also checked that using ifconfig while running the script and netstat
-an showed the same IP.
Here was the output (using the IPs from before) while running
For iperf2, the -B doesn't bind to an interface but only sets the source ip
address in the packet. The routing tables decide the output interface.
https://sourceforge.net/p/iperf2/discussion/general/thread/f856ae2c/
Here's an article:
https://codingrelic.geekhold.com/2009/10/code-snippet-sobind
If memory serves me right, Marcel wrote:
> I'm trying to do an iperf3 test using a Huawei ME909 wwan modem on a
> raspberry pi zero w.
>
> I use the command as iperf3 -c 12.12.12.12 -t 3 -p 5201 -B 12.34.56.78
>
> where 12.12.12.12 is the ip of the server machine and 12.34.56.78 is the
> ip of t
