Dahua NVR4232-16P-4KS2 - Network Config Issues & MTU Question

monoxyde

n3wb
Joined
Jan 13, 2019
Messages
11
Reaction score
4
Location
Southeast, USA
So I recently purchased a NVR4232 and I'm having some issues.

1) It doesn't seem to like pulling DHCP from my router (I've statically assigned the lease to 172.25.5.2).

When I set the unit to DHCP, it goes to 0.0.0.0 and I can reboot it and it never seems to pull, however if I statically set it it works just fine.

2) I tried to statically set the IPv6 address, and I cannot ping the unit.... period, it will not respond and it never comes online. Has anyone configured with IPv6?

3) If I set the MTU lower, does it actually modify the MTU value of the packets sent to my pfSense appliance?

Now, for backstory, would love to hear some thoughts.

I run pfSense and a managed Cisco switch on my network. The uplink port to pfSense is trunked for VLANS 1,5,6.

The NVR is plugged into a port on the Cisco that is only tagged with VLAN5.

VLAN5 is has limited internet access, the only access to the internet is port 53 and 123. (DNS and NTP, so the device can query the IP of the NTP server(s) in use and set the appropriate time.)

I've got a OpenVPN server running on pfSense to connect into my network. The only problem is that it doesn't work over cellular to stream videos with my mobile carrier (T-Mobile). T-Mobile uses an 464XLAT which means the maximum MTU is 1444, everything is on a IPv6 and and IPv4 addresses are proxied. So, that being said, VPN access doesn't work over cellular for me. I've tried it on a Verizon phone and have no issues.

If I can lower the MTU value, and it actually changes the max transmission unit I should be fine.

That being said, I know you can scan all IPv4 in a matter of hours if you have a fast enough internet connection. I'm kind of shooting for security by obscurity here, but it would take someone a long time to find me 1234:5678:91011:A:B:C:D:E/64 and they'd really have to be targetting me.

I've tried to setup native IPv6 on OpenVPN, but apparently there is some issues with assigning OpenVPN a /64 subnet of it's own at the moment. When I do that, I can ping the server 1234:5678:91011:A::/64 and even 1234:5678:81011:A::1/64 but any IP that it assigns out to the client doesn't appear to have routes.

Unit Information (if that matters), I flashed the firmware from dahuasecurity.com so it should be legit.
System Version: 3.216.0000000.0 Build Date: 2018-06-05
 

c hris527

Known around here
Joined
Oct 12, 2015
Messages
1,793
Reaction score
2,090
Location
NY
IPV6 on those NVR's is static only. IPV4 will do static and dynamic. I think that might go for quite a bit of the dahua cams also.
 

monoxyde

n3wb
Joined
Jan 13, 2019
Messages
11
Reaction score
4
Location
Southeast, USA
IPV6 on those NVR's is static only. IPV4 will do static and dynamic. I think that might go for quite a bit of the dahua cams also.
Does anyone know a compatible Android IPv6 client? All Apple App's must support IPv6 since June 2016. It works fine on my iPhone, but using an Android Pixel, it appears the gDMSS app does not support IPv6.

Firewall wise, I've opened up (in case anyone needs similar info in the future):
17.0.0.0/8 (Apple)
2620:149::/32 (Apple)
2620:0:1B00::/32 (Apple)
2607:FB90::/32 (T-Mobile)
2607:FC20::/32 (T-Mobile/Metro)
2607:7700::/32 (T-Mobile)
2620:F5:C000::/48 (T-Mobile/Level-3)
And my home /48

I know this is a couple trillion trillion trillion IP's, and pretty wide open by IPv4 standards... But, hopefully bots aren't connecting via cellular tether to attempt to scan IPv6 subnets.
 
Top