Re: ip alias interfaces don't respond
On 10/27/05, Scott Edwards <[EMAIL PROTECTED]> wrote: > On 10/27/05, Scott Edwards <[EMAIL PROTECTED]> wrote: > > I'm trying to determine why I can ssh into > > this box on the first ip address, but cannot on any of its other ips. > > There's 9 ip addresses in all. This machine has worked fine for some > > time... > > To restate, a machine I own has nine IP Addresses assigned to it. > Access to the first IP Address works ok. Services are not responding > on any other address. I added a few accounting only rules to iptables > to see if there are any counted. tcpdump displays traffic directed to > the apparently unresponsive addresses, and iptables hasn't incremented > any rules that should match. Works the same way with the old or new > kernels. It appears the upstream router was a tad bit foobar on my port configuration. tcpdump -n udp and not ether host was showing identical traffic, and caught my attention. I used arpspoof to reannounce my ip addresses, and apparently the upstream router got a [EMAIL PROTECTED](%$ clue. All traffic and iptables counters started to operate normally after this. Thanks anyway folks. Hopefully you'll not have to encounter this. If this does fix the problem I've discussed, keep the subject intact and reply (hopefully in a manner the message thread will stay intact on gmail ...) Thanks again!
Re: ip alias interfaces don't respond
On 10/27/05, Scott Edwards <[EMAIL PROTECTED]> wrote: > I'm trying to determine why I can ssh into > this box on the first ip address, but cannot on any of its other ips. > There's 9 ip addresses in all. This machine has worked fine for some > time... To restate, a machine I own has nine IP Addresses assigned to it. Access to the first IP Address works ok. Services are not responding on any other address. I added a few accounting only rules to iptables to see if there are any counted. tcpdump displays traffic directed to the apparently unresponsive addresses, and iptables hasn't incremented any rules that should match. Works the same way with the old or new kernels. I'm out of ideas, any suggestions? Thanks.
ip alias interfaces don't respond
I'm greatly scratching my head trying to determine why I can ssh into this box on the first ip address, but cannot on any of its other ips. There's 9 ip addresses in all. This machine has worked fine for some time - but that's not to say I didn't do something correct... I'm pretty sure it was correct to begin with, but there is certainly an issue now. A few weeks ago the machine was rebooted gracefully w/o incident. It was up for at least 30 days prior to my attempt to start using the 2.4.31 kernel. I have made an attempt to regress to the most previous 2.4.26-grsec kernel with no apparent improvement. During troubleshooting, I've temporarily discontinued using iptables on the source and destination machines. I've rebooted after making network changes (a specific routing issue lingers in the back of my mind for changes like this). I even attempted to run tcpdump to inspect what's occurring while using ssh or ping (three systems in all). Sometimes I see nothing, a few times I've seen the ping requests or ssh tcp syn packets, but no reply. I've spent most of my day on this issue. I look forward to any suggestions. Feel free to start over with my troubleshooting in case I missed something along the way... Thanks, Scott.
Re: sarge ip alias?
On Thu, Jul 28, 2005 at 11:46:34AM -0500, Matthew Lenz wrote: >so what's the proper debian way of adding an ip alias to an interface? > >say i've got 192.168.0.2 on eth0 and I want 192.168.0.3 on eth0:0 (or 1 >whatever debian uses for the first ip alias on an interface) > put this in /etc/network/interfaces iface eth0 inet static address 192.168.0.2 netmask 255.255.255.0 network 192.168.0.0 broadcast 192.168.0.255 gateway 192.168.0.1 up ip addr add dev $IFACE 192.168.0.3/24 broadcast 192.168.1.255 label eth0:1 down ip addr flush dev $IFACE -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: sarge ip alias?
On 7/28/05, Matthew Lenz <[EMAIL PROTECTED]> wrote: > so what's the proper debian way of adding an ip alias to an interface? Add it to /etc/network/interfaces > say i've got 192.168.0.2 on eth0 and I want 192.168.0.3 on eth0:0 (or 1 > whatever debian uses for the first ip alias on an interface) Not Nebian. Linux. Regards, Nelson.- -- Homepage : http://geocities.com/arhuaco The first principle is that you must not fool yourself and you are the easiest person to fool. -- Richard Feynman.
sarge ip alias?
so what's the proper debian way of adding an ip alias to an interface? say i've got 192.168.0.2 on eth0 and I want 192.168.0.3 on eth0:0 (or 1 whatever debian uses for the first ip alias on an interface) -Matt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ip alias
On Oct 13 at 18:48, Alan Chandler spoke: > Here is my /etc/network/interfaces with a number of aliased ip addresses on > eth1. > > auto eth0 eth1 lo eth1:0 eth1:1 eth1:2 I have now ### etherconf DEBCONF AREA. DO NOT EDIT THIS AREA OR INSERT TEXT BEFORE IT. auto lo iface lo inet loopback iface eth0 inet dhcp hostname snoopy iface eth0:0 inet static address 1.1.1.1 netmask 255.255.255.252 ### END OF DEBCONF AREA. PLACE YOUR EDITS BELOW; THEY WILL BE PRESERVED. I have to issue `ifup eth0:0' manually. If I put eth0:0 into the auto line. I get problems when booting: Setting up IP spoofing protection: rp_filter. Configuring network interfaces: eth0:0 ERROR while getting interface flags: No such device SIOCSIFADDR: No such device Should I use a specific configuration tool? The interface is on a PCMCIA card. -Hanspeter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ip alias
Is there any way to assign the alias'ed eth1 interfaces via DHCP? How about locking an IP to each that is assigned via DHCP (I guess this isnt possible since pre-allocated DHCP addresses are done via MAC addy) Alan Chandler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Sunday 13 October 2002 5:23 pm, Hanspeter Roth wrote: > > >Hello, > > > >how can one create an ip alias on an interface that has already > >another ip address? > > > >-Hanspeter > > > Here is my /etc/network/interfaces with a number of aliased ip > addresses on > eth1. > > auto eth0 eth1 lo eth1:0 eth1:1 eth1:2 > > iface lo inet loopback > > iface eth0 inet dhcp > > iface eth1 inet static > address 10.0.10.100 > netmask 255.255.255.0 > network 10.0.10.0 > broadcast 10.0.10.255 > > iface eth1:0 inet static > address 10.0.10.101 > netmask 255.255.255.0 > network 10.0.10.0 > broadcast 10.0.10.255 > > iface eth1:1 inet static > address 10.0.10.102 > netmask 255.255.255.0 > network 10.0.10.0 > broadcast 10.0.10.255 > > > iface eth1:2 inet static > address 10.0.10.103 > netmask 255.255.255.0 > network 10.0.10.0 > broadcast 10.0.10.255 > > - -- > Alan Chandler > [EMAIL PROTECTED] > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.2.0 (GNU/Linux) > > iD8DBQE9qbILuFHxcV2FFoIRAtGEAJwOk/8Hkv1idOq+CWYqmlbRUv2rmgCgsNL5 > BYagR8PdCVU54NM/UTma94Q= > =+CER > -END PGP SIGNATURE- > > -- = http://www.sun.com/service/sunps/jdc/javacenter.pdf= =www.sun.com | www.javasoft.com | http://wwws.sun.com/sunone = = = = "Noone wants advice - only corroboration" - John Steinbeck = ==== = "Pawns can become Royalty in Life or in Chess" = = "Life, the only game where Royalty can be a pawn,= =and not even know it" = = "Chess, the only game where pawns really are pawns" = -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ip alias
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sunday 13 October 2002 5:23 pm, Hanspeter Roth wrote: > Hello, > > how can one create an ip alias on an interface that has already > another ip address? > > -Hanspeter Here is my /etc/network/interfaces with a number of aliased ip addresses on eth1. auto eth0 eth1 lo eth1:0 eth1:1 eth1:2 iface lo inet loopback iface eth0 inet dhcp iface eth1 inet static address 10.0.10.100 netmask 255.255.255.0 network 10.0.10.0 broadcast 10.0.10.255 iface eth1:0 inet static address 10.0.10.101 netmask 255.255.255.0 network 10.0.10.0 broadcast 10.0.10.255 iface eth1:1 inet static address 10.0.10.102 netmask 255.255.255.0 network 10.0.10.0 broadcast 10.0.10.255 iface eth1:2 inet static address 10.0.10.103 netmask 255.255.255.0 network 10.0.10.0 broadcast 10.0.10.255 - -- Alan Chandler [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE9qbILuFHxcV2FFoIRAtGEAJwOk/8Hkv1idOq+CWYqmlbRUv2rmgCgsNL5 BYagR8PdCVU54NM/UTma94Q= =+CER -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: ip alias
On Sun, 13 Oct 2002, Hanspeter Roth wrote: > how can one create an ip alias on an interface that has already > another ip address? There's a kernel option in recent kernels to enable IP aliasing. Once you've done that, IIRC you can set the network settings with ifconfig for eth0:0, eth0:1, etc. - I think you have to do the eth0 before eth0:0 or whatever. Then you do the obvious stuff with route as if they were just different interfaces, if necessary. -- Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ip alias
Hello, how can one create an ip alias on an interface that has already another ip address? -Hanspeter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: IP Alias
* Kalle Olavi Niemitalo <[EMAIL PROTECTED]> [2001.10.19 09:12:47+0300]: > > eth0, IP Address A - can ping from my computer and from other computers > > eth0:0, IP Address B - can ping ONLY from my computer but not from = > > others. It is listed in ifconfig > > Are they in the same subnet? most likely not, then the other machines, or at least the default router needs forward and reverse route entries! -- martin; (greetings from the heart of the sun.) \ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED] first snow, then silence. this thousand dollar screen dies so beautifully. pgpJLTweQ4kVG.pgp Description: PGP signature
Re: IP Alias
"Chad Morgan" <[EMAIL PROTECTED]> writes: > eth0, IP Address A - can ping from my computer and from other computers > eth0:0, IP Address B - can ping ONLY from my computer but not from = > others. It is listed in ifconfig Are they in the same subnet? If you assign IP address A to eth0 and B to eth0:0, which one works then? Are you using a packet filter?
Re: IP Alias
* Chad Morgan ([EMAIL PROTECTED]) [011002 16:29]: > > Hello, > > I set up an IP Alias on my system but I'm unable to access the aliased IP > address from other computers. > > I have: > eth0, IP Address A - can ping from my computer and from other computers > eth0:0, IP Address B - can ping ONLY from my computer but not from others. It > is listed in ifconfig > > When I reverse the addresses > eth0 = IP Address B and > eth0:0 = IP Address A > the same thing occurs. > > I've followed the HOWTO and haven't been able to find any thing that I'm > missing. Any ideas on something else I should be looking at. what are the addresses and netmasks you're using? good times, -- Vineet http://www.anti-dmca.org Unauthorized use of this .sig may constitute violation of US law. echo Qba\'g gernq ba zr\! |tr 'a-zA-Z' 'n-za-mN-ZA-M' pgpRwSdVWZ3vd.pgp Description: PGP signature
IP Alias
Hello, I set up an IP Alias on my system but I'm unable to access the aliased IP address from other computers. I have: eth0, IP Address A - can ping from my computer and from other computers eth0:0, IP Address B - can ping ONLY from my computer but not from others. It is listed in ifconfig When I reverse the addresses eth0 = IP Address B and eth0:0 = IP Address A the same thing occurs. I've followed the HOWTO and haven't been able to find any thing that I'm missing. Any ideas on something else I should be looking at. Chad Morgan
Re: IP ALIAS
Dave Sherohman wrote: > On Mon, Jun 25, 2001 at 08:05:10PM -0300, Juan wrote: > > How can I configure an IP ALIAS ? > > 1) Build a kernel with IP aliasing support > 2) Assign an address to eth0:0, eth0:1, etc. > And, IIRC, in the 2.4.x kernel tree aliasing is default (or better, you will not find an alias options =) Andrea
Re: IP ALIAS
On Mon, Jun 25, 2001 at 08:05:10PM -0300, Juan wrote: > How can I configure an IP ALIAS ? 1) Build a kernel with IP aliasing support 2) Assign an address to eth0:0, eth0:1, etc. Easy as that. -- That's not gibberish... It's Linux. - Byers, The Lone Gunmen Geek Code 3.12: GCS d? s+: a C++ UL$ P++>+++ L+++> E- W--(++) N+ o+ !K w--- O M- V? PS+ PE Y+ PGP t 5++ X+ R++ tv+ b+ DI D G e* h r y+
IP ALIAS
Hi, How can I configure an IP ALIAS ? TIA, Juan José Velázquez Garcia Web Development www.htmlspider.com.br
Re: IP Alias
Michael Goodman was said to been seen saying: > How do you assigned an IP Alias to a nic card at boot? I tried adding it to > /etc/network/interfaces but it doesn't work. Thanks. > Have you tried the following? It works fine on my gateway machine that has eth0 and eth0:1 - eth0:4 configured in this manner: auto eth0:1 iface eth0:1 inet static address 192.168.0.1 netmask 255.255.255.0 Just duplicate the manner above and leave your eth0 interface config as you have it as the aliases will grab your broadcast and gateway from it. Respectfully, Jeremy T. Bouse -- ,-, |Jeremy T. Bouse, CCNA - UnderGrid Network Services, LLC - www.UnderGrid.net | |Public PGP/GPG fingerprint and location in headers of message| | If received unsigned (without requesting as such) DO NOT trust it! | | [EMAIL PROTECTED] - NIC Whois: JB5713 - [EMAIL PROTECTED] | `-' pgpMABrJOZvwK.pgp Description: PGP signature
IP Alias
How do you assigned an IP Alias to a nic card at boot? I tried adding it to /etc/network/interfaces but it doesn't work. Thanks.
dhcpcd doesn't like IP-alias?
I'm having a lot of trouble getting dhcpcd to work on a virtual NIC, and I'm having trouble with IP-alias in general. It works fine if I set it up manually: /sbin/ifconfig eth0:1 192.168.1.5 up However, getting this to work by editing the "interfaces" config file in /etc/network fails to bring it up, both in dhcp and static, configured as below for dhcp: iface eth0:1 inet dhcp hostname (hostname) I did a sloppy hack to make the thing work in /etc/rcS.d/S55bootmisc.sh with the command I had been using manually. I know that's the wrong way to do it, but I don't know another way. So I have eth0:1 after bootup now, even if it is rude and crude. Next, although the interface exists dhcpcd refuses to use it and in fact it takes down the whole darn network when trying to use eth0:1. If I tell it to use eth0 it works fine, but it kills eth0:1. I need dhcpcd to use eth0:1 since port forwarding won't work on a virtual NIC. Does dhcpcd not work on one either? What am I screwing up :-) No error messages are produced on the screen. In case I'm going about the _whole_ thing all wrong, here's what I'm trying to do: Debian box is a firewall providing internet access to three other PCs all on a 192.168.1.x network. I want the "real" NIC to use 192.168.1.1, and the virtual NIC to have its IP assigned by dhcpcd. The cable modem is not connected directly to the box, it is connected to the uplink port on the hub. The computer is running Potato and kernel 2.2.17 compiled from the source provided w/the distro. This was a lot easier for me with a 56K modem, to tell the truth! Also if it's not too much trouble, what are some good FMs for learning how to properly start up programs (say [EMAIL PROTECTED]) on bootup, and some information on how I should set up routing for my network? I read about runlevels in Debian, but I'm not clear on how scripts not installed by packages should be configured/started. TIA Andrew W. [EMAIL PROTECTED]
Re: SOLVED - Re: IP Alias and Slink - ARGH!
On Sat, Nov 13, 1999 at 01:14:07AM +1100, Damon Muller wrote > Hi folks, > > Thanks to those who responded promptly to my pathetic cries for help with an > IP aliasing problem. I have finally found the culprit. > > The ipmasq package obviously sets up some ipchains rules that prevent any > connections to IP aliases. I'd installed the package (not sure why), and of > course it runs the ipmasq script in /etc/rcS.d, every time the system boots. > I'm not an ipchains expert, so I couldn't work out where these DENY rules > were coming from. > > Anyway, I used update-rc.d to remove the links, rebooted (anyone know of a > way to clear all the ipchains rules without rebooting?), and now it all > seems to work (fingers crossed!). > FYI, ipmasq *should* deal correctly with aliases & multiple interfaces, but it must be run *after* they are configured. That said, the IPmasq package has had some problems in the past in this area; I'm not sure where it stands right now. John P. -- [EMAIL PROTECTED] [EMAIL PROTECTED] "Oh - I - you know - my job is to fear everything." - Bill Gates in Denmark
Re: IP Alias and Slink - ARGH!
Damon Muller wrote: > > 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. Did you set up a route for the new ip? for example: /sbin/ifconfig eth0:0 192.168.1.31 up netmask 255.255.255.0 /sbin/route add -host 192.168.1.31 dev eth0:0 jpb -- Joe Block <[EMAIL PROTECTED]> CREOL System Administrator Social graces are the packet headers of everyday life.
Re: IP Alias and Slink - ARGH!
On Fri, 12 Nov 1999, Damon Muller wrote: dm-deb >Has *anyone* managed to get IP aliasing working on Slink? Surely someone dm-deb >has. i have, no problem on both 2.0 and 2.2 kernels, make sure the route is added for the aliased ips. I got about 50 aliased ips on this machine for web hosting. dm-deb >network. I am able to ping, and connect to, the primary (eth0) IP with no dm-deb >problems from any machine. The NIC is an Intel 10/100, running on a 10M hub. dm-deb >3 packets transmitted, 0 packets received, 100% packet loss check firewall rules too .. dm-deb >I have tried everything I can think of: recopiling kernels, using different dm-deb >kernels, using different netbase packages, removing spoofprotect from dm-deb >/etc/init.d/netbase. show us output of route -n for me .. this is just 1 of my aliases: eth0 Link encap:Ethernet HWaddr 00:40:05:30:FF:19 inet addr:208.222.179.31 Bcast:208.222.179.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:58529532 errors:0 dropped:0 overruns:0 frame:0 TX packets:57602701 errors:6 dropped:0 overruns:2 carrier:4 Collisions:0 Interrupt:12 Base address:0xd000 eth0:1Link encap:Ethernet HWaddr 00:40:05:30:FF:19 inet addr:208.222.179.33 Bcast:208.222.179.255 Mask:255.255.255.0 UP BROADCAST RUNNING MTU:1500 Metric:1 RX packets:1 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 Collisions:0 and some of my routes .. Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 208.222.179.162 0.0.0.0 255.255.255.255 UH0 00 eth0:48 208.222.179.163 0.0.0.0 255.255.255.255 UH0 00 eth0:49 208.222.179.33 0.0.0.0 255.255.255.255 UH0 00 eth0:1 208.222.179.35 0.0.0.0 255.255.255.255 UH0 00 eth0:42 208.222.179.38 0.0.0.0 255.255.255.255 UH0 00 eth0:57 208.222.179.44 0.0.0.0 255.255.255.255 UH0 00 eth0:39 one more thing to try bind apache to that other IP and try to access it from www nate [mailto:[EMAIL PROTECTED] ]-- Vice President Network Operations http://www.firetrail.com/ Firetrail Internet Services Limited http://www.aphroland.org/ Everett, WA 425-348-7336http://www.linuxpowered.net/ Powered By:http://comedy.aphroland.org/ Debian 2.1 Linux 2.0.36 SMPhttp://yahoo.aphroland.org/ -[mailto:[EMAIL PROTECTED] ]-- 7:36am up 84 days, 19:07, 1 user, load average: 2.67, 2.10, 1.87
RE: SOLVED - Re: IP Alias and Slink - ARGH!
On 12-Nov-1999 Damon Muller wrote: > Hi folks, > > Thanks to those who responded promptly to my pathetic cries for help with an > IP aliasing problem. I have finally found the culprit. > > The ipmasq package obviously sets up some ipchains rules that prevent any > connections to IP aliases. I'd installed the package (not sure why), and of > course it runs the ipmasq script in /etc/rcS.d, every time the system boots. > I'm not an ipchains expert, so I couldn't work out where these DENY rules > were coming from. > > Anyway, I used update-rc.d to remove the links, rebooted (anyone know of a > way to clear all the ipchains rules without rebooting?), and now it all > seems to work (fingers crossed!). ipchains -Fwill do it. -- Andrew
SOLVED - Re: IP Alias and Slink - ARGH!
Hi folks, Thanks to those who responded promptly to my pathetic cries for help with an IP aliasing problem. I have finally found the culprit. The ipmasq package obviously sets up some ipchains rules that prevent any connections to IP aliases. I'd installed the package (not sure why), and of course it runs the ipmasq script in /etc/rcS.d, every time the system boots. I'm not an ipchains expert, so I couldn't work out where these DENY rules were coming from. Anyway, I used update-rc.d to remove the links, rebooted (anyone know of a way to clear all the ipchains rules without rebooting?), and now it all seems to work (fingers crossed!). Thanks again, damon -- Damon Muller ([EMAIL PROTECTED]) Systems Administrator EmpireNET Melbourne, Australia
IP Alias and Slink - ARGH!
Look your routing table. # man route -- __ Felipe Alvarez Harnecker. QlSoftware. Tel. 09.874.60.17 e-mail: [EMAIL PROTECTED] Potenciado por Ql/Linux http://www.qlsoft.cl __
IP Alias and Slink - ARGH!
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. 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:0Link 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 loLink 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 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): [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]# But when I ping the eth0 IP from the same remote machine, it works fine: [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]# 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
