Configuring static DHCP

Is it possible using the router as a DHCP server with a static configuration.
I.e. same IP for the same user

Make a dhcp pool mapping only one mac address.
Look example below.
ip dhcp pool statichost
host 192.168.1.1 255.255.255.0
hardware-address 0010.a3fd.2f9f
client-name something
domain-name test.com
default-router 192.168.1.254
dns-server 192.168.1.10
lease 1 0

Similar Messages

[Q]: Static DHCP Lease with the WRT54GL...

Hello,
I have replaced my old D-LINK router with a WRT54GL wireless router.
On the old router I could configure static DHCP entries, providing the same IP address to specific MAC addresses (from my different devices at home), and still continue to receive all other settings via DHCP (Like DNS servers that my ISP changes from time to time).
Using static IP addresses is not an option due that the ISP I'm connected changes the DNS settings frequently and my computers can't connect to the internet. Setting the WRT54GL router as DNS server on my computers is also not practical.
On the WRT54GL I could not find how to create static (or permanent) DHCP leases. Is this possible?.. is this in the wish list for future releases of the firmware?
Thanks in advance.

Thanks for the quick response.
I was surprised that this (and maybe other) Linksys routers does not provide this simple feature.
All DHCP servers I know provide this feature and most of the unmanaged routers that provide DHCP services have this feature.
--- Ricky.

RV180W with 1.0.2.6 Firmware - Static DHCP problem

Today I installed the 1.0.2.6 Firmware on a RV180W. I only have now two problems regarding the Static DHCP support in the GUI.
1. Via the Networking > LAN (Local Network) > Static DHCP I have no buttons to Add a new static Lease.
2. Via the Networking > LAN (Local Network) > DHCP Lease Clients I can thick a Lease and click on Make Static IP. The result is an error: Operation failed.
Is this a bug or am I doing something wrong?

RV180 f/w 1.0.4.14
Static DHCP page – missing buttons Add, Edit, Delete since some f/w update.
Apparently Cisco has changed syntax since some f/w version I don't remember.
Fix:
1. Backup unit's settings. Use some editor to check that the syntax for the section DhcpfixedIpAddress is correct in the configuration file. The main clue is a new variable "Name". An example bellow displays 2 lines in Static DHCP page. If necessary make changes most likely including upper/lower case conversion for MacAddr and the lines order.
2. Change checksum to 0.
systemConfig[1]["checksum"]="0"
3. Restore unit's settings from the edited configuration file. I have got missing buttons back only after the above procedure. Any other suggested solutions didn't work for me.
Correct syntax for newer firmware:
ifStatic[4]["SecondaryDns"] = ""
DhcpfixedIpAddress = {}
DhcpfixedIpAddress[1] = {}
DhcpfixedIpAddress[1]["MacAddr"] = "bc:ee:7b:e3:3b:0a"
DhcpfixedIpAddress[1]["Name"] = "Computer01"
DhcpfixedIpAddress[1]["IpAddr"] = "192.168.1.100"
DhcpfixedIpAddress[1]["LogicalIfName"] = "LAN"
DhcpfixedIpAddress[1]["_ROWID_"] = "1"
DhcpfixedIpAddress[2] = {}
DhcpfixedIpAddress[2]["MacAddr"] = "00:15:e9:6a:0f:15"
DhcpfixedIpAddress[2]["Name"] = "Unknown"
DhcpfixedIpAddress[2]["IpAddr"] = "192.168.1.101"
DhcpfixedIpAddress[2]["LogicalIfName"] = "LAN"
DhcpfixedIpAddress[2]["_ROWID_"] = "2"
DhcpLdapServerInfo = {}
Old syntax incompatible with newer firmware:
ifStatic[4]["SecondaryDns"] = ""
DhcpfixedIpAddress = {}
DhcpfixedIpAddress[1] = {}
DhcpfixedIpAddress[1]["IpAddr"] = "192.168.1.100"
DhcpfixedIpAddress[1]["LogicalIfName"] = "LAN"
DhcpfixedIpAddress[1]["_ROWID_"] = "1"
DhcpfixedIpAddress[1]["MacAddr"] = "BC:EE:7B:E3:3B:0A"
DhcpfixedIpAddress[2] = {}
DhcpfixedIpAddress[2]["IpAddr"] = "192.168.1.101"
DhcpfixedIpAddress[2]["LogicalIfName"] = "LAN"
DhcpfixedIpAddress[2]["_ROWID_"] = "2"
DhcpfixedIpAddress[2]["MacAddr"] = "00:15:E9:6A:0F:15"
DhcpLdapServerInfo = {}

