Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Pony1982]

Hi Everyone,
I have an AA Firebrick that bonds two VDSL connections together. This then plugs into a Ubiquiti network that I've been running for years. Recently, AA configured an internet facing IP for me on the Firebrick port that plugs into the Ubiquiti network. The LAN uses DHCP to get an IP address and this gets a correct internet facing IP via DHCP. Unfortunately, the local network cannot get to the internet using this method. I then set the local network up to use a static 10.x.x.x IP from the Firebrick and it can get to the internet when doing this. Any ideas on what the best way to proceed here? The reason I want an Internet facing IP on the LAN is to avoid any sort of NAT issues.

THanks

[Pony1982]

looks like there were some configuration issues on the Firebrick, which AA kindly helped resolved. All good now!!

[Alex Atkin UK]

Honestly I think its rather risky having anything public facing not behind NAT, it adds an incidental level of security on top of the client firewall.

Is there something specific you've had a snag with NAT on?

[j0hn]

The reason I want an Internet facing IP on the LAN is to avoid any sort of NAT issues.

I'm with Alex here.

NAT isn't a bad thing. Personally I think it's madness giving all your internal devices globally routable IP addresses that are publicly accessible from the entire internet.

I understand doing that for individual specific devices that require this but I don't know any reason why this would be desirable for the whole LAN.