FTP incoming with WinUAE 3.5b11 to 3.6b3

[AC/DC HACKER!]

Hello,

Something I noticed recently as I was again going to use FTP and FTPd.

With 3600b1 bsdsocket.library isn't allowing FTP connection from another machine. However, it is supporting Internet access with OS 3.5. If I go back to 3500b11, it allows FTP incoming connections. I downloaded 3600b3 and it won't allow incoming connections either, but does allow Internet access. I'm using an Amiga 4000 CSPPC config.

I'm using MiamiDx and AmiFTPd_GUI 2.2.

I am able to get Internet access with X-Surf "hardware", but FTP incoming isn't coming in. I've checked I'm addresses, and all looks great. But only bsdsocket.library is allowing access to WinUAE 3500b11. I've checked with all the ROMs, Direct, Indirect...etc. I might be missing something, but when I connect with AmigaOne X5000 or my Amiga 4000 Desktop, only 3500b11 is allowing access.

I'll continue checking.... Anyone else noticing this? By the way...I'm not switching to any other TCP/IP programs, I bought and use MiamiDX...hehe...in case anyone wants to suggest it.

[Toni Wilen]

Some firewall/security software suddenly deciding to block incoming connections?

Does Windows netstat show the listening port?

[AC/DC HACKER!]

WinUAE 3.5.0. B11, 20 and 21 are showing as connected to WinUAE from other Amiga. Using bsdsocket.library. Avast! firewall is temp off for an hour.

Proto Local Address Foreign Address State

TCP 192.168.1.2:20 192.168.1.11:1026 TIME_WAIT
TCP 192.168.1.2:20 192.168.1.11:1028 TIME_WAIT
TCP 192.168.1.2:21 192.168.1.11:1027 ESTABLISHED
TCP 192.168.1.2:49163 sea25:http ESTABLISHED
TCP 192.168.1.2:49250 13.107.42.11:https ESTABLISHED
TCP 192.168.1.2:49328 msnbot-65-52-108-76:https ESTABLISHED
TCP 192.168.1.2:49333 40.79.84.196:https ESTABLISHED
TCP 192.168.1.2:49380 edge-star-mini-shv-01-sea1:https ESTABLISHED
TCP 192.168.1.2:49392 edge-star-shv-01-sea1:https ESTABLISHED
TCP 192.168.1.2:49574 a890he:https CLOSE_WAIT
TCP 192.168.1.2:50012 r-253-41-234-77:http CLOSE_WAIT
TCP 192.168.1.2:50060 pc-in-f189:https ESTABLISHED
TCP 192.168.1.2:50199 sea15s11-in-f174:https ESTABLISHED
TCP 192.168.1.2:50206 104.208.165.109:https TIME_WAIT
TCP 192.168.1.2:50207 104.208.165.109:https TIME_WAIT

Now exiting WinUAE restarting with bsdsocket disabled and X-Surf 100 Z3 enabled (MAC).

TCP 192.168.1.2:49163 sea25:http ESTABLISHED
TCP 192.168.1.2:49250 13.107.42.11:https ESTABLISHED
TCP 192.168.1.2:49328 msnbot-65-52-108-76:https ESTABLISHED
TCP 192.168.1.2:49333 40.79.84.196:https ESTABLISHED
TCP 192.168.1.2:49380 edge-star-mini-shv-01-sea1:https ESTABLISHED
TCP 192.168.1.2:49392 edge-star-shv-01-sea1:https ESTABLISHED
TCP 192.168.1.2:49574 a890he:https CLOSE_WAIT
TCP 192.168.1.2:50012 r-253-41-234-77:http CLOSE_WAIT
TCP 192.168.1.2:50060 pc-in-f189:https ESTABLISHED
TCP 192.168.1.2:50246 sea15s11-in-f174:https ESTABLISHED

As you can see, there isn't a connection. Other Amiga is sitting at the attempting to connect. I'll go ahead and disable Avast! completely & check that again.

Avast! Internet Security is now totally disabled, but doesn't make sense for that since bsdsocket worked, but..eh.. Running WinUAE 3.5.0.B11, and now running MiamiDX then AmiFTPd.. Now FTP is active. Running IBrowse, and it has Internet access, browses through and pulls data..
Now, over to other Amiga, and attempt FTP connection. "Host found, connecting..." is all it does with X-Surf Z3.

I don't see anything about 192.168.1.2 which is where WinUAE is running. Exiting software, resetting WinUAE and going back to bsd...

TCP 192.168.1.2:20 192.168.1.11:1031 TIME_WAIT

Back to disabled BSDSOCKET and enabled X-Surf Z3... IBrowse is fine, but just sits "waiting". Nothing from Netstart about 192.168.1.2..

I have checked Windows Firewall as well. All looks good, and since BSDSOCKET is functioning.

