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..
>
> If I haven't forgotten anything, or goofed up the format, that may get
> you access to the ampr.org network. What it will not do is let the
> ampr.org contact you on 44.135.34.210. You need the virtual interface
> for that.
>
> Mikkel
--
Ted Gervais
Coldbrook, Nova Scotia Canada.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
