Server Edition WAN port IP wont work with default

[critchey]

I have a customer with a brand new Server Edition installation. The server was ignited, licenses ordered, and everything seemed great. We went to finish the install today after getting the licenses and it is giving an error on the WAN port "No IP on interface" in the Linux screen from vmware and I can't ping 192.168.43.1. If I change the WAN port to anything but 43.1 it takes without issue but it refuses to take the default IP. After playing with it for a few hours I decided to cut my loses and reinstall Server Edition from scratch and it does the same frigging thing...

I have a computer on 192.168.43.5 and can not ping anything on 43.1. Their SIP provider "device" is 192.168.43.2 so everything is hinged on them connecting to 192.168.43.1 but for the life of me I can't figure out why the Server Edition refuses to take that IP. At first I thought it was related to their IPO being converted to an expansion had that as the WAN port IP as well so I changed the IP, removed the link, removed it from the solution, but same thing. I reignited the server after this so I am not sure this is the cause but it is the only thing that makes any sense...

Any and all help would be grealy appreciated. Server Edition is running R11 SP2 (had some issues with FP4 staying away from it for now).

The truth is just an excuse for lack of imagination.

 

[derfloh]

Did you configure the IP through the CLI tool
system config network
?

Need some help with IP Office?

https://www.fwilke.com/home

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/

 

[snowman50]

Why don’t you change the LAN1 port 192.168.43.1 instead,
I don’t think the server actually has a wan port for Ipo.
I always thought the wan port was only on the IP500 CHASSIS because you could configure both of them..

 

[critchey]

He configured LAN 192.168.1.222 and WAN 192.168.43.1 and got licensed already so we can't change it without upsetting the licensing but I appreciate the suggestions. The Server Edition we have for testing, with full licensing, has both the LAN and WAN port specified and no issues with this type of configuration. I never dreamed it would not take the default IP like that... seems like I have been having all the luck with weird issues as of late!

The truth is just an excuse for lack of imagination.

 

[critchey]

We configured the IP for the WAN port from the web interface, under system settings, eth1 changed IP. Any IP but the default works. When you do a fresh install it does not come up on 192.168.43.1 it says it has no IP for the WAN port but if you change it to any other IP it works just fine...

The truth is just an excuse for lack of imagination.

 

[IPGuru]

re-licencing through PLDS is no big deal - may be your easiest route


Do things on the cheap & it will cost you dear

 

[critchey]

Ya I get the feeling that is the route we will need to go. I tried R11 FP4 just to test and same behavior. So odd it literally takes any IP, even one on the 43.X subnet, but not the default IP for the WAN port... Also sucks because their provider takes forever to change their device IP but that can hardly be helped at this point.

The truth is just an excuse for lack of imagination.