Router with no IPv4 address

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}

-1

I have a router that does not have an IPv4 address as seen in the photo

Network output from my computer.

Is there a way to connect to it and fix that? I tried connecting using the IPv6 name http://[fe80::ee08:6bff:fedd:63d] but id did not work.

It has openWRT on it if that helps.

Thank you.

asked Feb 7 at 16:09

unknown1

2

No, that image describes a host that configured itself with a link-local (APIPA) address. It did not get that address from any type of DHCP. That network block (169.254.0.0/16) is not allowed to be routed, and addresses in that block are not allowed to be statically or manually assigned, nor is that range allowed to be subnetted.

– Ron Maupin
Feb 7 at 16:17

2

Possible duplicate of I am using Windows 7 and I get a 169.254.x.x ip address

– Moab
Feb 7 at 16:19

1

Also, your IPv6 address is a link-local address, which is not allowed to be routed, and you did not include the required Zone ID. Every IPv6 interface uses the same network, so you must use a Zone ID to distinguish the specific network.

– Ron Maupin
Feb 7 at 16:21

1

Possible duplicate of Network devices getting an IP address in the 169.254.x.x range?

– Pimp Juice IT
Feb 7 at 17:05

add a comment |

-1

I have a router that does not have an IPv4 address as seen in the photo

Network output from my computer.

Is there a way to connect to it and fix that? I tried connecting using the IPv6 name http://[fe80::ee08:6bff:fedd:63d] but id did not work.

It has openWRT on it if that helps.

Thank you.

asked Feb 7 at 16:09

unknown1

2

No, that image describes a host that configured itself with a link-local (APIPA) address. It did not get that address from any type of DHCP. That network block (169.254.0.0/16) is not allowed to be routed, and addresses in that block are not allowed to be statically or manually assigned, nor is that range allowed to be subnetted.

– Ron Maupin
Feb 7 at 16:17

2

Possible duplicate of I am using Windows 7 and I get a 169.254.x.x ip address

– Moab
Feb 7 at 16:19

1

Also, your IPv6 address is a link-local address, which is not allowed to be routed, and you did not include the required Zone ID. Every IPv6 interface uses the same network, so you must use a Zone ID to distinguish the specific network.

– Ron Maupin
Feb 7 at 16:21

1

Possible duplicate of Network devices getting an IP address in the 169.254.x.x range?

– Pimp Juice IT
Feb 7 at 17:05

add a comment |

-1

I have a router that does not have an IPv4 address as seen in the photo

Network output from my computer.

Is there a way to connect to it and fix that? I tried connecting using the IPv6 name http://[fe80::ee08:6bff:fedd:63d] but id did not work.

It has openWRT on it if that helps.

Thank you.

asked Feb 7 at 16:09

unknown1

I have a router that does not have an IPv4 address as seen in the photo

Network output from my computer.

Is there a way to connect to it and fix that? I tried connecting using the IPv6 name http://[fe80::ee08:6bff:fedd:63d] but id did not work.

It has openWRT on it if that helps.

Thank you.

networking wireless-networking router wireless-router ipv6

asked Feb 7 at 16:09

unknown1

asked Feb 7 at 16:09

unknown1

asked Feb 7 at 16:09

unknown1

asked Feb 7 at 16:09

unknown1

asked Feb 7 at 16:09

unknown1

2

No, that image describes a host that configured itself with a link-local (APIPA) address. It did not get that address from any type of DHCP. That network block (169.254.0.0/16) is not allowed to be routed, and addresses in that block are not allowed to be statically or manually assigned, nor is that range allowed to be subnetted.

– Ron Maupin
Feb 7 at 16:17

2

Possible duplicate of I am using Windows 7 and I get a 169.254.x.x ip address

– Moab
Feb 7 at 16:19

1

Also, your IPv6 address is a link-local address, which is not allowed to be routed, and you did not include the required Zone ID. Every IPv6 interface uses the same network, so you must use a Zone ID to distinguish the specific network.

– Ron Maupin
Feb 7 at 16:21

1

Possible duplicate of Network devices getting an IP address in the 169.254.x.x range?

– Pimp Juice IT
Feb 7 at 17:05

add a comment |

2

No, that image describes a host that configured itself with a link-local (APIPA) address. It did not get that address from any type of DHCP. That network block (169.254.0.0/16) is not allowed to be routed, and addresses in that block are not allowed to be statically or manually assigned, nor is that range allowed to be subnetted.

– Ron Maupin
Feb 7 at 16:17

2

Possible duplicate of I am using Windows 7 and I get a 169.254.x.x ip address

– Moab
Feb 7 at 16:19

1

Also, your IPv6 address is a link-local address, which is not allowed to be routed, and you did not include the required Zone ID. Every IPv6 interface uses the same network, so you must use a Zone ID to distinguish the specific network.

– Ron Maupin
Feb 7 at 16:21

1

Possible duplicate of Network devices getting an IP address in the 169.254.x.x range?

– Pimp Juice IT
Feb 7 at 17:05

