Re: IP-Aliasing
On 7/11/05, Frank Hempel <red_socks@gmx.de> wrote:
> Hello,
>
> I don't get IP-Aliasing to work. The machine has got one interface
> (eth0) working correctly with ip=192.168.1.1
> Issuing the commands
>
> ifconfig eth0:1 192.168.1.100
> route add -host 192.168.1.100 dev eth0:1
>
> brings the interface eth0:1 up, but I can't ping it from the same
> machine or other ones.
>
>
> An odd thing I noticed is the ifconfig output:
>
> eth0 Protokoll:Ethernet Hardware Adresse 00:0B:6A:78:EB:25
> inet Adresse:192.168.1.66 Bcast:192.168.1.255
> Maske:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:27843 errors:0 dropped:0 overruns:0 frame:0
> TX packets:28857 errors:0 dropped:0 overruns:0 carrier:0
> Kollisionen:0 Sendewarteschlangenlänge:1000
> RX bytes:2944191 (2.8 MiB) TX bytes:17241905 (16.4 MiB)
> Interrupt:11 Basisadresse:0xd400
>
> eth0:1 Protokoll:Ethernet Hardware Adresse 00:0B:6A:78:EB:25
> inet Adresse:192.168.1.100 Bcast:192.168.1.255
> Maske:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> Interrupt:11 Basisadresse:0xd400
>
> lo Protokoll:Lokale Schleife
> inet Adresse:127.0.0.1 Maske:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:339 errors:0 dropped:0 overruns:0 frame:0
> TX packets:339 errors:0 dropped:0 overruns:0 carrier:0
> Kollisionen:0 Sendewarteschlangenlänge:0
> RX bytes:144621 (141.2 KiB) TX bytes:144621 (141.2 KiB)
>
>
> It doesnt show the RX/TX etc. lines for the eth0:1.
>
> Could someone give me a hint on how to do it right?
>
> Thanks, Frank.
Seems like you've done it properly. What's the output of 'route -n'
and are you running any type of firewall who's rules need to be reset
after you added the alias?
As for the RX/TX, linux only tracks that on a physical interface, so
eth0 is combined totals for any IPs aliased. If you want to actually
track per-ip you'll probably need to investigate some iptables rules,
and some other monitoring software like mrtg.
--
~ Darryl ~ smartssa@gmail.com
http://smartssa.com / http://darrylclarke.com
Reply to: