Hi Folks,
I posted this a week or so ago, and although I got a couple of suggestions,
nothing seemed to help. I've looked around the net, and not seen anything
else like it anywhere.
I have a pretty vanilla slink install, with the update for netbase
recommended for 2.2 kernels. I'm using a 2.2.12 kernal at the moment, but I
have also tried 2.0.38, and get exactly the same problem. Same thing if I
just use the standard slink netbase, with either 2.2.12 or 2.0.38.
Has *anyone* managed to get IP aliasing working on Slink? Surely someone
has.
The problem is, if I install an IP alias on this system, I am able to ping
the aliased IP (eth0:0) on the same box, but not from any other box on the
network. I am able to ping, and connect to, the primary (eth0) IP with no
problems from any machine. The NIC is an Intel 10/100, running on a 10M hub.
<snip>
callisto:~# ifconfig eth0:0 203.20.80.111 up
callisto:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:A0:C9:98:E2:91
inet addr:203.20.80.42 Bcast:203.20.80.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4259 errors:0 dropped:0 overruns:0 frame:0
TX packets:3939 errors:0 dropped:0 overruns:0 carrier:0
collisions:16 txqueuelen:100
Interrupt:10 Base address:0xe000
eth0:0 Link encap:Ethernet HWaddr 00:A0:C9:98:E2:91
inet addr:203.20.80.111 Bcast:203.20.80.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:10 Base address:0xe000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:201 errors:0 dropped:0 overruns:0 frame:0
TX packets:201 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
callisto:~# ping 203.20.80.111
PING 203.20.80.111 (203.20.80.111): 56 data bytes
64 bytes from 203.20.80.111: icmp_seq=0 ttl=255 time=0.9 ms
64 bytes from 203.20.80.111: icmp_seq=1 ttl=255 time=0.6 ms
--- 203.20.80.111 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.6/0.7/0.9 ms
<snip>
As you can see from the above, I can add the alias, it shows up, and I can
ping it on the same machine.
When I move onto another machine from the network, and I try and ping the
alias I have created, it doesn't respond (the other machine is running
RedHat 5.2, updated to kernel 2.2.10):
<snip>
[EMAIL PROTECTED] damon]# ping 203.20.80.111
PING 203.20.80.111 (203.20.80.111): 56 data bytes
--- 203.20.80.111 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
[EMAIL PROTECTED] damon]#
<snip>
But when I ping the eth0 IP from the same remote machine, it works fine:
<snip>
[EMAIL PROTECTED] damon]# ping 203.20.80.42
PING 203.20.80.42 (203.20.80.42): 56 data bytes
64 bytes from 203.20.80.42: icmp_seq=0 ttl=255 time=2.4 ms
64 bytes from 203.20.80.42: icmp_seq=1 ttl=255 time=1.8 ms
64 bytes from 203.20.80.42: icmp_seq=2 ttl=255 time=1.0 ms
64 bytes from 203.20.80.42: icmp_seq=3 ttl=255 time=1.0 ms
--- 203.20.80.42 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 1.0/1.5/2.4 ms
[EMAIL PROTECTED] damon]#
<snip>
I have tried everything I can think of: recopiling kernels, using different
kernels, using different netbase packages, removing spoofprotect from
/etc/init.d/netbase.
I am competely out of options, and about to start damaging some hardware! I
hope I have posed enough information here for someone to help me diagnose
the problem. If there is anything more I can post, let me know and I will.
Someone please save me!
damon
--
Damon Muller ([EMAIL PROTECTED])
Systems Administrator
EmpireNET
Melbourne, Australia
