skyhook
06-05-2008, 01:48 AM
Automatic IP address from 169.254.0.0/16 on NS: can you explain how the NS generate and autoassign this IP address?
TNX
TNX
View Full Version : Automatic IP like 169.254.0.0/16 on NS: how autoassign?
WHT
06-05-2008, 08:19 AM
Automatic IP address from 169.254.0.0/16 on NS: can you explain how the NS generate and autoassign this IP address?
Its not coming from the NS, its a default Windows IP addy when the computer is set for "Obtain an IP address automatically", but can't connect to a DHCP server, i.e. a router. See http://en.wikipedia.org/wiki/Classful_network for an explanation of 169.254.0.xxx.
Could be several reasons: You're not associating your client with the NS, the NS isn't set to be a DHCP server...
Its not coming from the NS, its a default Windows IP addy when the computer is set for "Obtain an IP address automatically", but can't connect to a DHCP server, i.e. a router. See http://en.wikipedia.org/wiki/Classful_network for an explanation of 169.254.0.xxx.
Could be several reasons: You're not associating your client with the NS, the NS isn't set to be a DHCP server...
skyhook
06-05-2008, 09:37 AM
Automatic IP address from 169.254.0.0/16 on NS: can you explain how the NS generate and autoassign this IP address?
Its not coming from the NS, its a default Windows IP addy when the computer is set for "Obtain an IP address automatically", but can't connect to a DHCP server, i.e. a router. See http://en.wikipedia.org/wiki/Classful_network for an explanation of 169.254.0.xxx.
Could be several reasons: You're not associating your client with the NS, the NS isn't set to be a DHCP server...
Dear WHT,
I talk about the IP address self-assigned by NS itself..
Try to connect a NS at you PC and start the discovery tool... you can see
that NS have alwais a IP of the 169.254.0.xxx network.
In this mode, when your PC is configured as DHCP client, if can't connect to
a DHCP server (no DHCP setted on NS), Windows autoassign to PC a IP of
the 169.254.0.xxx network (as you write)... the same network of NS :-D
and you can easly connect to it ;)
My question is: how the NS generate this IP?
TNX!
Its not coming from the NS, its a default Windows IP addy when the computer is set for "Obtain an IP address automatically", but can't connect to a DHCP server, i.e. a router. See http://en.wikipedia.org/wiki/Classful_network for an explanation of 169.254.0.xxx.
Could be several reasons: You're not associating your client with the NS, the NS isn't set to be a DHCP server...
Dear WHT,
I talk about the IP address self-assigned by NS itself..
Try to connect a NS at you PC and start the discovery tool... you can see
that NS have alwais a IP of the 169.254.0.xxx network.
In this mode, when your PC is configured as DHCP client, if can't connect to
a DHCP server (no DHCP setted on NS), Windows autoassign to PC a IP of
the 169.254.0.xxx network (as you write)... the same network of NS :-D
and you can easly connect to it ;)
My question is: how the NS generate this IP?
TNX!
WHT
06-05-2008, 09:53 AM
OK, I understand your question now.
As we no longer have any NS to test, I can only guess at this point. Try this...default the NS and set your computer IP in the same range of the default NS addy and set the NS back to a client. Then try to connect the NS to your AP again.
As we no longer have any NS to test, I can only guess at this point. Try this...default the NS and set your computer IP in the same range of the default NS addy and set the NS back to a client. Then try to connect the NS to your AP again.
skyhook
06-05-2008, 09:59 AM
OK, I understand your question now.
As we no longer have any NS to test, I can only guess at this point. Try this...default the NS and set your computer IP in the same range of the default NS addy and set the NS back to a client. Then try to connect the NS to your AP again.
Dear WHT,
I don't have problem to connect to NS... ;)
I m interest to know the algoritm of IP generation.
TNX
As we no longer have any NS to test, I can only guess at this point. Try this...default the NS and set your computer IP in the same range of the default NS addy and set the NS back to a client. Then try to connect the NS to your AP again.
Dear WHT,
I don't have problem to connect to NS... ;)
I m interest to know the algoritm of IP generation.
TNX
UBNT-keba
06-05-2008, 10:41 PM
Hi,
Auto IP question was already asked somewhere in the forum but for people who did not found that answer I could repeat that again:
Auto IP starts with 169.254.X.Y.
There X and Y are last 2 digits from device MAC address.
Sample:
MAC: 00:15:6D:A3:04:FB
Auto IP: 169.254.4.251
Auto IP question was already asked somewhere in the forum but for people who did not found that answer I could repeat that again:
Auto IP starts with 169.254.X.Y.
There X and Y are last 2 digits from device MAC address.
Sample:
MAC: 00:15:6D:A3:04:FB
Auto IP: 169.254.4.251
skyhook
06-05-2008, 10:51 PM
Hi,
Auto IP question was already asked somewhere in the forum but for people who did not found that answer I could repeat that again:
Auto IP starts with 169.254.X.Y.
There X and Y are last 2 digits from device MAC address.
Sample:
MAC: 00:15:6D:A3:04:FB
Auto IP: 169.254.4.251
Tnx, Keba.
I suggest UBNT to make a FAQ and promote your wiki http://wiki.ubnt.com/wiki/index.php/AirOS ;)
Auto IP question was already asked somewhere in the forum but for people who did not found that answer I could repeat that again:
Auto IP starts with 169.254.X.Y.
There X and Y are last 2 digits from device MAC address.
Sample:
MAC: 00:15:6D:A3:04:FB
Auto IP: 169.254.4.251
Tnx, Keba.
I suggest UBNT to make a FAQ and promote your wiki http://wiki.ubnt.com/wiki/index.php/AirOS ;)
UBNT-keba
06-05-2008, 10:56 PM
We are working on wiki and we are near to provide something useful.
drwho17
07-15-2009, 05:10 PM
I can see the IP's fine on the discovery tool for clients that authenticate with PPP, however I can't connect to them on this address when PPP is enabled. The units with static IP's are accessable on their static ip, or the fallback ip, is this intentional, or just something that is broken.
Jason O
07-17-2009, 10:49 PM
I can see the IP's fine on the discovery tool for clients that authenticate with PPP, however I can't connect to them on this address when PPP is enabled. The units with static IP's are accessable on their static ip, or the fallback ip, is this intentional, or just something that is broken.
Are the PPP and Static IP's on Different IP rage or subnet?
Are the PPP and Static IP's on Different IP rage or subnet?
drwho17
08-17-2009, 04:03 PM
I can see the IP's fine on the discovery tool for clients that authenticate with PPP, however I can't connect to them on this address when PPP is enabled. The units with static IP's are accessable on their static ip, or the fallback ip, is this intentional, or just something that is broken.
Are the PPP and Static IP's on Different IP rage or subnet?
Yes indeed. The extra IP's are on a subnet only reachable via the bridge, I use a 10.130.x.x/255.255.0.0 scheme. PPPoE obtains a realworld IP. I want to be able to reach them when the PPPoE session isn't up.
Are the PPP and Static IP's on Different IP rage or subnet?
Yes indeed. The extra IP's are on a subnet only reachable via the bridge, I use a 10.130.x.x/255.255.0.0 scheme. PPPoE obtains a realworld IP. I want to be able to reach them when the PPPoE session isn't up.
Languages translations made by vBET Translator 3.5.4