-
|
Hi All, I have a config that spins up a bunch of dhcp and pppoe subscribers and all I was after from streams is to send 1 pps from each subscriber to something upstream of the BNG. I've simplified the config down to this (bgplink0 is a layer 2 interface into the access network): {
"interfaces": {
"access": [
{
"interface": "bnglink0",
"type": "ipoe",
"outer-vlan-min": 3089,
"outer-vlan-max": 3701,
"outer-vlan-step": 1,
"inner-vlan-min": 11,
"inner-vlan-max": 4011,
"inner-vlan-step": 1,
"stream-group-id": 1
}
]
},
"dhcp": {
"enable": true
},
"dhcpv6": {
"enable": false
},
"access-line": {
"agent-remote-id": "AVC.{session-global}",
"agent-circuit-id": "et-7/0/1:{session-global}"
},
"sessions": {
"start-rate": 100,
"max-outstanding": 40000
},
"streams": [
{
"stream-group-id": 1,
"name": "S1",
"direction": "upstream",
"pps": 1,
"type": "ipv4",
"destination-ipv4-address": "10.241.0.1"
}
]
}So far, all I can get out of it is: So im not sure if im miss-understanding the purpose of streams or using them wrong or supposed to be using something other than streams?? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 2 replies
-
|
It failed to create traffic because there is no network-interface which could receive the traffic. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, BNG Blaster expects to be the receiver, but if you override the destination IPv4 address, it should work as long as you create at least one network interface. This allows BNG Blaster to assume traffic there, even if it is not actually received on that interface. Alternatively, you can create a dummy network interface with the option |
Beta Was this translation helpful? Give feedback.
Yes, BNG Blaster expects to be the receiver, but if you override the destination IPv4 address, it should work as long as you create at least one network interface. This allows BNG Blaster to assume traffic there, even if it is not actually received on that interface. Alternatively, you can create a dummy network interface with the option
"gateway-resolve-wait": falseto ignore when resolving the network interface gateway address fails.