The information you report indicates that the change you made did not take
effect. Specificially, you say you changed:
>eth0_MASKLEN=24
But ip's output still reports:
> inet 66.51.222.67/32 scope global eth0
^^
Aside from that, your report is too terse to suggest what specific error in
your setup is causing this problem to persist.
At 05:26 AM 4/21/02 +0000, Blue Shadow wrote:
>
>
>>Ok. The 255.255.255.0 is another, older style of subnet mask. It is
>> >EXACTLY
>>equivalent to a /24 subnet mask. So whoever at the ISP told you to >try /32
>>(as you reported in an earlier message) didn't know his own ISP's >setup.
>>Pfui!
>
>>Try using a /24 netmask and see if that gives you connectivity. If not,
>>report the new symptoms and we'll see what we can do.
>
>
>Ok,I shanged the mask length to 24
>
>eth0_MASKLEN=24
>
>however, the ping still fails the same way.
>
>and I think the outputs bellow are the same as before.
>
>
>Is there anyway to know if it took effect.
>
>Do I need to re-start it.
>
>
>ip addr show
>
>1: lo: <LOOPBACK,UP> mtu 3924 qdisc noqueue
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 brd 127.255.255.255 scope global lo
>2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
> link/ether 00:e0:7d:c1:83:5c brd ff:ff:ff:ff:ff:ff
> inet 66.51.222.67/32 scope global eth0
>3: eth1: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
> link/ether 00:e0:7d:c1:83:73 brd ff:ff:ff:ff:ff:ff
> inet 192.168.1.254/24 brd 192.168.1.255 scope global eth1
>
>
>Ip route show
>
>192.168.1.0/24 dev eth1 proto kernel scope link src 192.168.1.254
--
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
