Public IP assigned through router DHCP - Head Banging
 

Hi,

I've just bought a replacement ML350 G6 server. The 6 HD' (RAID5) I've simply transplanted into the replacement server in the order I removed them from the old one. Booted up, loaded grub followed by OpenSuse. Everything is working fine.. apart from trying to set my static IP.

The server is set to DHCP and if I leave it to its own devices it's assigned an internal IP from the router eg. 192.168.0.112. Internet works!

To assign my public static IP as I've done countless times before:

Log into router.
Select MacAddr for router and set to assign public static IP.
Restart server (keeping it in DHCP mode).

On reboot server now has public IP, job done.

However when I do this via the router the server isnt assigned the public IP. Instead it has no IP at all and the network is unreachable. I cant understand this as I've done it this way for years.

I know the router is working properly as its assigning public static IP's to other devices on the network eg. camera.

Could it be a conflict on the server? I am getting the log "IPv4: Martian source 255.255.255.255 from 192.168.0.1, on dev eth0".

Can anyone shed any light, this is usually just a 5 minute job, but instead its being a nightmare.

Thanks

I assume you've checked everywhere on the server where the MAC address is used and ensured that the new hardware MAC address is being used instead of the one that the disks were transplanted from?

Yes, I've check the MAC address for the adapter I'm using and this relates to the one selected on the router.
Could there be an old MAC address or card config saved within the filesystem thats causing issues?

Yes, especially if the original server had multiple NICs. That's why I suggested checking everywhere on the server :) Ensure that the hardware address showing under ifconfig or ip link show (or the OpenSuse equivalents) show the MAC that the router is expecting to reply to.

Router is using the correct MAC address.

If I remove the static IP from the server via the router control panel, and then restart the interface with 'ifdown eth0' followed by 'ifup eth0' I get assigned a random internal IP. Connection functions.

If I set the router to assign the public static IP to the server using DHCP, then restart the interface, when I run 'ifup eth0' I get the following error:

/sbin/ifup: line 232: 12273 Segmentation Fault $wicked_client ${opt_debug} ifup "$INTERFACE"

The interface still enables, but I get no IP and the connection is useless. It is important to note I only get this segmentation fault on the server when I set the router to assign a public static IP.

Confused.......

Well I'm out of ideas :( If it was my box I'd just be setting the static IPs on the server to get around the problem and then forget about it ;)

That's what I've done with partial success. Server is now connected to the net, but.....

Problem I've got when I set the static IP this way is that the router doesn't recognise the server as been connected to it. Thus, I cant forward any ports to my server.

It's a nightmare. Usually its a 5 minute job, done, forgotten about!

Your router doesn't let you forward ports to arbitrary IPs on the subnet? I've never seen that behavior before, and it's a really stupid design if that's the case. Maybe there's another menu option for port forwarding where you can just type in an IP without having to pick one from a list?