Running WinUAE 3.6.0.B3 and BSDSOCKET; Netstat:

TCP 192.168.1.2:49184 sea15s11-in-f14:https ESTABLISHED
TCP 192.168.1.2:49185 a23-47-144-56:http ESTABLISHED
TCP 192.168.1.2:49186 sea15s11-in-f14:https ESTABLISHED
TCP 192.168.1.2:49187 ec2-52-9-194-80:https ESTABLISHED
TCP 192.168.1.2:49198 sea15s11-in-f14:http TIME_WAIT
TCP 192.168.1.2:49199 72.21.91.29:http TIME_WAIT
TCP 192.168.1.2:49200 sea15s11-in-f14:http TIME_WAIT
TCP 192.168.1.2:49201 sea02-027:https TIME_WAIT
TCP 192.168.1.2:49202 sea02-027:https TIME_WAIT
TCP 192.168.1.2:49227 ec2-35-160-9-151:https TIME_WAIT
TCP 192.168.1.2:49228 72.21.91.29:http TIME_WAIT
TCP 192.168.1.2:49234 pc-in-f105:http TIME_WAIT
TCP 192.168.1.2:49235 sea15s11-in-f14:https ESTABLISHED

Again, I'm not including localhost because it doesn't seem important. Count not connect to FTPd.

Resetting, disabled BSD...and enabled X-Surf Z3. IBrowse browses Aminet and accepts a gibberish search and returns that there aren't any matches for it. So, it works. But FTPd is not accepting connection.

I don't know what else at the moment to attempt. Seems like a bug. Hmm.. Now returning Avast! back to normal since it's the same activity.

[Toni Wilen]

Use "netstat -a" to see all listening ports. You should see "TCP 0.0.0.0:21" with State = LISTENING if port is listening for all connections.

Did you also try connection from same PC? (If you originally tried from other PC. Incoming connection may be blocked.)

It still sounds like firewall issue.

[AC/DC HACKER!]

For WinUAE 3.5.0. B11 BSDSOCKET.

TCP 0.0.0.0:21 SUCK:0 LISTENING

Directory Opus 11.5 from same Windows WinUAE is running from, FTP connects.

TCP 192.168.1.2:21 SUCK:49426 ESTABLISHED

Exited FTP connection from same machine with Directory Opus 11. Now connecting with external Amiga...

TCP 0.0.0.0:21 SUCK:0 LISTENING

TCP 192.168.1.2:20 192.168.1.11:1025 TIME_WAIT
TCP 192.168.1.2:21 192.168.1.11:1024 ESTABLISHED

So, 3.5.0. B11 is allowing and connecting fine. Resetting and disabling BSDSOCKET and enabling X-Surf 100 Z3.

Nothing is showing that looks like the above. Directory Opus 11 noticing the IP but won't connect. Checking something different. Disabled X-Surf and enabling A2065. Okay, it's Online with MiamiDX.. IBrowse connects to Aminet as before..

Directory Opus does not connect, and Netstat -a doesn't show anything like the above. This indicates to me it's not a Firewall problem. But...perhaps?

I decided to disable Avast! Firewall and Windows Firewall. Directory Opus 11 connects from same Windows. Switching to X-Surf Z3.

Nada....not any LISTENING on 20 or 21. Any other ideas? I'm not sure what to consider next. Hmm.. I suppose I could uninstall Avast! but using MSConfig and disabling it after disabling its self-protection usually does very, very well if needed. There's an Update for it so I'll have it to do...but, I don't see how it's an Avast! bug / block at this point since BSDSOCKET is working and the others are also except for port 21. Hmm...

[AC/DC HACKER!]

Since my WinUAE A4000 setup is a clone of my Amiga 4000 CSPPC I decided to start the FTP with it which has the X-Surf Z3 installed. WinUAE 3.5.0. B11 connects fine with Directory Opus 5.91 from Workbench. It has the same MiamiDx config accept for A4K is using Static vs DHCP for WinUAE, so that's not the problem...since Amiga 4000 is allowing FTPd connections. I wanted to totally rule that out.

[Toni Wilen]

Listening sockets work fine here. (and there would have been lots of bug reports if bsdsocket incoming connections stopped working)

There is no bsdsocket changes in b12 (or close it). Last bsdsocket related change was in b5.

[AC/DC HACKER!]

I thought so also. Which is why I'm confused. I uninstalled Avast! and disabled Windows Firewall. Next thing to do is create a new WinUAE directory and act like it's a fresh install and see if that does it.

Appreciate the help, Toni.

[AC/DC HACKER!]

Toni, are you meaning BSDSOCKET is used when X-Surf 100 Z3 is active? I have it unticked. If I have it ticked AND use X-Surf 100 Z3 then MiamiDx informs me of a TCP/IP stack already running, which makes sense.

[AC/DC HACKER!]

Hi,

