network configuration.

Hi,

I have just received my Mesa 7i96s today from Mr. Andrew Beck of BECK CNC.

I left W4 and W5 at their default setting ( I can't see jumpers ) And I have followed the instructions given in this thread, and I am able to ping it.

This is what I have done:

With the Ethernet cable connected between Mesa 7i96s and Raspberry Pi4

[
behai@picnc:~ $ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DEFAULT group default qlen 1000
    link/ether d8:3a:dd:25:8c:37 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DORMANT group default qlen 1000
    link/ether d8:3a:dd:25:8c:38 brd ff:ff:ff:ff:ff:ff
]

I notice that eth0 shows <BROADCAST,MULTICAST,UP,LOWER_UP>

With the Ethernet cable disconnected:

[
behai@picnc:~ $ ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether d8:3a:dd:25:8c:37 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DORMANT group default qlen 1000
    link/ether d8:3a:dd:25:8c:38 brd ff:ff:ff:ff:ff:ff
]

I notice that eth0 shows <NO-CARRIER,BROADCAST,MULTICAST,UP>

So I guess my hardwired ethernet is eth0.

Then I log into my home router to verify that 192.168.1/24 is not in used as per the official manual instruction.

I then added the following lines into /etc/network/interfaces:

[
auto eth0
iface eth0 inet static
address 192.168.1.121
hardware-irq-coalesce-rx-usecs 0
]

Then I ran sudo ifdown -a followed by sudo ifup -a, both ran successfully. I.e. they produced no output.

Then finally: ping 192.168.1.121

The response is continuous until I pressed Control + C to interrupt.

I HAVE A QUESTION, PLEASE:

While the pinging was running, I disconnected the Ethernet cable, I expect the response to stop or at least to halt, but it did not. It continues to produce pinging notifications. Is this normal, please?

Thank you and best regards,

...behai.




 

Please watch my video

start at about 16 minutes in if you want to get to the section on networking

[
auto eth0
iface eth0 inet static
address 192.168.1.121
hardware-irq-coalesce-rx-usecs 0
]

if you ping  192.168.1.121, you are pinging the PC

I would not use the 192.xxx.xxx.xxx range, but rather set the 7I96s
to 10.10.10.10 = W4 down W5 up +power cycle and set the host address
to 10.10.10.100:

[
auto eth0
iface eth0 inet static
address 10.10.10.100
hardware-irq-coalesce-rx-usecs 0
]


 

rodw wrote:

Please watch my video

start at about 16 minutes in if you want to get to the section on networking
 

Hi,

Thank you very much for your suggestion, I did watch the entire video. I understand your explanation on the TCP/IP protocol.

Best regards,

...behai.

PCW wrote:

I would not use the 192.xxx.xxx.xxx range, but rather set the 7I96s
to 10.10.10.10 = W4 down W5 up +power cycle and set the host address
to 10.10.10.100:

[
auto eth0
iface eth0 inet static
address 10.10.10.100
hardware-irq-coalesce-rx-usecs 0
]

 

Hi,

Thank you for your reply. I would like to use 10.10.10.10 also: I have read the manual on this part and I have watch some set up vidoes for this card too. But I am not entirely certain about the jumpers. Please refer to the attached image:



To pull W4 down, do I just push that shiny piece pointed to by the green arrow down, please?

Thank you and best regards,

...behai.

To change the jumper position just pull the little link off and put it back on the top pin

Clive wrote:

To change the jumper position just pull the little link off and put it back on the top pin
 

Hi,

Thank you very much. I have been able to do this:



And I have changed the setting as per @PWC's instructions. The pinging appears to be correct now. When the network cable is disconnected in the middle of pinging, it reports ``Destination Host Unreachable`` which is what should happens. And when reconnected, it it picks it up again:

[
...
64 bytes from 10.10.10.10: icmp_seq=22 ttl=64 time=0.089 ms
64 bytes from 10.10.10.10: icmp_seq=23 ttl=64 time=0.090 ms
From 10.10.10.100 icmp_seq=24 Destination Host Unreachable
ping: sendmsg: No route to host
From 10.10.10.100 icmp_seq=25 Destination Host Unreachable
...
From 10.10.10.100 icmp_seq=31 Destination Host Unreachable
ping: sendmsg: No route to host
From 10.10.10.100 icmp_seq=32 Destination Host Unreachable
From 10.10.10.100 icmp_seq=33 Destination Host Unreachable
64 bytes from 10.10.10.10: icmp_seq=35 ttl=64 time=0.181 ms
...
64 bytes from 10.10.10.10: icmp_seq=38 ttl=64 time=0.098 ms
^C
--- 10.10.10.10 ping statistics ---
38 packets transmitted, 27 received, +9 errors, 28.9474% packet loss, time 37876ms
rtt min/avg/max/mdev = 0.078/0.105/0.225/0.032 ms, pipe 3
]

Thank you for your helps.

Best regards,

...behai.