Failing to execute Check: systems configured with DHCP

Recommendation: Oracle supports installations on systems with DHCP-assigned public IP addresses. However, the primary network interface on the system should be configured with a static IP address in order for the Oracle Software to function properly. See the Installation Guide for more details on installing the software on systems configured with DHCP.
Status: Not Executed
Why is Oracle failing to execute the check? What sort of check does Oracle run for DHCP IPs?
Any help will be appreciated.
Thanks

A server is not supposed to work with DHCP but with a fixed IP address. Enterprise Manager DB Control Console will only work with a fixed IP address, if ever either the IP or the hostname change then EM won't work any more unless it is reconfigured.
The purpose of the loopback adapter is to provide a fixed IP address on a dynamic assigned environment. You should make sure once you fix the IP address by means of DHCP to name this IP address in the host file at c:\windows\system32\drivers\etc\host.
~ Madrid
http://hrivera99.blogspot.com/

EA6700 DHCP Reservation (Static DHCP) limit

Hi,
just got an EA6700. Setup was the most difficult I've ever experienced in many years of Wifi/router config. I almost packed it back up to return it. The cloud thing is absurd. Using CAPTCHA that does not even display the CAPTCHA image is even worse.
Alright, I succeeded in using the local admin login and set up the router. Actually the plan was to have it just be a wireless access point, using my Cisco RV042 as the router and DHCP server. Well that 'dream' was squashed right quick. That **bleep** RV042 blew up when I added one more Static DHCP entry. Poof. 'No more SYSTEM' errors in a few spots. On reboot the darn thing does not come back up. This after the RV042 needed to be reset after I used a quote or some other 'illegal' character in a static DHCP entry. What a piece of amateur junk.
So. Tomorrow I will reset the RV042 again and relegate it to just doing WAN failover, nothing more. The EA6700 will be the router and DHCP server. So my question (sorry for the ranting) is how many DHCP reservations the EA6700 can handle. I'll probably need 75. I assign DHCP reservations for LAN stability and to prevent IP address collisions.
Please note that I'm not talking about static IP addresses. I have a few of those too but I know they are different from DHCP reservations.
Thanks,
Sander

It's highly unlikely the EA6700 can handle 70+ DHCP reservations. But I don't know for sure.
My advice is to go back to plan A and use EA6700 as AP.
Configure it for bridge mode. Be sure to "specify and IP address". Don't use "obtain IP address automatically" when configuring bridge mode.
http://kb.linksys.com/Linksys/ukp.aspx?pid=94&vw=1&articleid=25714
Edit: don't configure ea6700 for bridge mode while it's connected to your main router. You've probably noticed by now that the EA routers will automatically change their IP to 10.x.x.x if they detect a double NAT. Which I why I suggest keeping it disconnected from main router when configuring.

Does 3550/3560 support static dhcp snooping binding?

Hi All,
I'm currently studing DHCP snooping.
Just found there is no 'ip dhcp snooping bindg' syntax on 3550/3560, Is there any way to add static dhcp snooping entry?
If there is no way, and the switch intruduced ip arp inspect and ip source guard, and a untrust port connected to an end host with static IP address assigned, in such situation, is it right that I have to add static 'ip arp inspection filter' and ' ip source binding' to makes the end host can send packet out?
Thanks for any comments.
Regards,
Yi

check the following link for configuration of DHCP snooping
http://packetlife.net/blog/2010/aug/18/dhcp-snooping-and-dynamic-arp-inspection/
http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst6500/ios/12-2SX/configuration/guide/book/snoodhcp.html

PS Script to Automate NIC Teaming and Configure Static IP Address based off an Existing Physical NIC

