will this allow me to block my wii-u's mac address while also being able to connect to my hosted files? I tried it, and it didn't work. I guess I'm wondering what the purpose of mac filtering is if u can't connect to anything or if I'm doing something wrong. thanks!
- Joined
- Jan 7, 2014
- Messages
- 14,600
- Trophies
- 4
- Location
- Another World
- Website
- www.gbatemp.net
- XP
- 25,207
- Country
You can apply a parental control to a specific mac adress, and block IPs/URLs of your choice just fine on many routers.
I did with my WiiU MAC adress, and it works perfectly
I did with my WiiU MAC adress, and it works perfectly
MAC filtering would only affect the traffic from your Wii U to your router and out to the internet (and vice versa). If you cannot connect to your hosted files then you've got a setting that's not correct.
1. Can you browse to your self hosted files using another node on your network? (computer, tablet, phone etc.)
2. What are you using to self host? XAMPP? Mongoose?
3. Did you change the port on the webserver software to something other than the default? (port 80)
You need to test using something that is not hosting the files. Try the browser on your phone if you don't have another computer or tablet to test with. Really anything that has an internet connection using the wifi or wired and has a browser will work to test.
Yes I understand that. But we need to first make sure that ANY device can get to the website that Mongoose is running on. This is just to test that the webhosting is first working. After you are able to browse to your hosted files using a different device than the laptop, then you can move on to testing the Wii U.
You will always be able to browse the files on the laptop that is hosting them. That's because it doesn't have to go out and back into a different site. It just shows you what is running locally. That doesn't mean that you have it set up to properly send data OUT.
If you are unable to browse to your hosted files using a different device other than your laptop then most likely mongoose isn't working or is misconfigured.
By default it uses port 80 for listening port. If you are using skype or a number of other programs then port 80 will already be in use. I would suggest changing this to something that you KNOW is not in use. For example. I have mine set to 12345. (In mongoose setting., set listening ports to 12345, stop and restart).
Then when test the site on a different device OTHER than the laptop make sure to add the port number to the url.
For example:
http://192.168.0.145:12345/
Last edited by Kafluke,
Woah, backup. You have completely blocked the mac address of the wii u on your router? If you do this then you will not be able to browse ANY sites, locally or online. You have to setup filtering so you tell it "block all these nintendo IP addresses whenever this MAC address tries to access them". You aren't suppose to just tell your wifi router to completely block the wii u MAC address. This is the same thing as saying, "no wifi network access for wii u... at all"
Good at least that is working. No need to change the port if you can see the wii u homebrew list on your phone. Mongoose is up and running. Now let's fix your MAC address issue.
Hmmmm. According to the definitive guide:
Additional preventative measures:
A. Block by URL Filtering (allows internet access still)
B. Block your Wii U's MAC Address (no internet access at all, can only run self-hosted files)
So this says that you should still be able to see self hosted files but as a network engineer I would say that this highly depends on your router. To me it looks like you have completely blocked all access to your wii u by blocking the MAC address.
It does say that it is additional preventative measures. I don't use MAC filtering personally. I just use TubeHax DNS. It has always done the trick for me.
As long as you have TubeHax DNS working and we can confirm that it is still working for everyone, why don't you stop blocking on the router side and test just to make sure that we are troubleshooting the correct issue.
Just make sure that TubeHax is actually set up or you'll get updated.
Last edited by Kafluke,
For now stop blocking on your router end and test with just TubeHax to make sure we are looking at the right issue.
A lot of firmware that comes stock on routers are junk. Don't forget lots of users switch to tomato, dd-wrt, or open-wrt.
Also, proper mac filtering will only block what you tell it to and not all of the internet. As Kafluke said, it's highly dependent on the router, but if you really want to do this route and your firmware is the issue, I'd look into seeing if I could put one of those on my router. I have met some routers who just do not like to run the other firmwares though (frequent restarts etc).
Basically, MAC Filtering uses a device identification number to block or allow only certain things, or everything, and require making separate rules for multiple applications. The guide is wrong when it says it will block everything except LAN. It's just some routers are trash when it comes to options.
Also, proper mac filtering will only block what you tell it to and not all of the internet. As Kafluke said, it's highly dependent on the router, but if you really want to do this route and your firmware is the issue, I'd look into seeing if I could put one of those on my router. I have met some routers who just do not like to run the other firmwares though (frequent restarts etc).
Basically, MAC Filtering uses a device identification number to block or allow only certain things, or everything, and require making separate rules for multiple applications. The guide is wrong when it says it will block everything except LAN. It's just some routers are trash when it comes to options.
Last edited by EclipseSin,
Similar threads
