inband question

[gao weiwei]

大家好，我最近一直在研究 in-band 模式，我已经执行了 sudo util/install.sh -3f 命令来安装 bofuss。我想实现一个由 9 个 userAP 组成的网络，每个 userAP 都连接到一个主机 h。在我的拓扑中，有一个控制器在连接到 AP1 的主机 h1 上启动。但是，在我启动 ryu 控制器后，我无法从 AP 接收到数据包传入消息，因此无法在主机之间执行 ping。以下是 net、links 和 dump 命令的结果以及代码附件。谁能帮我找出这段代码中的问题并提供修改建议？

[Ramon Fontes]

Hello,

Inexplicably you don't answer a simple question: is bofuss working? Why don't you follow bofuss' instructions and check if its commands are working as expected?

Sent from my mobile device

On Mon, Dec 30, 2024, 07:00 gao weiwei <gao1817...@gmail.com> wrote:

大家好，我最近一直在研究 in-band 模式，我已经执行了 sudo util/install.sh -3f 命令来安装 bofuss。我想实现一个由 9 个 userAP 组成的网络，每个 userAP 都连接到一个主机 h。在我的拓扑中，有一个控制器在连接到 AP1 的主机 h1 上启动。但是，在我启动 ryu 控制器后，我无法从 AP 接收到数据包传入消息，因此无法在主机之间执行 ping。以下是 net、links 和 dump 命令的结果以及代码附件。谁能帮我找出这段代码中的问题并提供修改建议？

--
You received this message because you are subscribed to the Google Groups "mininet-wifi-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mininet-wifi-dis...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/mininet-wifi-discuss/b75e1b03-95e6-46e1-b90b-2422beefeb56n%40googlegroups.com.

[gao weiwei]

  Hello, I apologize for not clarifying whether bofuss is working. Regarding your suggestion to check if its commands are working as expected according to bofuss' instructions, I'm not sure how to perform the check. Is there any documentation available? Is it something like the following?  

