我正在使用bgp在ubuntu上实现。我想在bgp包中做一些畸形,bgp限制我们的大小在19到4096之间,但是为了测试目的,我正在更改小于19和大于4096的大小。在此之后,当我将这个数据包从一个发送到第二个,在两个扬声器之间建立的bgp会话上,第二个应该发送包含错误:坏消息长度的通知消息。但我并没有得到这一点,而是在wireshark中显示了格式错误的数据包,而且我也无法在wireshark中打开该数据包。有人能帮我处理这个数据包的畸形并得到通知错误吗?
我试过了每一个包,比如打开、更新和保持生命。格式错误的打开包:

发布于 2019-01-30 17:58:54
更新了下面的答案
Wireshark中显示的BGP分组具有标记字段(16 X ff),后面是长度16 (00 10)。
因此,这确实是您想要测试的场景:您的测试人员BGP扬声器发送了一个长度不正确的BGP数据包,而被测试的远程BGP扬声器应该通过发送带有错误代码"Message Header Error“和错误子代码"Bad Message Length”的通知数据包来响应。
Wireshark显示了从测试器BGP扬声器发送到正在测试的BGP扬声器的错误BGP数据包。Wireshark抱怨它是一个格式错误的BGP数据包是正确的:它是格式错误的,因为长度是无效的。显然,Wireshark对于它不喜欢这个包的内容不是很具体。
您应该向相反的方向查看TCP流(源10.0.0.2目的地10.0.0.1),并查找被测试的BGP扬声器返回的BGP通知包。
更新的答案从这里开始,
基于错误消息([Error] bgp_read_packet error: Connection reset),看起来您正在测试自由范围路由,或者它的前身Quagga或Zebra。
我复制了你正在测试的场景。
我正在运行一个自由范围路由(FRR) BGP扬声器,配置如下:
Current configuration:
!
frr version 7.1-dev-MyOwnFRRVersion
frr defaults traditional
hostname ip-172-31-31-121
log file /var/log/frr/debug.log
log syslog
service integrated-vtysh-config
!
debug bgp neighbor-events
!
router bgp 100
neighbor X.X.X.X remote-as 200
!
line vty
!
end我使用下面的Python测试程序发送带有“太短”标题的消息:
#!/usr/bin/env python3
import socket
BGP_IP = 'Y.Y.Y.Y'
SHORT_MSG = (b'\xff\xff\xff\xff\xff\xff\xff\xff' # First 8 bytes of marker
b'\xff\xff\xff\xff\xff\xff\xff\xff' # Last 8 bytes of marker
b'\x00\x10' # Length 16
b'\x01') # Open
def main():
sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
print("Socket created")
sock.connect((BGP_IP, 179))
print("Socket connected")
sock.send(SHORT_MSG)
print("Short message sent")
while True:
data = sock.recv(1)
if data == b'':
print("Connection closed or reset")
break
print("Received:", data)
if __name__ == "__main__":
main()用测试器的IP地址替换X.X.X.X,用正在测试的BGP扬声器的IP地址替换Y.Y.Y.Y。
在这种情况下,被测试的BGP扬声器确实发送正确的通知消息。
以下是FRR日志报告的内容:
2019/02/09 21:49:05 BGP: 172.31.17.121 [FSM] Timer (connect timer expire)
2019/02/09 21:49:05 BGP: 172.31.17.121 [FSM] ConnectRetry_timer_expired (Active->Connect), fd -1
2019/02/09 21:49:05 BGP: 172.31.17.121 [Event] Connect start to 172.31.17.121 fd 26
2019/02/09 21:49:05 BGP: 172.31.17.121 [FSM] Non blocking connect waiting result, fd 26
2019/02/09 21:49:05 BGP: bgp_fsm_change_status : vrf 0, established_peers 0
2019/02/09 21:49:05 BGP: 172.31.17.121 went from Active to Connect
2019/02/09 21:49:05 BGP: 172.31.17.121 [Event] Connect failed 111(Connection refused)
2019/02/09 21:49:05 BGP: 172.31.17.121 [FSM] TCP_connection_open_failed (Connect->Active), fd 26
2019/02/09 21:49:05 BGP: bgp_fsm_change_status : vrf 0, established_peers 0
2019/02/09 21:49:05 BGP: 172.31.17.121 went from Connect to Active
2019/02/09 21:49:08 BGP: [Event] BGP connection from host 172.31.17.121 fd 26
2019/02/09 21:49:08 BGP: bgp_fsm_change_status : vrf 0, established_peers 0
2019/02/09 21:49:08 BGP: 172.31.17.121 went from Idle to Active
2019/02/09 21:49:08 BGP: 172.31.17.121 [FSM] TCP_connection_open (Active->OpenSent), fd 26
2019/02/09 21:49:08 BGP: 172.31.17.121 passive open
2019/02/09 21:49:08 BGP: 172.31.17.121 Sending hostname cap with hn = ip-172-31-31-121, dn = (null)
2019/02/09 21:49:08 BGP: 172.31.17.121 sending OPEN, version 4, my as 100, holdtime 180, id 172.31.31.121
2019/02/09 21:49:08 BGP: bgp_fsm_change_status : vrf 0, established_peers 0
2019/02/09 21:49:08 BGP: 172.31.17.121 went from Active to OpenSent
2019/02/09 21:49:08 BGP: 172.31.17.121 bad message length - 16 for OPEN
2019/02/09 21:49:08 BGP: %NOTIFICATION: sent to neighbor 172.31.17.121 1/2 (Message Header Error/Bad Message Length) 2 bytes 00 10
2019/02/09 21:49:08 BGP: 172.31.17.121 [FSM] BGP_Stop (OpenSent->Idle), fd 26
2019/02/09 21:49:08 BGP: bgp_fsm_change_status : vrf 0, established_peers 0
2019/02/09 21:49:08 BGP: 172.31.17.121 went from OpenSent to Deleted注意“坏消息长度”消息。
下面是测试程序报告的内容:
Socket created
Socket connected
Short message sent
Received: b'\xff'
Received: b'\xff'
Received: b'\xff'
Received: b'\xff'
Received: b'\xff'
Received: b'\xff'
Received: b'\xff'
Received: b'\xff'
Received: b'\xff'
Received: b'\xff'
Received: b'\xff'
Received: b'\xff'
Received: b'\xff'
Received: b'\xff'
Received: b'\xff'
Received: b'\xff'
Received: b'\x00'
Received: b'\x17'
Received: b'\x03'
Received: b'\x01'
Received: b'\x02'
Received: b'\x00'
Received: b'\x10'
Connection closed or reset请注意,这是正确的坏消息长度通知。
下面是坏消息的Wireshark解码:

