This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Cookie Policy. Click Preferences to customize your cookie settings.
Ok, understand it now - just bit new to VM solution in AWS - last good few years was working with multiple physical Palo boxes.
Will check with Radius guys to change IP to .15 there and hopefully it will work with Radius request coming from eth 1/2 with x.x.209.15 IP
Thanks again for your help - much appreciated.
... View more
I have changed in Service Route config IPV4 and Destination IP to x.x.209.15 with src int 1/2.
I think it did some "trick" as now when applying "test"command on cli I dont have any errors - its just hanging with out any output.
Also I can see traffic logs(attached) with reason for session end "n/a"
So hopefully changing IP on PF RAdious to .209.15 (as its setup for .14) will do the trick.
Or should we look int changing mgmt IP in DHCP to .15 as well?
... View more
The IP in first section is wrong - someone put x.x.208.14 whereas this FW is x.x.209.14 mgmt IP.
Question is if I should use mgmt IP here or mgmt interface with .209.15?
In service route should I put source interface with x.x.209.15 ? Radius server expecting traffic from mgmt IP - x.x.209.14(or its irrelevant)
... View more
I've just added screenshots with current setup (2 newest). Unfortunately even with bringing it to default , when trying to reconfigure - it's bringing up wrong 208.14 IP. If I put mgmt interface IP - it will accept as its autofilling but whatever I type in box- its not accepting it - just coming with wrong .208.14 or other preconfigured staff
... View more
yeah, I think these double IP management setup causing issue...
Its a VM Palo in AWS so not sure whether I should change mgmt to .15 - same as interface or change IP on interface to .14 - mgmt IP address (both screen attached) - and if reboot of FW or instance required.
... View more