I added a second IP, and configured my Linode as described here:
When I ping locally (from the Linode itself), I get a response from both IPs, but when I do the same remotely (as in from my own PC), the old IP works fine, but the new one gives me "Request timed out".
When I run ifconfig, it lists the old IP as eth0, and the new one as eth0:1.
My old ip is 220.127.116.11, and the new one is 18.104.22.168.
Thanks for your help!
I don't think I have a firewall configured:
# iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination
This is what I've configured:
# cat ifcfg-eth0:0 DEVICE=eth0:0 BOOTPROTO=none ONBOOT=yes IPADDR=22.214.171.124 NETMASK=255.255.255.0
I've not seen 0:0 used before (but it may be valid). I use 0:1
Here's the output from ifconfig:
# ifconfig eth0 Link encap:Ethernet HWaddr FE:FD:40:16:67:0A inet addr:126.96.36.199 Bcast:188.8.131.52 Mask:255.255.255.0 inet6 addr: fe80::fcfd:40ff:fe16:670a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2696115 errors:0 dropped:0 overruns:0 frame:0 TX packets:2742679 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:531381736 (506.7 MiB) TX bytes:1622071325 (1.5 GiB) Interrupt:5 eth0:1 Link encap:Ethernet HWaddr FE:FD:40:16:67:0A inet addr:184.108.40.206 Bcast:220.127.116.11 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:5 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:64841 errors:0 dropped:0 overruns:0 frame:0 TX packets:64841 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:7901846 (7.5 MiB) TX bytes:7901846 (7.5 MiB)
I'd appreciate any suggestions as to how I can diagnose the problem.
It won't work until you do. (The IP can't be routed to your UML instance on the fly while it's running)
It might be a good idea to add that to the Wiki entry.
> RTNETLINK answers: Invalid argument
"Multiple IPs" a note about rebooting
I added this note under the Debian / Ubuntu section; if this applies to other distros as well, somebody please promote that warning upwards in the article.