sd-manet@sdmanet-virtual-machine:~/test$ ps aux | grep ofdatapath
root       35323  0.4  0.4 100712 37504 pts/2    S+   19:35   0:00 ofdatapath -i ap1-mp1 ap1-eth2 punix:/tmp/ap1 -d 100000000001 --no-slicing
root       35325  0.4  0.4 100712 37504 pts/4    S+   19:35   0:00 ofdatapath -i ap2-mp1 ap2-eth2 punix:/tmp/ap2 -d 100000000002 --no-slicing
root       35327  0.4  0.4 100708 37504 pts/6    S+   19:35   0:00 ofdatapath -i ap3-mp1 ap3-eth2 punix:/tmp/ap3 -d 100000000003 --no-slicing
root       35329  0.4  0.4 100708 37376 pts/8    S+   19:35   0:00 ofdatapath -i ap4-mp1 ap4-eth2 punix:/tmp/ap4 -d 100000000004 --no-slicing
root       35331  0.4  0.4 100704 37120 pts/10   S+   19:35   0:00 ofdatapath -i ap5-mp1 ap5-eth2 punix:/tmp/ap5 -d 100000000005 --no-slicing
root       35333  0.4  0.4 100712 37504 pts/12   S+   19:35   0:00 ofdatapath -i ap6-mp1 ap6-eth2 punix:/tmp/ap6 -d 100000000006 --no-slicing
root       35335  0.4  0.4 100708 37248 pts/14   S+   19:35   0:00 ofdatapath -i ap7-mp1 ap7-eth2 punix:/tmp/ap7 -d 100000000007 --no-slicing
root       35337  0.4  0.4 100708 37504 pts/16   S+   19:35   0:00 ofdatapath -i ap8-mp1 ap8-eth2 punix:/tmp/ap8 -d 100000000008 --no-slicing
root       35339  0.4  0.4 100712 37248 pts/18   S+   19:35   0:00 ofdatapath -i ap9-mp1 ap9-eth2 punix:/tmp/ap9 -d 100000000009 --no-slicing
sd-manet   35452  0.0  0.0  17756  2560 pts/23   S+   19:37   0:00 grep --color=auto ofdatapath
sd-manet@sdmanet-virtual-machine:~/test$ ps aux | grep ofprotocol
root       35324  0.0  0.0   3148  2304 pts/2    S+   19:35   0:00 ofprotocol unix:/tmp/ap1 tcp:10.0.0.1:6653 --fail=closed --listen=punix:/tmp/ap1.listen
root       35326  0.0  0.0   3148  2304 pts/4    S+   19:35   0:00 ofprotocol unix:/tmp/ap2 tcp:10.0.0.1:6653 --fail=closed --listen=punix:/tmp/ap2.listen
root       35328  0.0  0.0   3148  2304 pts/6    S+   19:35   0:00 ofprotocol unix:/tmp/ap3 tcp:10.0.0.1:6653 --fail=closed --listen=punix:/tmp/ap3.listen
root       35330  0.0  0.0   3148  2304 pts/8    S+   19:35   0:00 ofprotocol unix:/tmp/ap4 tcp:10.0.0.1:6653 --fail=closed --listen=punix:/tmp/ap4.listen
root       35332  0.0  0.0   3148  2304 pts/10   S+   19:35   0:00 ofprotocol unix:/tmp/ap5 tcp:10.0.0.1:6653 --fail=closed --listen=punix:/tmp/ap5.listen
root       35334  0.0  0.0   3148  2432 pts/12   S+   19:35   0:00 ofprotocol unix:/tmp/ap6 tcp:10.0.0.1:6653 --fail=closed --listen=punix:/tmp/ap6.listen
root       35336  0.0  0.0   3148  2304 pts/14   S+   19:35   0:00 ofprotocol unix:/tmp/ap7 tcp:10.0.0.1:6653 --fail=closed --listen=punix:/tmp/ap7.listen
root       35338  0.0  0.0   3148  2432 pts/16   S+   19:35   0:00 ofprotocol unix:/tmp/ap8 tcp:10.0.0.1:6653 --fail=closed --listen=punix:/tmp/ap8.listen
root       35340  0.0  0.0   3148  2304 pts/18   S+   19:35   0:00 ofprotocol unix:/tmp/ap9 tcp:10.0.0.1:6653 --fail=closed --listen=punix:/tmp/ap9.listen
sd-manet   35454  0.0  0.0  17756  2560 pts/23   S+   19:37   0:00 grep --color=auto ofprotocol

Ramon Fontes <ramonre...@gmail.com> 于2024年12月30日周一 18:05写道：

[Ramon Fontes]

Did you try dpctl? Isn't it more appropriate for such tests? https://github.com/CPqD/ofsoftswitch13?tab=readme-ov-file#configuring

[gao weiwei]

  Hello, I checked with dpctl and found that the AP is not connected to the controller. Could it be an issue with my configuration? How should I modify it? And when I use the command sudo ofdatapath --datapath-id=0000000000000001 --interfaces=ens33 ptcp:6633, I get an error as well.  How should I modify it? Can you help me?

  mininet-wifi> dpctl tcp:10.0.0.1:6653
