This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
I am setting it up with my ps4 and wondering if I set a static ip address, which is under the lan settings, will it apply to non lan wifi connections as well?
Reserving an address for a specific device works both for LAN and WiFi devices. If you add a reserved address for a device, it'll always get the same IP from the DHCP no matter if connected with a cable or wirelessly
Just make sure you use the correct MAC address. If a device has both wired and wireless capabilities, it'll have 2 different MAC addresses, one for the wired and one for the WiFi
Yes, and it's not a static address but a DHCP reserved one, based on the device's MAC address. Static addresses are set on the device(s) itself, not in the router
considering i want to set up a port forwarding system for my ps4, are these functionally the same thing or i should i still set up a static ip on the ps4?
if i set up a static ip, is there any reason for this reserved ip?
> I am setting it up with my ps4 and wondering if I set a static ip > address, which is under the lan settings, [...]
Terminology: A "static" address is configured on the device itself. What you configure on the (DHCP server on the) router is a reserved dynamic address, not a static address.
> [...] will it apply to non lan wifi connections as well?
What is the actual problem which you are trying to solve?
A network "connection" does not have an IP address; a network interface does. Apparently, your "my ps4" has two network interfaces, one wired (Ethernet), and one wireless.
Address Reservation reserves a particular IP address to be associated with a particular MAC address. Normally, every network interface in your LAN has its own (locally) unique MAC address. Reserving an IP address for one network interface (specified by its MAC address) does not automatically reserve that IP address for any other network interface (which should have its own, different MAC address), even if both those interfaces are in the same box ("my ps4").
You can try it, but I'd guess that the router won't let you reserve the same LAN IP address for two different MAC addresses. If that's what you're trying to do.
Note that, strictly speaking, your "my ps4" does not have an IP address. A network interface in your "my ps4" can have an IP address. If there are two network interfaces in your "my ps4", then each one can have its own IP address. (I'd bet that each one has its own MAC address.) Trying to give the same IP address to both network interfaces in your "my ps4" is more likely to cause trouble than not.
i reserved an ip address under the lan settings for my ps4 based on it's mac address.
the issue is that this was under lan settings on the router. that is why i am not sure if it will apply to the wireless connection i am using with it.
because it was under lan settings...is the thing.
also i know i can set a static ip on the ps4 interface.
my question is if that is necessary or if the dhcp i set up under lan settings will have the same effect.
i am only using my ps4 with this router, so that is why i am thinking the dhcp settings alone might work for, it in terms of setting up port forwarding
Reserving an address for a specific device works both for LAN and WiFi devices. If you add a reserved address for a device, it'll always get the same IP from the DHCP no matter if connected with a cable or wirelessly
Just make sure you use the correct MAC address. If a device has both wired and wireless capabilities, it'll have 2 different MAC addresses, one for the wired and one for the WiFi
> i reserved an ip address under the lan settings for my ps4 based on > it's mac address.
Not exactly. See 'Note that, strictly speaking, your "my ps4" does not have an IP address. [...]', above.
> the issue is that this was under lan settings on the router. that is > why i am not sure if it will apply to the wireless connection i am using > with it.
"LAN" = "Local-Area Network". "Local-Area" and "wired" are spelled differently for a reason. A device with a wireless connection to your router is as much a part of your LAN as a device with a wired connection.` You do Address Reservation for all your devices in the same place.
> because it was under lan settings...is the thing.
No, that's not the thing.
> also i know i can set a static ip on the ps4 interface.
I'll try again...
> Terminology: A "static" address is configured on the device itself. > What you configure on the (DHCP server on the) router is a reserved > dynamic address, not a static address.
Do you mean a static address, or a reserved dynamic address? And for _which_ "the ps4 interface"?
> [...] Apparently, your "my ps4" has two network interfaces, one wired > (Ethernet), and one wireless.
Still true, isn't it?
> my question is if that is necessary or if the dhcp i set up under lan > settings will have the same effect.
If you reserved an IP address for the Ethernet interface of the PS4, then you reserved an IP address for the _Ethernet_ interface of the PS4.
The wireless interface of the PS4 is a different interface, with a different MAC address (I'd guess), so a reservation for one of these interfaces is not a reservation for both interfaces.
> [...] i am thinking the dhcp settings alone might work for, it in > terms of setting up port forwarding
What, exactly, are these "the dhcp settings"?
> What is the actual problem which you are trying to solve?
Still a mystery.
> [...] setting up port forwarding
Are you trying to set up port forwarding so that it works no matter which network interface you use on the PS4?
> [...] Trying to give the same IP address to both network interfaces > in your "my ps4" is more likely to cause trouble than not.
do you even own a netgear router or one of their gaming routers? if you knew anything about the interface of the router, maybe you would understand what i am talking about a bit better.
> [...] if you knew anything about the interface of the router, maybe > you would understand what i am talking about a bit better.
If you would identify the actual problem which you are trying to solve, _then_ I might understand what you're trying to do. But, I'm willing to stay ignorant, if that's what you'd prefer.
> Reserving an address for a specific device works both for LAN and WiFi > devices. [...]
Because, as explained above, they're _all_ "LAN devices".
> [...] If you add a reserved address for a device, it'll always get the > same IP from the DHCP no matter if connected with a cable or > wirelessly
Have you actually run this experiment in the real world, or only in your head? (I have. See below.)
Define "device". Does my MacBook ("13-inch, Aluminum, Late 2008", "OS X El Capitan", "Version 10.11.6") qualify as a "device"?
My MacBook has an IP address reserved (for its wireless interface) of "10.0.0.29". You seem to be claiming that if I disable its wireless interface, and connect its Ethernet interface to the same router, then its Ethernet interface will also get that same IP address. Or did I misunderstand?
Surprise!!! It doesn't. For its Ethernet interface, it gets an address from the DHCP pool ("10.0.0.227"). Around here, that's _not_ "the same IP [address] from the DHCP [server] no matter if connected with a cable or wirelessly".
As explained above (repeatedly), "a device" does _not_ have an IP
address (or a MAC address). A _network_interface_ has these properties.
If "a device" has only one network interface, then you can usually ignore the distinction between a device and its (one and only) network interface, but when "a device" has multiple network interfaces, then you ignore that distinction at your peril.
I'd explain it all again, but if the first or second time didn't do the job, then I might be wasting my time with more attempts.
do you even own a netgear router or one of their gaming routers? if you knew anything about the interface of the router, maybe you would understand what i am talking about a bit better.
sheesh
He loves to make it sound like he knows everything, but rest of us are big dummies.
Bottom line on the question is this. When you make a DHCP reservation based on client MAC the DHCP server could care less what the client connection is, wired or wireless. The DHCP server sees the request from the client including the MAC. DHCP server checks and says hay I have an IP address I need to give to that client. No real mystery about what connection.
> He loves to make it sound like he knows everything, [...]
I frequently admit to my ignorance on various subjects, but, in this case, I actually demonstrated my claim. Read it again?
> Bottom line on the question is this. [...]
That might be _your_ "Bottom line". It's not mine.
> [...] When you make a DHCP reservation based on client MAC the DHCP > server could care less what the client connection is, wired or wireless. > [...]
I'll assume that you meant "could _not_ care less", but, as previously explained (repeatedly), the "client MAC [address]" is not a "client [device] MAC [address]"; it's a "client _interface_ MAC address", and, as previously stated, I would not expect the wired and wireless interfaces in any particular client device to have the same MAC address.
In my MacBook example, its Ethernet MAC address is "00:23:32:c6:6d:be", and its wireless MAC address is "00:23:6c:87:9c:83". See the difference? And that's why my address reservation for its wireless interface has no direct effect on the address granted to its Ethernet interface.
> [...] No real mystery about what connection.
If you say so. But some of us know-it-all types prefer to run the experiment before making such pronouncements. Because "believing" and "knowing" are spelled differently for a reason.
> [...] also yes that was the point of my question
"that"? What?
I'm curious...
You've marked this thread as "Solved!". I didn't think that it was, but it's your thread, and there are many things which I don't understand, including exactly what you wish to do. What's left to discuss is not clear to me.
Also, do you really believe that insulting the only participant here who seems to have any grasp at all on the implications of multiple network interfaces on one device will be an effective way to get him to help you (further)? Let's run that experiment, and see what happens.
That's not strictly true. The second half of the "solution" ("If a device has both wired and wireless capabilities, it'll have 2 different MAC addresses [...]") makes sense. The (contradictory) first half ("If you add a reserved address for a device, it'll always get the same IP from the DHCP no matter if connected with a cable or wirelessly") is the part which departs from reality. Because (again) "a device" is not what has an address; a network _interface_ is what has an address.)