下面是通知的Wireshark解码:

如果测试程序终止而不试图读取通知消息,那么被测试的BGP扬声器将无法在线路上发送通知消息。这是因为它在发送通知之前将接收TCP RST消息。这很可能是您没有在连线上看到通知的原因。
实际上,我能够通过如下修改测试程序来重现这一假设:
#!/usr/bin/env python3
import socket
import struct
BGP_IP = '172.31.31.121'
SHORT_MSG = (b'\xff\xff\xff\xff\xff\xff\xff\xff' # First 8 bytes of marker
b'\xff\xff\xff\xff\xff\xff\xff\xff' # Last 8 bytes of marker
b'\x00\x10' # Length 16
b'\x01') # Open
def main():
sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
print("Socket created")
sock.connect((BGP_IP, 179))
print("Socket connected")
sock.send(SHORT_MSG)
# Trick TCP into sending a RST when the socket is closed
on_off = 1
linger = 0
sock.setsockopt(socket.SOL_SOCKET, socket.SO_LINGER, struct.pack('ii', on_off, linger))
print("Socket linger time set to 0")
# Close the socket
sock.close()
print("Socket closed")
# Terminate without reading the response NOTIFICATION
if __name__ == "__main__":
main()使用此测试程序,Wireshark跟踪中缺少通知(正如您报告的那样):

请注意,我必须跳过一些环(特别是将逗留时间设置为零),以强制测试程序发送RST,而不是FIN ACK。(详见Sending a reset in TCP/IP Socket connection。)
如果测试程序发送FIN ACK而不是RST (如果您优雅地关闭套接字,甚至在不关闭套接字的情况下正常终止),则BGP扬声器将能够在接收到FIN ACK之后但在发送自己的FIN ACK之前发送通知。
https://stackoverflow.com/questions/54434522
复制相似问题