# Retrieve IP Address and Default Gateway from static IP Assigned NIC and assign to variables.
$wmi = Get-WmiObject Win32_NetworkAdapterConfiguration -Filter "IPEnabled = True" |
Where-Object { $_.IPAddress -match '192\.' }
$IPAddress = $wmi.IpAddress[0]
$DefaultGateway = $wmi.DefaultIPGateway[0]
# Create Lbfo TEAM1, by binding “Ethernet” and “Ethernet 2” NICs.
New-NetLbfoTeam -Name TEAM1 -TeamMembers "Ethernet","Ethernet 2" -TeamingMode Lacp -LoadBalancingAlgorithm TransportPorts -Confirm:$false
# 20 second pause to allow TEAM1 to form and come online.
Start-Sleep -s 20
# Configure static IP Address, Subnet, Default Gateway, DNS Server IPs to newly formed TEAM1 interface.
New-NetIPAddress –InterfaceAlias “TEAM1” –IPAddress $IPAddress –PrefixLength 24 -DefaultGateway $DefaultGateway
Set-DnsClientServerAddress -InterfaceAlias “TEAM1” -ServerAddresses xx.xx.xx.xx, xx.xx.xx.xx
Howdy All!
I was recently presented with the challenge of automating the creation and configuration of a NIC Team on Server 2012 and Server 2012 R2.
Condition:
New Team will use static IP Address of an existing NIC (one of two physical NICs to be used in the Team). Each server has more than one NIC.
Our environment is pretty static, in the sense that all our servers use the same subnet mask and DNS server IP Addresses, so I really only had
to worry about the Static IP Address and the Default Gateway.
1. Retrieve NIC IP Address and Default Gateway:
I needed a way to query only the NIC with the correct IP Address settings and create required variables based on that query. For that, I
leveraged WMI. For example purposes, let's say the servers in your environment start with 192. and you know the source physical NIC with desired network configurations follows this scheme. This will retrieve only the network configuration information
for the NIC that has the IP Address that starts with "192." Feel free to replace 192 with whatever octet you use. you can expand the criteria by filling out additional octects... example:
Where-Object
$_.IPAddress
-match'192\.168.' } This would search for NICs with IP Addresses 192.168.xx.xx.
$wmi
= Get-WmiObject
Win32_NetworkAdapterConfiguration
-Filter "IPEnabled = True"
|
Where-Object {
$_.IPAddress
-match '192\.' }
$IPAddress
= $wmi.IpAddress[0]
$DefaultGateway
= $wmi.DefaultIPGateway[0]
2. Create Lbfo TEAM1
This is a straight forward command based off of New-NetLbfoTeam. I used "-Confirm:$false" to suppress prompts.
Our NICs are named “Ethernet” and “Ethernet 2” by default, so I was able to keep –TeamMembers as a static entry.
Also added start-sleep command to give the new Team time to build and come online before moving on to network configurations.
New-NetLbfoTeam
-Name TEAM1
-TeamMembers "Ethernet","Ethernet 2"
-TeamingMode SwitchIndependent
-LoadBalancingAlgorithm
Dynamic -Confirm:$false
# 20 second pause to allow TEAM1 to form and come online.
Start-Sleep
-s 20
3. Configure network settings for interface "TEAM1".
Now it's time to pipe the previous physical NICs configurations to the newly built team. Here is where I will leverage
the variables I created earlier.
There are two separate commands used to fully configure network settings,
New-NetIPAddress : Here is where you assign the IP Address, Subnet Mask, and Default Gateway.
Set-DnsClientServerAddress: Here is where you assign any DNS Servers. In my case, I have 2, just replace x's with your
desired DNS IP Addresses.
New-NetIPAddress
–InterfaceAlias “TEAM1”
–IPAddress $IPAddress
–PrefixLength 24
-DefaultGateway $DefaultGateway
Set-DnsClientServerAddress
-InterfaceAlias “TEAM1”
-ServerAddresses xx.xx.xx.xx, xx.xx.xx.xx
Hope this helps and cheers!

