You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not able to run multiple instances of BNG-Blaster on one server
Instance-1 running fine
when we start Instance-2 getting 'Error: Failed to init interfaces '
mponnusa@podblaster:~$ sudo bngblaster -C instance1.json -S run.sock
Nov 20 07:14:11.697653 Warning: Interfaces must not have an IP address configured in the host OS!
Nov 20 07:14:11.697702 Warning: IP address fe80::1e98:ecff:fe15:419d on interface eno2 is conflicting!
Nov 20 07:14:12.188316 Total PPS of all streams: 0.00
Nov 20 07:14:12.188644 Opened control socket run.sock
Nov 20 07:14:13.188390 Resolve network interfaces
Nov 20 07:14:13.188414 All network interfaces resolved
mponnusa@podblaster:~$ sudo bngblaster -C instance2.json -S run.sock -I
Nov 20 06:53:54.835847 Failed to set fanout group for interface eno3 - Invalid argument (22)
Nov 20 06:53:54.835928 Failed to add link eno3
Error: Failed to init interfaces
Additional Note:
When we run instance1.json & instance2.json without tx-threads & rx-threads, we were able to run both instances parallelly
The text was updated successfully, but these errors were encountered:
Not able to run multiple instances of BNG-Blaster on one server
Instance-1 running fine
when we start Instance-2 getting 'Error: Failed to init interfaces '
Version: 0.9.12
Payload
{
"comment": "VULCANUS",
"interfaces": {
"capture-include-streams": true,
"tx-threads": 10,
"access": [
{
"comment": "WM-TEST",
"interface": "eno2",
"inner-vlan": 7,
"monkey": false,
"type": "pppoe",
"outer-vlan": 1124
}
],
"rx-threads": 10
},
"traffic": {
"stream-burst-ms": 10
},
"sessions": {
"count": 1,
"max-outstanding": 800,
"start-rate": 400,
"stop-rate": 400,
"reconnect": true,
"monkey-autostart": false
},
"pppoe": {
"reconnect": true,
"discovery-timeout": 3,
"discovery-retry": 10,
"vlan-priority": 6
}
}
instance2.json
{
"comment": "VULCANUS",
"interfaces": {
"capture-include-streams": true,
"tx-threads": 10,
"access": [
{
"comment": "WM-TEST",
"interface": "eno3",
"inner-vlan": 7,
"monkey": false,
"type": "pppoe",
"outer-vlan": 1125
}
],
"rx-threads": 10
},
"traffic": {
"stream-burst-ms": 10
},
"sessions": {
"count": 1,
"max-outstanding": 800,
"start-rate": 400,
"stop-rate": 400,
"reconnect": true,
"monkey-autostart": false
},
"pppoe": {
"reconnect": true,
"discovery-timeout": 3,
"discovery-retry": 10,
"vlan-priority": 6
}
}
mponnusa@podblaster:~$ sudo bngblaster -C instance1.json -S run.sock
Nov 20 07:14:11.697653 Warning: Interfaces must not have an IP address configured in the host OS!
Nov 20 07:14:11.697702 Warning: IP address fe80::1e98:ecff:fe15:419d on interface eno2 is conflicting!
Nov 20 07:14:12.188316 Total PPS of all streams: 0.00
Nov 20 07:14:12.188644 Opened control socket run.sock
Nov 20 07:14:13.188390 Resolve network interfaces
Nov 20 07:14:13.188414 All network interfaces resolved
mponnusa@podblaster:~$ sudo bngblaster -C instance2.json -S run.sock -I
Nov 20 06:53:54.835847 Failed to set fanout group for interface eno3 - Invalid argument (22)
Nov 20 06:53:54.835928 Failed to add link eno3
Error: Failed to init interfaces
Additional Note:
When we run instance1.json & instance2.json without tx-threads & rx-threads, we were able to run both instances parallelly
The text was updated successfully, but these errors were encountered: