Hi me again. Just in case this is relevant, my ISP has me on an IPoE/CG-NAT system.
Thanks to you guys over the last month I got through the basic configuration of my router and have moved onto the next stage, setting up a handful of devices. The other day I hooked up a NAS and set it a static IPv4.
It worked that day and I got through some of the NAS's basic configuration accessing it from my laptop. But today I tried accessing it again and no dice. I assume I screwed something up in the configuration, but I'm not sure where to start. I tried both the static IP and tower.local, the DNS that Unraid sets up for you upon installation--it also worked the other day.
Here's a list of what I did and remember doing:
I confirmed both through OpenWrt and the NAS device's command line that the static IP I set the other day is still its IP address.
The NAS doesn't have wifi yet, so I connected the ethernet cable in all sorts of ways just to make sure this wasn't just an ethernet port problem.
I noticed tonight that under Network > Diagnostics, IPv4 Ping doesn't work while IPv6 does:
PING openwrt.org (64.226.122.113): 56 data bytes
--- openwrt.org ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
PING openwrt.org (2a03:b0c0:3:d0::1a51:c001): 56 data bytes
64 bytes from 2a03:b0c0:3:d0::1a51:c001: seq=0 ttl=54 time=226.305 ms
64 bytes from 2a03:b0c0:3:d0::1a51:c001: seq=1 ttl=54 time=222.381 ms
64 bytes from 2a03:b0c0:3:d0::1a51:c001: seq=2 ttl=54 time=222.091 ms
64 bytes from 2a03:b0c0:3:d0::1a51:c001: seq=3 ttl=54 time=225.956 ms
64 bytes from 2a03:b0c0:3:d0::1a51:c001: seq=4 ttl=54 time=222.159 ms
--- openwrt.org ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 222.091/223.778/226.305 ms
I'm happy to grab more code if it would help with troubleshooting, but I really don't know where to start Thanks again to anyone who takes the time to help me out.
Please test some domain other than openwrt.org, OpenWrt's servers have been under constant attacks from ai companies and even more shady shady sources for the last few months and might not respond (because they're down, very slow or need to employ more extensive filtering). Meaning that any ping responses from *.openwrt.org need to be taken with a huge grain of salt, as the issues might be server-side and not with your client.
If I understand the issue correctly, you cannot reach your NAS from your computer -- is that correct?
Assuming that the two devices are on the same subnet, the router itself is not involved when devices are connecting to each other on the same L2 network. This would most likely point to an issue with the configuration of the NAS, not the router.
Just to be sure, though, we can take a look at your router's configuration:
Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, VPN keys, MAC addresses and any public IP addresses you may have:
Ah, thanks for the insight. I tried Google and Amazon Japan but got the same result. Would that be an effect of CG-NAT, or is it more likely I configured something wrong?
My reply will be strictly about pinging IPv4 addresses (directly or indirectly via their fully qualified domain name) from either your router or a client behind your router (and not about anything regarding your NAS issues, as that's a whole other can of worms). cgNAT will not impede outgoing ping/ ping6 calls, nor the incoming responses, you can expect that to work regardless of cgNAT (or almost all other IPv4 transition mechanisms), because that's the most basic thing that needs to be done to keep access to IPv4-only servers working (and not inciting a riot from the ISP's paying customers).
But we are seeing ai companies and related enterprises going totally rampant in recent months (in particular, but already for the last 2-4 years), effectively attacking and DDoS'ing servers to a scale that can even bring down big projects and quite a few companies (at least temporarily), this makes the internet as a whole less stable and reliable than it had been before (bots have been a problem for the last two decades already, but it has really gone off the scales 'recently', since ai became the new gold rush). And as an opensource project with limited financial resources and few dedicated servers, without enterprise level protection schemes (proxies) in place, *.openwrt.org (like any opensource project) is particularly vulnerable to this.
The IPv6 stuff I'm sure was me over the past several weeks. I'm not at home now so I can't confirm directly, but I think I have a box checked somewhere (Interface menu?) regarding masquerading. There's a little sign next to the box, but I didn't note in my documentation whether that was checked by default or if I did it myself. As a result, I've kept it checked. I really don't understand the implications, so if you know of the best practices in a general home network remote-access use-case I would appreciate it.
But would this have something to do with connecting to this NAS machine? As far as I know it only has an IPv4 address--when I boot the machine up it says IPv6 is "Not set".
Also, the NAS machine is running Unraid, which boots from a USB. If I disconnect that the machine would boot into Windows, which I might be able to use to fix whatever I've mucked up.
Again, sorry for the amateur questions, and thank you very much for your time.
In that case, you may want to reset and try using the defaults since it looks like your config wouldn't take long to rebuild. (obviously make a backup first).
But the lan interface is still a big question mark:
And, of course, you didn't specifically confirm/refute this:
Ah sorry--That's correct, I was able to reach the NAS by entering its IP into a browser window on the day of initial installation, but yesterday--the second time I tried to access it--I was unable to.
I confirmed via command line on the NAS machine itself that its IPv4 was 192.168.29.15, and I set that IP address as static in OpenWrt using the NAS's MAC address. But even following that step, I was unable to access the device via my laptop's browser.
And as for the subnet mask, I don't clearly remember setting that (for the NAS) on either machine. Is that something I would be able to do now?
^Edit: Actually, I think I do remember doing that. Unraid requires it when you set the IP. I would have set it as usual, 255.255.255.0.
Let's make sure that we've got a precise description of what you've done...
Did you manually set the IP address on the NAS (as in a true static IP address, set in the network config of the NAS itself), or is the NAS set to DHCP client?
How is the NAS connected to the network? Is it directly plugged into eth1, or is there a downstream switch?
How is the laptop connected to the network? Ethernet or wifi?
What is the IP address of the laptop (and the subnet mask)?
What is the redacted line from the lan network interface (as I said previously, it's not necessary to redact that info).
I see that you have a DHCP reservation here:
I recommend removing the leasetime line.
There have been some recent debates about if the reservation needs to be within the DHCP pool or if it is okay for it to be outside the pool... currently, yours is outside the DHCP range. I'll try to run a quick experiment to see if this could be causing any of your issues.
I believe I manually set the IP address via the NAS's settings menu. I've attached a screenshot from a YouTube tutorial for context, but that's not my machine's configuration.
The NAS is connected to a managed switch, which is itself connected to my OpenWrt One. The OW1 is connected to an ONU, typical in Japan.
The laptop is typically connected to wifi, but yesterday I was connecting via ethernet, first via the switch and then directly to the NAS (which has two ethernet ports, one of which maintained its connection to the switch at all times).
The laptop gets assigned an IP from the router on a 12-hour lease so I assume it will be different when I get home tonight, but the subnet mask ought to be 255.255.255.0. At any rate, the address will be 192.168.29.x.
And here is the code I erroneously redacted:
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ip6assign '60'
list ipaddr '192.168.29.1/24'
The unreacted lan interface looks fine. the CIDR notation (/24) specifies the subnet size, so the netmask is not required.
Your NAS config is theoretically fine if it's a variant of what is shown in the screen grab, but it's hard to know for sure.
All that said, there is nothing that the OpenWrt router can do to affect connectivity between your devices. Something is wrong. but I don't think it can be your router because of the fact that the laptop <-> NAS connections should be at L2.
With that in mind, you could use an unmanaged switch if you have one lying around, or just connect the NAS directly to the OpenWrt router and then connect your laptop via wifi... if they still can't connect to each other, the problem must be on the NAS (configuration or otherwise).
Thank you so much for troubleshooting this with me. I'll do as you suggested, and if all else fails it seems like I should be able to un-set the IP from the NAS's command line.
Thanks again to anyone who takes the time to help me out.
sign next to the box, but I didn't note in my documentation whether that was checked by default or if I did it myself. As a result, I've kept it checked. I really don't understand the implications, so if you know of the best practices in a general home network remote-access use-case I would appreciate it.