I've done this before, and because of that I've run into something you may find valuable.
Namely two challenges:
There are "n" number of adapters in the server.
Adapters with multiple ports should be labeled in order.
MS only supports making a LBFO Team out of "like speed" adapters.
To solve both of these challenges I standardized the name based on link speed for each adapter before creating hte team. Pretty simple really! FIrst I created to variables to store the 10g and 1g adapters. I went ahead and told it to skip
any "hyper-V" ports for obvious reasons, and sorted by MAC address as servers tend to put all thier onboard NICs in sequentially by MAC:
$All10GAdapters = (Get-NetAdapter |where{$_.LinkSpeed -eq "10 Gbps" -and $_.InterfaceDesription -notmatch 'Hyper-V*'}|sort-object MacAddress)
$All1GAdapters = (Get-NetAdapter |where{$_.LinkSpeed -eq "1 Gbps" -and $_.InterfaceDesription -notmatch 'Hyper-V*'}|sort-object MacAddress)
Sweet ... now that I have my adapters I can rename them into something standardized:
$i=0
$All10GAdapters | ForEach-Object {
Rename-NetAdapter -Name $_.Name -NewName "Ethernet_10g_$i"
$i++
$i = 0
$All1GAdapters | ForEach-Object {
Rename-NetAdapter -Name $_.Name -NewName "Ethernet_1g_$i"
$i++
Once that's done Now i can return to your team command but use a wildcard sense I know the standardized name!
New-NetLbfoTeam -Name TEAM1G -TeamMembers Ethernet_1g_* -TeamingMode SwitchIndependent -LoadBalancingAlgorithm Dynamic -Confirm:$false
New-NetLbfoTeam -Name TEAM10G -TeamMembers Ethernet_10g_* -TeamingMode SwitchIndependent -LoadBalancingAlgorithm Dynamic -Confirm:$false

Cisco Catalyst 6500 version 12.2(33)SXI13 configured as DHCP server for a VLAN responds to Windows 7 client with status code NOA

Can anyone help figure out why the Catalyst 6509 is not able to assign an IPv6 address? Thank you.
Cisco Catalyst 6500 version 12.2(33)SXI13 configured as DHCP server for a VLAN responds to Windows 7 client with status code NOADDRS-AVAIL(2). My configuration on the 6500 for the DHCPv6 server is:
ipv6 dhcp database disk0://DHCPV6-DB
ipv6 dhcp pool VLAN206IPV6
prefix-delegation pool VLAN206IPV6-POOL
dns-server 2620:B700:0:1001::53
domain-name global.bio.com
ipv6 local pool VLAN206IPV6-POOL 2620:B700:0:12C7::/65 65
interface Vlan206
description *** IPv6 Subnet ***
ip address 10.2.104.2 255.255.255.0
ipv6 address 2620:B700:0:12C7::2/64
ipv6 nd prefix 2620:B700:0:12C7::/64 14400 14400 no-autoconfig
ipv6 nd managed-config-flag
ipv6 dhcp server VLAN206IPV6
standby version 2
standby 0 ip 10.2.104.1
standby 0 preempt
standby 6 ipv6 2620:B700:0:12C7::1/64
standby 6 preempt
I'm getting a result from my debug as follows:
Apr 10 16:28:02.873 PDT: %LINK-3-UPDOWN: Interface GigabitEthernet2/2, changed state to up
Apr 10 16:28:02.873 PDT: %LINK-SP-3-UPDOWN: Interface GigabitEthernet2/2, changed state to up
Apr 10 16:28:02.877 PDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet2/2, changed state to up
Apr 10 16:28:03.861 PDT: IPv6 DHCP: Received SOLICIT from FE80::5D5E:7EBD:CDBF:2519 on Vlan206
Apr 10 16:28:03.861 PDT: IPv6 DHCP: detailed packet contents
Apr 10 16:28:03.861 PDT: src FE80::5D5E:7EBD:CDBF:2519 (Vlan206)
Apr 10 16:28:03.861 PDT: dst FF02::1:2
Apr 10 16:28:03.861 PDT: type SOLICIT(1), xid 8277025
Apr 10 16:28:03.861 PDT: option ELAPSED-TIME(8), len 2
Apr 10 16:28:03.861 PDT: elapsed-time 101
Apr 10 16:28:03.861 PDT: option CLIENTID(1), len 14
Apr 10 16:28:03.861 PDT: 00010001195FD895F01FAF10689E
Apr 10 16:28:03.861 PDT: option IA-NA(3), len 12
Apr 10 16:28:03.861 PDT: IAID 0x0FF01FAF, T1 0, T2 0
Apr 10 16:28:03.861 PDT: option UNKNOWN(39), len 32
Apr 10 16:28:03.861 PDT: option VENDOR-CLASS(16), len 14
Apr 10 16:28:03.861 PDT: option ORO(6), len 8
Apr 10 16:28:03.861 PDT: DOMAIN-LIST,DNS-SERVERS,VENDOR-OPTS,UNKNOWN
Apr 10 16:28:03.861 PDT: IPv6 DHCP: Option IA-NA(3) is not supported yet
Apr 10 16:28:03.861 PDT: IPv6 DHCP: Sending ADVERTISE to FE80::5D5E:7EBD:CDBF:2519 on Vlan206
Apr 10 16:28:03.861 PDT: IPv6 DHCP: detailed packet contents
Apr 10 16:28:03.861 PDT: src FE80::21D:E6FF:FEE4:4400
Apr 10 16:28:03.861 PDT: dst FE80::5D5E:7EBD:CDBF:2519 (Vlan206)
Apr 10 16:28:03.861 PDT: type ADVERTISE(2), xid 8277025
Apr 10 16:28:03.861 PDT: option SERVERID(2), len 10
Apr 10 16:28:03.865 PDT: 00030001001DE6E44400
Apr 10 16:28:03.865 PDT: option CLIENTID(1), len 14
Apr 10 16:28:03.865 PDT: 00010001195FD895F01FAF10689E
Apr 10 16:28:03.865 PDT: option STATUS-CODE(13), len 15
Apr 10 16:28:03.865 PDT: status code NOADDRS-AVAIL(2)
Apr 10 16:28:03.865 PDT: status message: NOADDRS-AVAIL

Hello,
maybe hitting the following bug.
Pv6 Address Assignment Support for IPv6 DHCP Server
CSCse81385
Hope this helps

Configuring Static Route Tracking Using ASDM 7.1(3) ASA 9.1(2)

I have recently updated my ASA5520 to 9.1(2) and I am using ASDM 7.1(3) to configure Static Route Tracking. I have done this previoussy in earlier version of ASDM without a problem. There seems to be a new field in the Tracked Options section. What is the "Target Interface"? Is it the interface I want to use as the standby route when the Monitor fails? Or is it the Interface that is doing the monitoring?
I have looked through Cisco ASA Series General Operations ASDM Configuration Guide Software Version 7.1, as well as older ASDM books and this field is never listed or described.

Hi,
The target interface will be the interface through which you will be polling some destination IP address with ICMP Echos to determine if the route through that interface is still valid.
So in your case you would use "Outside"
Heres the link to the ASA Command Reference listing the above "type" command under the "sla monitor 1" configuration
http://www.cisco.com/en/US/docs/security/asa/command-reference/t2.html#wp1568359
- Jouni

All STATIC DHCP Assignments wiped out

Out of the clear blue sky, my Verizon Fios Router (the new Gateway G1100) suddenly had none of my static DHCP Assignments. They all vanished! I have no idea how, but on January 3rd, I had a fully functioning router with everything set the way I want, and I had a backup of the settings.
Today, I'm trying to remote in to some PCs on my lan and their not responding. Well of course they're not, they have new IP addresses assigned dynamically because my entire address reservation entries were gone!
What the hell? Best guess I have is VERIZON pushed a firmware update that screwed me and never told me. The fact they can push updates at their whim kills me! I'm stable, don't push me jack S%$#. Don't fix what isn't broken. Notify me, let me opt in!!!!
I'm so hating my switch to verizon!
Has anyone else had this happen?

Verizon is pushing a firmware update to the Quantum routers. It adds useful functionality to the router. See this thread for the details:
http://forums.verizon.com/t5/FiOS-Internet/Fios-Quantum-Gateway-1-1-Enhancements/m-p/774233#M54060
My router was updated yesterday. Unfortunately, my router lost it's static DHCP assignments as well. I had even saved my router config prior to the upgrade as I was concerned about loosing my settings. A restore of the router config after the update did not recover my static DHCP settings. I'm not sure what else wasn't restored.
While I do like the improved features that the new firmware provides (Guest WiFi is a big deal for me), I too am disappointed in how this upgrade cleared out some settings and how we users have no control over the process. I've heard that we're supposed to receive an email about the upgrade, but I never got one.
Good Luck.
If a forum member gives an answer you like, give them the Kudos they deserve. If a member gives you the answer to your question, mark the answer as Accepted Solution so others can see the solution to the problem.

How to get Airport Extreme to Provide DNS for Static DHCP

I set up some static DHCP entries on my Airport Extreme 802.11n. How do I make it provide DNS resolution for these devices?
For example, I defined a device which I named "tvpc". With my old router, once I added a static DHCP reservation and provided it with a name, I could "ping tvpc" from any device on my network, and my old router would provide the DNS resolution, because it provided DNS service for all DHCP entries.
I suspect that the answer is, "Apple routers don't do this." If that is the case, how do other people get name resolution for the non-Apple devices you set up with static DHCP? Do you use /etc/hosts files?

I set up some static DHCP entries on my Airport Extreme 802.11n. How do I make it provide DNS resolution for these devices?
"Apple routers don't do this."
how do other people get name resolution for the non-Apple devices you set up with static DHCP?
They don't.
Suggest that you use another router with the capabilities that you need.

Configure static PAT for port range

Hi,
could someone help with this:
we have an ASA 5510 version 8.2 and ASDM 6.4. we want to configure a static PAT for a range of TCP and UDP port. in the nat configuration window we have just to enter one port ( range are note accepted).
Thanks,

Hi,
In software levels 8.2 and below the only option is to generate a separate configurations for each port. This is easiest achieved through the CLI and using some text editor to help generate the possibly large configurations.
On ASA software 8.3 and above (where NAT format was completely redone) you have the option to use a single "nat" command to configure Static PAT for a continuous range of ports.
So your option is to either generate a separate "static" configuration for each port or upgrade the software to a newer one to be able to do Static PAT for a range of ports.
Naturally the update involves rewriting the current NAT configuratins into a new format even though booting to newer software usually converts the configurations automatically but with varying success.
- Jouni

WRT54GC - Port ranges, triggering, static DHCP.

Recently got a WBR54GC router and it works great on the network. I don't use it wirelessly, but hey, it was cheap, may aswell go for it! The firmware though has been less-than comforting. It works, but there are a few gaudy bugs.
Port range forwarding refuses to work on ports higher than 32768, and ports higher than 20000 are often very flaky to get the router to properly take. After saving the settings the port range often appears vastly incorrect or even impossible (ports 104824 to 0 for example).
Second comes port triggering, which puzzles me. There's no option to set if the trigger port or the forwarded range should be UDP, TCP, or both. It simply asks for two ranges of ports, one to monitor and the other to open, and it only seems to do this over TCP ports. Currently, I swap the computer's IP back and forth in the forwarded ports page to the computer I'm using. Its a fix but its a pain in the ass.
Finally comes static DHCP, the settings page of which seems to not properly remove settings. After I entered an IP/MAC combination in the first few avaliable boxes I went back to change one. The router then told me that the DHCP client I entered was already in the table? Strange. I opened the static DHCP page again and now there was nothing! Alright, enter all the details again, save settings. It again told me that the DHCP client was already in the table. Close, open it again, still blank. I tried to save the settings with the DHCP client table completely blank thinking this could correct it. Funny, I'm still entering duplicates even though the page is blank. I ended up recording my settings and doing a factory reset to wipe the table correctly.
Firmware Version: v1.02.8, latest of course. Searching these forums, I did manage to find a thread that mentioned the port range forwarding issue, the first one I talked about. The problem is the Rapidshare link given to a beta firmware was dead. Since then I'd been looking for this new firmware beta to hopefully resolve most of these issues, but without much luck.
Any help greatly appreciated.

This problem is an obvious firmware bug.
Why the hell do all router companies sell a professional looking product, but with firmware that looks like a group of random twekaers and hackers threw together?
No offence. My D-Link router has misspelt words, which is absolutely sad.

(ask) WRT54GC Static DHCP client name always "unknown"

I use WRT54GC for gateway for my internet connection. I have several wired computer that connect to switch that connet to WRT54GC. I have set Static DHCP as in manual book and name each MAC address. But in DHCP client list the name always show "unknown". Anyway to fix this? Thank you.
Message Edited by scannerfm77 on 07-29-2008 08:12 PM

The router DHCP will not show client using Static IP in the network .....
If you are using "Obtain IP settings" .... then the IP address ...computer name & MAC address ... will be there ...

WRT320N static DHCP leases

hi,
i have a wrt320n. it runs fine, but i'm in need of static DHCP leases.
the reason is simple: if one uses static port forwards for applications that doesn't support upnp, and the client gets a different ip than what's specified for the port forwards, it all gets messed up.
i couldn't find any reference for this feature neither in the manual nor in the router web interface, so i guess it's not possible ATM.
could you please add support for this (quite basic) feature?
thanks in advance.
Solved!
Go to Solution.

Well i think the feature which you are trying to look under the linksys router its not possible. I think you need to wait until linksys release the new firmware along with the DHCP Leases.

Configuring static DHCP

Similar Messages

Maybe you are looking for