If you can ping the addresses from the machine itself, then they
have been successfully added to the interface (eth0). You can
confirm this, of course by listing all of the addresses on eth0:
# ip addr show dev eth0
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:30:1b:af:78:51 brd ff:ff:ff:ff:ff:ff
inet 38.99.214.162/30 brd 38.99.214.163 scope global eth0
inet 38.98.6.230/27 brd 38.98.6.255 scope global eth0:1
inet 38.98.6.235/27 brd 38.98.6.255 scope global secondary eth0:2
inet 38.98.6.240/27 brd 38.98.6.255 scope global secondary eth0:3
inet 38.98.6.245/27 brd 38.98.6.255 scope global secondary eth0:4
inet 38.98.6.250/27 brd 38.98.6.255 scope global secondary eth0:5
inet6 fe80::230:1bff:feaf:7851/64 scope link
valid_lft forever preferred_lft forever
//cool thats what mine looks like there
# ip route show dev eth0
38.98.6.224/27 proto kernel scope link src 38.98.6.230
38.99.214.160/30 proto kernel scope link src 38.98.6.230
default via 38.99.214.161
// mine looks different here
//[root@landuconsulting ~]# ip route show dev eth0
//38.99.214.160/30 proto kernel scope link src 38.99.214.162
//38.98.6.224/27 proto kernel scope link src 38.98.6.230
//169.254.0.0/16 scope link
//default via 38.99.214.161
//should I remove this line "38.99.214.160/30 proto kernel scope link src 38.99.214.162"
//and replace it with this line:"38.99.214.160/30 proto kernel scope link src 38.98.6.230"
Note the following potential pitfall. If you were to remove the IP
address 38.98.6.230 from eth0, all of the other ones would also be
removed [1].
//noted
Is the machine a router? If "landuconsulting" is not a router, then
you do not need (nor want) IP forwarding enabled.
//removed ip_forwarding
So, you are testing to see if you can reach 38.98.214.162 and
38.98.6.230 (and friends) from a remote location? Are you sure the
upstream route exists? Here's how to use tcpdump to test on
landuconsulting:
# tcpdump -nn -i eth0 net 38.98.6.224/27 or arp
Now, generate your inbound traffic to any of your additional
addresses. Watch for ARP requests. Is your machine answering them?
//nope
It is quite possible that your upstream router does not have a route
to 38.98.6.224/27 to your local Ethernet.
//I'm calling them in 30 to verify.
That's something you need
to fix on the upstream router, not on the host you are configuring
with many IP addresses.
Good luck,
-Martin
Thank you Martin.
JD
[0] http://linux-net.osdl.org/index.php/IPv4
[1] http://linux-ip.net/html/tools-ip-address.html#tools-ip-address-del
--
Martin A. Brown
http://linux-ip.net/
_______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
