Hello, Here's the setup. I put FreeDOS 1.2 into a KVM-backed VM and gave it a Realtek 8139 so I can test network connectivity. I've installed the appropriate packet driver from here http://www.georgpotthast.de/sioux/packet.htm Next, I run "curl -v http://10.0.0.2:8080"; because this is where I keep my Jenkins running on my local network. To my surprise, the results are completely inconsistent with reality. This is what I get on DOS after the compile errors: * Trying 208.73.211.165... connected > GET //10.0.0.2:8080 HTTP/1.1 > User-Agent: curl/7.21.6 (i386-pc-msdosdjgpp) libcurl/7.21.6 CyaSSL/2.0.0rc1 zlib/1.2.5 > Host: http > Accept: */* > < HTTP/1.1 200 OK < Date: Thu, 14 Feb 2019 01:03:53 GMT < Server: Apache < Content-Length: 51 < Content-Type: text/html; charset=UTF-8 < * Connection #0 to host http left intact * Closing connection #0 <html><head></head><body><!-- vbe --></body></html>
At first I googled this strange IP and got this: https://ransomwaretracker.abuse.ch/ip/208.73.211.177/ Everyone loves talking to unexpected ransomware hosts at 2 AM :) I tried confirming the results on 10.0.0.2 and curl properly got me the Jenkins login prompt and a 403. So I've read the DOS curl output the 2nd time. What peaked my interest is "Connection #0 to host http left intact". On Linux it said "Connection #0 to host 10.0.0.2 left intact"... Wait a minute. Did curl just resolve "http" into a DNS host? I realized this may be due to my mistake, so I tried to escape the slashes and encapsulate the destination into single and double quotemarks. No effect. I only get the correct result if I completely skip "http://"; from the destination. Anyone else had this problem? Best regards, Michal
_______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