*** ap1 ------------------------------------------------------------------------
Jan 14 14:56:17|00001|vconn_tcp|ERR|tcp:10.0.0.1:6653: connect: Network is unreachable
dpctl: Error connecting to switch tcp:10.0.0.1:6653. (Network is unreachable)
*** ap2 ------------------------------------------------------------------------
Jan 14 14:56:17|00001|vconn_tcp|ERR|tcp:10.0.0.1:6653: connect: Network is unreachable
dpctl: Error connecting to switch tcp:10.0.0.1:6653. (Network is unreachable)
*** ap3 ------------------------------------------------------------------------
Jan 14 14:56:17|00001|vconn_tcp|ERR|tcp:10.0.0.1:6653: connect: Network is unreachable
dpctl: Error connecting to switch tcp:10.0.0.1:6653. (Network is unreachable)
*** ap4 ------------------------------------------------------------------------
Jan 14 14:56:17|00001|vconn_tcp|ERR|tcp:10.0.0.1:6653: connect: Network is unreachable
dpctl: Error connecting to switch tcp:10.0.0.1:6653. (Network is unreachable)
*** ap5 ------------------------------------------------------------------------
Jan 14 14:56:17|00001|vconn_tcp|ERR|tcp:10.0.0.1:6653: connect: Network is unreachable
dpctl: Error connecting to switch tcp:10.0.0.1:6653. (Network is unreachable)
*** ap6 ------------------------------------------------------------------------
Jan 14 14:56:17|00001|vconn_tcp|ERR|tcp:10.0.0.1:6653: connect: Network is unreachable
dpctl: Error connecting to switch tcp:10.0.0.1:6653. (Network is unreachable)
*** ap7 ------------------------------------------------------------------------
Jan 14 14:56:17|00001|vconn_tcp|ERR|tcp:10.0.0.1:6653: connect: Network is unreachable
dpctl: Error connecting to switch tcp:10.0.0.1:6653. (Network is unreachable)
*** ap8 ------------------------------------------------------------------------
Jan 14 14:56:17|00001|vconn_tcp|ERR|tcp:10.0.0.1:6653: connect: Network is unreachable
dpctl: Error connecting to switch tcp:10.0.0.1:6653. (Network is unreachable)
*** ap9 ------------------------------------------------------------------------
Jan 14 14:56:17|00001|vconn_tcp|ERR|tcp:10.0.0.1:6653: connect: Network is unreachable
dpctl: Error connecting to switch tcp:10.0.0.1:6653. (Network is unreachable)
mininet-wifi> dpctl unix:/tmp/ap1 stats-flow
*** ap1 ------------------------------------------------------------------------
dpctl: Error parsing flow_stat arg: unix:/tmp/ap1.listen.
*** ap2 ------------------------------------------------------------------------
dpctl: Error parsing flow_stat arg: unix:/tmp/ap2.listen.
*** ap3 ------------------------------------------------------------------------
dpctl: Error parsing flow_stat arg: unix:/tmp/ap3.listen.
*** ap4 ------------------------------------------------------------------------
dpctl: Error parsing flow_stat arg: unix:/tmp/ap4.listen.
*** ap5 ------------------------------------------------------------------------
dpctl: Error parsing flow_stat arg: unix:/tmp/ap5.listen.
*** ap6 ------------------------------------------------------------------------
dpctl: Error parsing flow_stat arg: unix:/tmp/ap6.listen.
*** ap7 ------------------------------------------------------------------------
dpctl: Error parsing flow_stat arg: unix:/tmp/ap7.listen.
*** ap8 ------------------------------------------------------------------------
dpctl: Error parsing flow_stat arg: unix:/tmp/ap8.listen.
*** ap9 ------------------------------------------------------------------------
dpctl: Error parsing flow_stat arg: unix:/tmp/ap9.listen.

sd-manet@sdmanet-virtual-machine:~/test$ sudo ofdatapath --datapath-id=0000000000000001--interfaces=ens33 ptcp:6633
ofdatapath: argument to -d or --datapath-id must be exactly 16 hex digits

[Ramon Fontes]

Hello, I checked with dpctl and found that the AP is not connected to the controller. Could it be an issue with my configuration?

Firstly you have to make sure that you have bofuss working correctly.

 

How should I modify it? And when I use the command sudo ofdatapath --datapath-id=0000000000000001 --interfaces=ens33 ptcp:6633, I get an error as well.  How should I modify it? Can you help me?

The error indicates that either the node is unable to reach the subnet 10.0.0.0/8, or there is no controller actively running at the address 10.0.0.1 on port 6653.

[gao weiwei]

i think my bofuss should be running normally.Here are some test results.

[gao weiwei]

Dear ramonfontes, is this issue due to my incorrect usage of BOFUSS as UserAP in Mininet-Wifi? What steps should I take to use BOFUSS as UserAP in Mininet-Wifi? I only added cls=UserAP, inNamespace=True, inband=True, datapath='user' when adding the AP.

[Ramon Fontes]

Only cls=UserAP is mandatory; the others are optional.