Changes between Version 2 and Version 3 of Ticket #17405, comment 2
- Timestamp:
- Dec 29, 2017 12:32:01 AM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #17405, comment 2
v2 v3 1 1. Apologies for my lack of proper "bug reporting etiquette" this is the first one I've posted a nd there is nothing on the main bug tracker page that specifieswhat information is required, furthermore what I provided was additional technical configurations of my setup which clearly show the issue is with Virtualbox itself, specifically in Bridge Mode. Also please direct me to any special "posting procedure" documents I should read before posting in the future and I will try to post in that manner.1 1. Apologies for my lack of proper "bug reporting etiquette" this is the first one I've posted a bug report and as far as I could tell on the main bug tracker page I found: https://www.virtualbox.org/wiki/Bugtracker there didn’t seem to be anything that specified any “bug submission guidelines” or what information is required, furthermore what I provided was additional technical configurations of my setup which clearly show the issue is with Virtualbox itself, specifically in Bridge Mode. Also please direct me to any special "posting procedure" documents I should read before posting in the future and I will try to post in that manner. 2 2 3 3 2. There were multiple differences which compelled me to open a new ticket. … … 8 8 That said if you still believe this to be a duplication I will migrate my information over to ticket #17375. 9 9 10 3. I've attached the following information with the system (Kali 2017.3 - Live amd64 Bootmode) 10 3. I've included the following information for the VM Guest (Kali 2017.3 - Live amd64 Bootmode) 11 a. VBOX.LOG 12 b. /etc/network/interfaces 13 c. NATDUMP.PCAP (SUCCESSFUL NAT) 14 d. Ip addr output in NAT mode 15 e. BRIDGEDUMP.PCAP (FAILED BRIDGE) 16 f. Ip addr output in Bridge mode 11 17 12 == /etc/network/interfaces: == 18 19 20 ---- 21 22 == a. VBOX.LOG == 23 http://termbin.com/xgb5 24 25 26 ---- 27 28 29 == b. /etc/network/interfaces: == 13 30 14 31 {{{ … … 23 40 ---- 24 41 25 == PCAP (SUCCESSFUL NAT) accessing ubuntu.com using wget==26 42 == c. NATDUMP.PCAP (SUCCESSFUL NAT) == 43 Description: Accessing ubuntu.com using wget with system in NAT Mode 27 44 https://drive.google.com/open?id=1TM69sy11XVJmdPSkQXwo1W7oeUv0gOkg 28 45 29 46 30 == Ip addr output in NAT mode: ==47 == d. Ip addr output in NAT mode: == 31 48 32 49 {{{ … … 50 67 ---- 51 68 52 == PCAP (FAILED BRIDGE) accessing ubuntu.com using wget==53 69 == e. BRIDGEDUMP.PCAP (FAILED BRIDGE) == 70 Description: Accessing ubuntu.com using wget with system in Bridge Mode 54 71 https://drive.google.com/open?id=1DmK2Ly-r40zA2IwFHkDAxGFh1dpMQwKY 55 72 56 == Ip addr output of Bridge mode: ==73 == f. Ip addr output of Bridge mode: == 57 74 58 75 {{{ … … 74 91 75 92 ---- 76 As you can see from the BridgeDump.PCAP, the issue starts around packet 11 with a "Previous Segment not captured" when performing the TLS exchange for the HTTPS traffic, which is then followed by a series of failed re-transmissions. This behavior only happens in Bridge mode as seen when comparing it to the NAT PCAP where the TLS exchange works fine. 93 == Technical Summary of PCAP data == 94 As you can see from the BridgeDump.PCAP, the issue starts around packet 11 with a "Previous Segment not captured" when performing the TLS key exchange for the HTTPS traffic, which is then followed by a series of failed re-transmissions. This behavior only happens in Bridge mode as seen when comparing it to the NAT PCAP where the TLS key exchange works fine. 95 96 ---- 77 97 78 98 That said, if you want to test this highly repeatable behavior yourself it will happen even with a default “live (amd64) boot mode” instance of Kali 2017.3 so no additional configurations need to be made for you to replicate the issue in Virtualbox's Bridge Mode. … … 81 101 82 102 -J 83 84 PS. I still owe you a log file for the VM. (I just noticed as I was heading out the door that I failed to provide this piece for. I'll get that for you when I've returned home in around 3-4 Hours)

