Multiple IPs
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 64.22.103.10, and the new one is 64.22.103.92.
Thanks for your help!
11 Replies
I think I know what to do now.
Thanks.
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=64.22.103.92
NETMASK=255.255.255.0
Any suggestions?
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:64.22.103.10 Bcast:64.22.103.255 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:64.22.103.92 Bcast:64.22.103.255 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.
Thanks,
James
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.
Thanks again.
> RTNETLINK answers: Invalid argument
Meh.
"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.