On Fri, 4 May 2001, Ted Gervais wrote:
> On Friday 04 May 2001 11:43 am, you wrote:
>
> > Well, you may be able to get by with adding another route. Boot up
> > using the 142.176.139.107 IP, and try running:
> > route add -net 44.0.0.0 netmask 255.0.0.0 gw 44.135.34.201 eth0
>
> OK. I did as you said and here is what I see/saw:
>
> [root@mach3 /root]# route add -net 44.0.0.0 netmask 255.0.0.0 gw
> 44.135.34.201 eth0
> SIOCADDRT: Network is unreachable
>
> So I thought -- need to add a route first.....
>
> [root@mach3 /root]# route add 44.135.34.201 eth0
> [root@mach3 /root]# route add -net 44.0.0.0 netmask 255.0.0.0 gw
> 44.135.34.201 eth0
>
>
> It took! So then I ran a ping -
>
> [root@mach3 /root]# ping ve7tsi
> PING ve7tsi.ampr.org (44.135.163.21) from 142.176.139.108 : 56(84) bytes of
> data.
>
> Notice that it found it (resolved it) but couldn't reach it..
>
> --- ve7tsi.ampr.org ping statistics ---
> 9 packets transmitted, 0 packets received, 100% packet loss
>
>
>
> Just wondering something - you wouldn't have any ampr.org addresses set up.
> You try pinging that ve7tsi or ve4umr. You system should be able to resolve
> them but let me know if you reach them? I bet you do..
>
>
I don't have an ampr.org address. Pinging them from infinity-ltd.com
doesn't produce a return, but that doesn't say anything. I know a lot
of systems that I can reach that I can not ping. A lot of systems have
disabled the ping responce. What may also be happening is that
everything not comming form a ampr.org address is blocked by a firewall.
If so, you will have to add the virtual interface.
Mikkel
--
Do not meddle in the affairs of dragons,
for you are crunchy and taste good with ketchup.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