Maybe this will help? First BSDSOCKET is used with FTPd.. Then disabled and used X-Surf 100 Z3. Maybe not many are using it? I don't know. Here are he debud logs. I read through it but if you're inclined to do so, you'd be able to spot any problems better than I.

[Toni Wilen]

Do you mean you use hardware emulated network card? (Not bsdsocket.library).

Then make sure you have slirp + open ports mode enabled. Selected NIC in expansion panel -> network mode. Drop down menu under the NIC selection. (Manual config file editing is needed if you need to open other ports). Default mode is outbound connections only.

EDIT: or winpcap mode which makes selected PC NIC to have separate virtual MAC address that is connected to emulated NIC. This mode does not have any port limits.

[AC/DC HACKER!]

Yes, that's what switching to X-Surf 100 Z3 was meaning. As well as enabling and disabling. Every time I had chosen / selected Slirp I'd press F12 and notice it was back to MAC. I hadn't followed through after that. My error. Now I see that "slirp + open ports mode enabled." does show it as LISTENING and is accessible.
I don't understand why leaving it at MAC for X-Surf doesn't allow port 21 to LISTEN. Hmm.. But your description of wincap mode makes sense for BSDSOCKET and why it's much faster and MiamiDx reports there's already an TCP/IP stack running.

I was being fooled by the Slirp selection being active even though it would show MAC as the selected choice after press F12 once Workbench was loaded.

Again, appreciation. Another donation coming soon. Not because of this, but reminded me.

[Toni Wilen]

Originally Posted by AC/DC HACKER!

Yes, that's what switching to X-Surf 100 Z3 was meaning. As well as enabling and disabling. Every time I had chosen / selected Slirp I'd press F12 and notice it was back to MAC. I hadn't followed through after that. My error. Now I see that "slirp + open ports mode enabled." does show it as LISTENING and is accessible.

MAC is just an another option that does not even work currently (I forgot to implement text box in expansion configuration gui.. oops..) It is only a selector that shows either MAC or Network mode option.

Note that option won't "stick" if expansion device is not enabled.

I don't understand why leaving it at MAC for X-Surf doesn't allow port 21 to LISTEN. Hmm.. But your description of wincap mode makes sense for BSDSOCKET and why it's much faster and MiamiDx reports there's already an TCP/IP stack running.

I think you are confused by something.. bsdsocket emulation has nothing to do with slirp/winpcap.

There are 3 different network emulation layers:

- bsdsocket = socket level, maps Amiga socket API to host socket API. Network driver or network adapter does not exist. Only plain TCP and UDP supported.

- uaenet.device = Amiga network driver level, raw ethernet frames, nearly same as below.

- hardware emulated nic = pure hardware level, only sees raw ethernet packets that can be connected to slirp which reroutes it back to host API (=only popular TCP and UDP protocols supported) or winpcap = raw ethernet frames are transmitted/received by host PC NIC driver. (Not restrictions whatsoever)

In conclusion: if you only need to run basic Amiga internet software -> bsdsocket.library emulation.

[AC/DC HACKER!]

MAC is just an another option that does not even work currently (I forgot to implement text box in expansion configuration gui.. oops..) It is only a selector that shows either MAC or Network mode option.

Note that option won't "stick" if expansion device is not enabled.

The oops answers as to why it wasn't functioning as I thought it should. Naughty, Toni! Haha!

I understand it won't "stick" if not enabled, I didn't check for that.

I think you are confused by something.. bsdsocket emulation has nothing to do with slirp/winpcap.

There are 3 different network emulation layers:

- bsdsocket = socket level, maps Amiga socket API to host socket API. Network driver or network adapter does not exist. Only plain TCP and UDP supported.

- uaenet.device = Amiga network driver level, raw ethernet frames, nearly same as below.

- hardware emulated nic = pure hardware level, only sees raw ethernet packets that can be connected to slirp which reroutes it back to host API (=only popular TCP and UDP protocols supported) or winpcap = raw ethernet frames are transmitted/received by host PC NIC driver. (Not restrictions whatsoever)

In conclusion: if you only need to run basic Amiga internet software -> bsdsocket.library emulation.

I wasn't confused the way you where thinking. I was only confused as to why the MAC wasn't functioning as it should. Now I know. I will continue to BSDSOCKET because that's really speedy, and though I'm still okay with the speaks of the 90's and so on, I do like the quicker. The AmiFTP Directory Opus and all that have KB/s transfer progress, so...it's cool. I do think it's really sweet to have X-Surf's accessible.

I entered the "uaenet.device" into MiamiDx and it noticed it without a problem. So MAC was my only wonderment. Appreciate the help, Toni. Love that BSDSOCKET.


P.S. Side note...I hope this current version, once out of beta, becomes ported to AmigaOne's. I already know you don't want to. Only a comment. This would really bring the Classic together with the "New".

P.S.S. Donation made.