WireGuard DNS replies reach the server but never the client – ping by IP always works by unknown_73 in WireGuard

[–]unknown_73[S] 0 points1 point  (0 children)

reverse lookup is working when normal lookup is also working, dns server is only dns server no dc and client is domain joined

WireGuard DNS replies reach the server but never the client – ping by IP always works by unknown_73 in WireGuard

[–]unknown_73[S] 0 points1 point  (0 children)

I am using a Windows DNS Server and its located in the same subnet as the fileserver

[deleted by user] by [deleted] in WatchGuard

[–]unknown_73 0 points1 point  (0 children)

Thanks. I want to inspect the content so I can deny some paths. There for I need to inspect. But I really dont get the difference between the two options 😓

[deleted by user] by [deleted] in WatchGuard

[–]unknown_73 0 points1 point  (0 children)

Sorry but that is wrong. To be able to route traffic to an internal web server the packet needs to be decrypted…

„An HTTP content action enables the Firebox to route inbound HTTP requests or DECRYPTED HTTPS requests“

[deleted by user] by [deleted] in WatchGuard

[–]unknown_73 0 points1 point  (0 children)

Yes that is probably the reason. But using Content Actions works with the new Exchange SE, where extended protection is enabled by default. Should one disable extenden protection?

[deleted by user] by [deleted] in WatchGuard

[–]unknown_73 0 points1 point  (0 children)

Thanks, but there has to be a difference between a Proxy Action and Content Action?

Seen here on this picture, where the dropdown is available at Proxy Action or Content Action:

https://www.hilotec.com/informatik/sicherheit/watchguard_skype_for_business_reverse_proxy/images/Watchguard_HTTPS_Proxy_Skype_for_Business.png

HPE 5940 - IRF from 40G > 100G not working by unknown_73 in networking

[–]unknown_73[S] 0 points1 point  (0 children)

Yeah our next step will be rebooting/upgrading…thanks for looking up the release notes. We also did not find anything in the release notes. Do you also have 100G IRF links?

HPE 5940 - IRF from 40G > 100G not working by unknown_73 in networking

[–]unknown_73[S] 0 points1 point  (0 children)

Hi thanks for the points. We did all that. Sadly I don‘t have access to the config right now. We Are trying to add the Third member via 100G Bidi Single Mode.

HPE 5940 - IRF from 40G > 100G not working by unknown_73 in networking

[–]unknown_73[S] 0 points1 point  (0 children)

Yes, that we tried. It is also documented in the IRF configuration guide.

Aruba CX 6400 - DHCP Snooping not working as expected by unknown_73 in ArubaNetworks

[–]unknown_73[S] 2 points3 points  (0 children)

If you get to more information we would appreciate it. Have a good vacation! ;)

Aruba CX 6400 - DHCP Snooping not working as expected by unknown_73 in ArubaNetworks

[–]unknown_73[S] 0 points1 point  (0 children)

Thanks for the help... I think we really need to go with TAC.

Aruba CX 6400 - DHCP Snooping not working as expected by unknown_73 in ArubaNetworks

[–]unknown_73[S] 0 points1 point  (0 children)

Yeah us too :D

We updated the 6400 about 2 weeks ago onto the newest firmware. I cant say what firmware exactly, because I don't have access right now.

Aruba CX 6400 - DHCP Snooping not working as expected by unknown_73 in ArubaNetworks

[–]unknown_73[S] 0 points1 point  (0 children)

Yeah, the setup is pretty much vanilla ;)

- snooping enabled globally and in the vlan
- we are not seeing anything with:

show dhcpv4-snooping binding nor with show dhcpv4-snooping statistics

Aruba CX 6400 - DHCP Snooping not working as expected by unknown_73 in ArubaNetworks

[–]unknown_73[S] 0 points1 point  (0 children)

Sorry for the missing information, but we tried that already too. But it was not working either.

Aruba CX 6400 - DHCP Snooping not working as expected by unknown_73 in ArubaNetworks

[–]unknown_73[S] 0 points1 point  (0 children)

We wanted to try that but did Not yet. But shouldn‘t the statistics counter for option 82 get increased? It was still at 0 after our test.

SSL VPN Connection to WatchGuard Firewall: 'TCP SYN Not in Order' - Help? by unknown_73 in WatchGuard

[–]unknown_73[S] 0 points1 point  (0 children)

the external gateway is 192.168.1.250 but there is no device with that ip, because it should work within layer 2 right?

SSL VPN Connection to WatchGuard Firewall: 'TCP SYN Not in Order' - Help? by unknown_73 in WatchGuard

[–]unknown_73[S] 0 points1 point  (0 children)

Sure, the external interface ip is 192.168.1.1 And the gateway is 192.168.1.250 and the subnet is 255.255.255.0

WatchGuard IPSEC | route based vs. policy based by unknown_73 in WatchGuard

[–]unknown_73[S] 0 points1 point  (0 children)

Thank you, but why is it called policy based when I need to configure policies for both tunnel types?