Access Modem GUI Behind Firewall

[johnpoz]

@Gblenn said in Access Modem GUI Behind Firewall:

and I find it strange that it wouldn't "just work".

because as you can see by his lan rules - he is policy routing.. Which has been brought up multiple times already.. He needs a rule to allows the normal routing to work..

Here

https://docs.netgate.com/pfsense/en/latest/multiwan/policy-route.html#bypassing-policy-routing

[Globaltrader312]

@johnpoz I apologise for asking this question.

I have looked at the instructions, unfortunately I do not understand one point in the instructions it says to create an alias for RFC1918 and in the picture it can also be seen that RFC1918 was set as destination.

but when i want to create a new rule, the destination RF1918 is displayed as invalid IP so i don't quite understand how i can set this i can only set an IP subnet e.g. 192.168.0.0/16

[johnpoz]

@Globaltrader312 Huh.. You don't need to create such an alias you could just put in 192.168.0.0/16 cidr in the rule.. Or just your 192.168.5.1/32 or 192.168.5.0/24

But creating an alias for all rfc1918 space would be done in the alias section

Here would be an example of using it in rule - this isn't a rule like you need but just an example of using the alias in a firewall rule

[Globaltrader312]

@johnpoz

I have now created the rule via the Policy Based Rules and traffic is also flowing see screen shot and packet capture

but the GUI of the Vigor is still not accessible.

can it be that I still have to enter the changed ports from vigor in the firewall 8080 and 444 which I changed because of an advice from another user a few posts before.

[johnpoz]

@Globaltrader312 well if your device is not listening on port 80 any more, and you try and talk to port 80 which is what your sniff shows - then yeah its not going to answer. Either change its port back to 80, or talk to it on port whatever you changed it too

http://192.168.5.1:port

But your sniff shows 192.168.5.0 -- that is not really a valid IP address using a /24 mask.. I thought you set your pfsense interface to be .2 and or .3 why would it be using .0??

[Globaltrader312]

@johnpoz

so i have now set the ports back to 80 and 443 it still does not work unfortunately

the 192.168.5.0/24 is because when I set Vigor to /32 under interfcaes no packets get through.

if i set it to /24 then packets go through at 192.168.5 but it says 192.168.5.0 / 24.

[johnpoz]

@Globaltrader312 no idea what your talking about?

Your address there is 192.168.5.3, why would pfsense change the address it sends from to .0??? That doesn't happen

The mask of /24 means this

The Wire or network is .0, the host address on this /24 network is .1 to .254, the broadcast address is .255

What you show there is correct, the interface address would be .3, there is no scenario that I can think of where pfsense would jsut on its own change that to .0 as its source address when natting to that interface.

Please post your outbound nat rule..

Why do you show .3 and .4?

Did you create a vip or something? And your natting to the vip address? VIP is not something you need to create.. VIP was my attempt at showing you how it can be done when your actual interface has a actual public IP like mine does... You are using PPPoE so you don't need to create a vip

[Globaltrader312]

@johnpoz

[johnpoz]

@Globaltrader312 just show your outbound nat tab.. Not the specific details of 1 of them - for a we know this one isn't even being used because you have some other one above it.

Example here is mine

But this isn't right

Click the dropdown and pick the Vigor address, which would be 192.168.5.3 from your screenshot

[Globaltrader312]

@johnpoz

thank you guys for your help it works after i entered the alias rfc1918 as soure and selected 192.168.5.0/24 as destination and Vigor aadress as translation address.

[johnpoz]

@Globaltrader312 so if you would of followed the instructions, you would of been done in like 2 seconds.

And actually understood that you were policy routing.. How did you think something would work when your shoving it out some gateway that is not connected to what you want to talk too?

[JonathanLee]

Great job, and you also learned port forwarding, ACL ordering, alias creation and much more. I love this forum you can learn so
much. Now you just need a OpenVPN configured with a NAS server for private cloud use