No, that image describes a host that configured itself with a link-local (APIPA) address. It did not get that address from any type of DHCP. That network block (169.254.0.0/16) is not allowed to be routed, and addresses in that block are not allowed to be statically or manually assigned, nor is that range allowed to be subnetted.

– Ron Maupin
Feb 7 at 16:17

Possible duplicate of I am using Windows 7 and I get a 169.254.x.x ip address

– Moab
Feb 7 at 16:19

Also, your IPv6 address is a link-local address, which is not allowed to be routed, and you did not include the required Zone ID. Every IPv6 interface uses the same network, so you must use a Zone ID to distinguish the specific network.

– Ron Maupin
Feb 7 at 16:21

Possible duplicate of Network devices getting an IP address in the 169.254.x.x range?

– Pimp Juice IT
Feb 7 at 17:05

add a comment |

2 Answers
2

active

oldest

votes

You are not getting a DHCP assigned address from the OpenWrt device.

Try setting a static IP on your wifi connection, the default LAN ip range of a OpenWrt device is 192.168.1.1/24 so you need to set your wifi to:

ip: 192.168.1.10

netmask: 192.168.255.0

gateway: 192.168.1.1

Either you can now login at http://192.168.1.1 (default username is root without password for a fresh installed OpenWrt). Perhaps you need to enable the DHCP server on the LAN network.

If that does not work, try to ping from a MacOS terminal:

$ping 192.168.1.1

If you do not get a ping reply, there is something else wrong with the actual network.

answered Feb 7 at 17:43

LVC

182

add a comment |

It's well known that browsers refuse to accept IPv6 link-local address literals as the host part of a URL. So you need a different address for the router.

Fortunately it appears your network is also configured with an IPv6 unique local address network, fd4f:3537:6693::/48, where your LAN is on fd4f:3537:6693::/64.

This means the router should be avaiable on the subnet router anycast address, which is the zero address of the subnet, i.e. fd4f:3537:6693::.

But not all routers listen to this address, so there is another way to find its other IPv6 addresses, and that is by pinging the all routers multicast address, ff02::2. Open a Terminal.app and run:

ping6 ff02::2%wlan0

(where wlan0 is the interface name of your Wi-Fi interface)

If your router responds to pings, this should return responses from at least two addresses, one of which is in the ULA prefix, and which you can then use in a URL.

Either way, once you have an address, try accessing it in your browser:

http://[fd4f:3537:6693::<whatever>]/

Even this isn't guaranteed to work, because your router might not be serving its built in web server on IPv6. But it's what I would do to try to get back in.

edited Feb 7 at 18:56

answered Feb 7 at 18:21

Michael Hampton

11.1k33469

add a comment |

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1403193%2frouter-with-no-ipv4-address%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

You are not getting a DHCP assigned address from the OpenWrt device.

Try setting a static IP on your wifi connection, the default LAN ip range of a OpenWrt device is 192.168.1.1/24 so you need to set your wifi to:

ip: 192.168.1.10

netmask: 192.168.255.0

gateway: 192.168.1.1

Either you can now login at http://192.168.1.1 (default username is root without password for a fresh installed OpenWrt). Perhaps you need to enable the DHCP server on the LAN network.

If that does not work, try to ping from a MacOS terminal:

$ping 192.168.1.1

If you do not get a ping reply, there is something else wrong with the actual network.

answered Feb 7 at 17:43

LVC

182

add a comment |

You are not getting a DHCP assigned address from the OpenWrt device.

Try setting a static IP on your wifi connection, the default LAN ip range of a OpenWrt device is 192.168.1.1/24 so you need to set your wifi to:

ip: 192.168.1.10

netmask: 192.168.255.0

gateway: 192.168.1.1

Either you can now login at http://192.168.1.1 (default username is root without password for a fresh installed OpenWrt). Perhaps you need to enable the DHCP server on the LAN network.

If that does not work, try to ping from a MacOS terminal:

$ping 192.168.1.1

If you do not get a ping reply, there is something else wrong with the actual network.

answered Feb 7 at 17:43

LVC

182

add a comment |

You are not getting a DHCP assigned address from the OpenWrt device.

Try setting a static IP on your wifi connection, the default LAN ip range of a OpenWrt device is 192.168.1.1/24 so you need to set your wifi to:

ip: 192.168.1.10

netmask: 192.168.255.0

gateway: 192.168.1.1

Either you can now login at http://192.168.1.1 (default username is root without password for a fresh installed OpenWrt). Perhaps you need to enable the DHCP server on the LAN network.

If that does not work, try to ping from a MacOS terminal:

$ping 192.168.1.1

If you do not get a ping reply, there is something else wrong with the actual network.

answered Feb 7 at 17:43

LVC

182

You are not getting a DHCP assigned address from the OpenWrt device.

Try setting a static IP on your wifi connection, the default LAN ip range of a OpenWrt device is 192.168.1.1/24 so you need to set your wifi to:

ip: 192.168.1.10

netmask: 192.168.255.0

gateway: 192.168.1.1

Either you can now login at http://192.168.1.1 (default username is root without password for a fresh installed OpenWrt). Perhaps you need to enable the DHCP server on the LAN network.

If that does not work, try to ping from a MacOS terminal:

