• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help AFwall+ interferes with chromecast

electricpete

electricpete

Android Expert
I have AFwall+ firewall set up in "whitelist mode" on my S4.
(For whitelist mode, all apps/processes are blocked except those explicitly allowed)
Chromecast app is allowed in AFwall+

When I attempt to cast anything with AFwall+ active, it shows the chromecast device name, I click on the name to connect, it shows a message "connecting" followed immediately by "disconnecting" and no screencast occurs.

When I attempt to cast with AFwall+ disabled, it casts the fine.

The problem casting (with afwall enabled) applies both to screen cast (initiated from within chromecast app) as well as to casting initiated from within chromecast-compatible apps like YouTube.



I presently "work around" the situation by disabling AFwall+ whenever I want to cast. But I'd like to fix it so I don't have to do that.

I assume there is some system process that I have to enable within AFwall... any ideas which one? Other suggestions?
 
Last edited:
Thanks. Five minutes after starting casting, I went to settings / manage-apps/ running-services. The only thing that had been running for five minutes was "Google play services", which is already on my afwall whitelist, so not the culprit. The other items are things running since boot, d....Maybe I'll look at those closer when I get a chance.


it's not really important to you guys, but this thread may stretch out awhile in time. The reason is: I have access to chromecast only where I installed a chromecast in my mom's tv in her apartment (so I can show her stuff on my phone). I have no chromecast in my home so I'll having limited opportunity to troubleshoot
 
Last edited:
I don't follow.

I'm using the deprecated predecessor to AFWall+ (because ipchains are ipchains, regardless of the manager) and I don't have the problem at all.

I don't have input chains active, I do have it open across the board, LAN, wifi and data.
 
Does yours work on a principle like whitelist mode (only specifically identified processes are allowed) or blacklist mode (only specifically identified processes are blocked).

whitelist mode is more secure, but also more susceptible to this kind of problem.
 
electricpete said:
Does yours work on a principle like whitelist mode (only specifically identified processes are allowed) or blacklist mode (only specifically identified processes are blocked).

I tend to believe whitelist mode is more secure, but also more susceptible to this kind of problem.
Click to expand...
It's set the same as yours, earlier version.

1435349350285.jpg

I stay in whitelist mode and don't open up anything to a new app until I see where it wants to go using Network Connections, and approve.
 
Last edited:
I don't have any "LAN" checked, only wifi and data. I thought LAN was for roaming, but I'll give it a try this afternoon.... easy enough to check.

If that doesn't work I'll post a list of what system (red) processes I have enabled and disabled. There are a lot those that I have no clue about, ... so I left them disabled.
 
I went through and checked the LAN box on all my red system processes that already had wifi checked. That fixed it.

Thanks, earlymon.
 
You must log in or register to reply here.
Back
Top Bottom