PS4/Hulu connection issues.

RouterOS Beginner Basics
1

We use Mikrotiks extensively at work, and my awesome boss let me take home a RB951 to play around with.

I got it setup, manually, without issue. Didn’t use quick set.

My devices get IPs, I’m pushing 150mb/s down, the works.
Netflix, Steam, youtube, etc etc.

However, I’m having one weird issue.

Playstation network. Can’t sign in via PS4 or web browser.
Hulu also states I’m using an anonymous proxy, I’m certainly not.

I’m using the latest version RouterOS, and my firewall is open (for now) while I troubleshoot.

Any ideas?
Please let me know of any outputs you guys need.

Thank you!

2

Read these posts: https://forum.mikrotik.com/search.php?keywords=hulu

3

Thank you, but I’ve already searched this forum and others.

I’m not using a VPN, almost all of the Hulu threads are people trying to watch Hulu via VPN.

All of the PSN/Ps4 threads are exactly the issue I have, no one seems to have formed a solution yet.

4

Sounds like Hulu doesn’t like something about your connection (ISP, your IP address, Geolocation) or is detecting an open service on your IP address (or provider)

I have users watching Hulu daily, no problems.

I have no experience with PS4 but i’m guessing it’s lack of PnP related, which no one seems to recommending turning on.

5

Just wanted to post an update for people of the future.

I found out the issue.

If your firewalls arn’t setup right, these services for some reason straight up refuse to work.

In my case, I disabled ALL my firewall rules during testing, and that was the issue.

Literally just adding an implicit accept followed by an implicit deny fixed it, BUT DON’T ACTUALLY DO THAT IT’S AS UNSECURE AS LEAVING YOUR DOOR UNLOCKED IN DETROIT.
/ip firewall filter
add action=drop chain=input comment=“Drop Invalid” connection-state=invalid
in-interface=YOUR_WAN_ETHER
add action=accept chain=input connection-state=related in-interface=
YOUR_WAN_ETHER
add action=accept chain=input connection-state=established in-interface=
YOUR_WAN_ETHER
add action=drop chain=input comment=“Drop ALL” in-interface=YOUR_WAN_ETHERLiterally just copy the above bit, and paste it in the terminal. Just change YOUR_WAN_ETHER to whatever your WAN ether is (the one where the internet is comming in, ie, if it’s in port 1, by default it’s ether-1)

6

Interesting but what I want to know is … what do INPUT chain rules have do with Internet being forwarded to LAN and LAN being forwarded to the internet???
I would have thought that is where FW rules may have been an issue.
In other words you have not shed light on what the actual problem is…at least from my brief reading and limited understanding.