$ping 192.168.1.1

If you do not get a ping reply, there is something else wrong with the actual network.

answered Feb 7 at 17:43

LVC

182

answered Feb 7 at 17:43

LVC

182

answered Feb 7 at 17:43

LVC

182

answered Feb 7 at 17:43

LVC

182

add a comment |

It's well known that browsers refuse to accept IPv6 link-local address literals as the host part of a URL. So you need a different address for the router.

Fortunately it appears your network is also configured with an IPv6 unique local address network, fd4f:3537:6693::/48, where your LAN is on fd4f:3537:6693::/64.

This means the router should be avaiable on the subnet router anycast address, which is the zero address of the subnet, i.e. fd4f:3537:6693::.

But not all routers listen to this address, so there is another way to find its other IPv6 addresses, and that is by pinging the all routers multicast address, ff02::2. Open a Terminal.app and run:

ping6 ff02::2%wlan0

(where wlan0 is the interface name of your Wi-Fi interface)

If your router responds to pings, this should return responses from at least two addresses, one of which is in the ULA prefix, and which you can then use in a URL.

Either way, once you have an address, try accessing it in your browser:

http://[fd4f:3537:6693::<whatever>]/

Even this isn't guaranteed to work, because your router might not be serving its built in web server on IPv6. But it's what I would do to try to get back in.

edited Feb 7 at 18:56

answered Feb 7 at 18:21

Michael Hampton

11.1k33469

add a comment |

It's well known that browsers refuse to accept IPv6 link-local address literals as the host part of a URL. So you need a different address for the router.

Fortunately it appears your network is also configured with an IPv6 unique local address network, fd4f:3537:6693::/48, where your LAN is on fd4f:3537:6693::/64.

This means the router should be avaiable on the subnet router anycast address, which is the zero address of the subnet, i.e. fd4f:3537:6693::.

But not all routers listen to this address, so there is another way to find its other IPv6 addresses, and that is by pinging the all routers multicast address, ff02::2. Open a Terminal.app and run:

ping6 ff02::2%wlan0

(where wlan0 is the interface name of your Wi-Fi interface)

If your router responds to pings, this should return responses from at least two addresses, one of which is in the ULA prefix, and which you can then use in a URL.

Either way, once you have an address, try accessing it in your browser:

http://[fd4f:3537:6693::<whatever>]/

Even this isn't guaranteed to work, because your router might not be serving its built in web server on IPv6. But it's what I would do to try to get back in.

edited Feb 7 at 18:56

answered Feb 7 at 18:21

Michael Hampton

11.1k33469

add a comment |

It's well known that browsers refuse to accept IPv6 link-local address literals as the host part of a URL. So you need a different address for the router.

Fortunately it appears your network is also configured with an IPv6 unique local address network, fd4f:3537:6693::/48, where your LAN is on fd4f:3537:6693::/64.

This means the router should be avaiable on the subnet router anycast address, which is the zero address of the subnet, i.e. fd4f:3537:6693::.

But not all routers listen to this address, so there is another way to find its other IPv6 addresses, and that is by pinging the all routers multicast address, ff02::2. Open a Terminal.app and run:

ping6 ff02::2%wlan0

(where wlan0 is the interface name of your Wi-Fi interface)

If your router responds to pings, this should return responses from at least two addresses, one of which is in the ULA prefix, and which you can then use in a URL.

Either way, once you have an address, try accessing it in your browser:

http://[fd4f:3537:6693::<whatever>]/

Even this isn't guaranteed to work, because your router might not be serving its built in web server on IPv6. But it's what I would do to try to get back in.

edited Feb 7 at 18:56

answered Feb 7 at 18:21

Michael Hampton

11.1k33469

It's well known that browsers refuse to accept IPv6 link-local address literals as the host part of a URL. So you need a different address for the router.

Fortunately it appears your network is also configured with an IPv6 unique local address network, fd4f:3537:6693::/48, where your LAN is on fd4f:3537:6693::/64.

This means the router should be avaiable on the subnet router anycast address, which is the zero address of the subnet, i.e. fd4f:3537:6693::.

But not all routers listen to this address, so there is another way to find its other IPv6 addresses, and that is by pinging the all routers multicast address, ff02::2. Open a Terminal.app and run:

ping6 ff02::2%wlan0

(where wlan0 is the interface name of your Wi-Fi interface)

If your router responds to pings, this should return responses from at least two addresses, one of which is in the ULA prefix, and which you can then use in a URL.

Either way, once you have an address, try accessing it in your browser:

http://[fd4f:3537:6693::<whatever>]/

Even this isn't guaranteed to work, because your router might not be serving its built in web server on IPv6. But it's what I would do to try to get back in.

edited Feb 7 at 18:56

answered Feb 7 at 18:21

Michael Hampton

11.1k33469

edited Feb 7 at 18:56

answered Feb 7 at 18:21

Michael Hampton

11.1k33469

answered Feb 7 at 18:21

Michael Hampton

11.1k33469

answered Feb 7 at 18:21

Michael Hampton

11.1k33469

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Super User!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

搜尋此網誌

Csdrhrt