[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: LAN/NAS problem.



On Thu, Jun 08, 2000 at 12:10:01PM +1000, Marc-Adrian Napoli wrote
> hi all,
> 

Hello, Marc!

> we have an ascend server that serves a dial up customer sitting on 203.28.51.128.
> 
> routing table on the ascend server:
> 
> 203.28.51.128/27   203.28.51.128   wan12    rGT    120   2    6575    5169
> 203.28.51.128/32   203.28.51.128   wan12    rT      60   1    4150    5169
> 
> they are given the 203.28.51.128/27 subnet from radius.
> 
> on the customers end is a linux box acting as a router for their /27 subnet.
> 
> ifconfig on the debian box shows:
> 
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
>           UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
>           RX packets:7607 errors:0 dropped:0 overruns:0
>           TX packets:7607 errors:0 dropped:0 overruns:0
> 
> eth0      Link encap:Ethernet  HWaddr 00:00:E8:47:F3:9C
>           inet addr:203.28.51.128  Bcast:203.28.51.159  Mask:255.255.255.224
                      ^^^^^^^^^^^^^
>           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>           RX packets:85592 errors:0 dropped:23 overruns:0
>           TX packets:6940 errors:0 dropped:0 overruns:0
>           Interrupt:9 Base address:0x240
> 
> ppp0      Link encap:Point-to-Point Protocol
>           inet addr:203.28.51.128  P-t-P:203.63.219.10  Mask:255.255.255.224
                      ^^^^^^^^^^^^^
>           UP POINTOPOINT RUNNING  MTU:1524  Metric:1
>           RX packets:10757 errors:0 dropped:0 overruns:0
>           TX packets:10410 errors:0 dropped:0 overruns:0
> 

[snip]

Using the network address ([203.28.51.128]) as the interface
address isn't a good idea.  It may be treated as special for all
sorts of reasons and you can't rely on it to behave like a
regular host IP, or even for different TCP/IP stacks to deal
with it consistently.

For example on my local LAN, with a network address of
192.168.113.0, all of my Debian boxes (running kernel
2.2.15) respond if I ping 192.168.113.0, but it would be equally
understandable if none of them did (as is the case if I run
# echo 1 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
).  Change the interface address to (say) 203.28.51.129; it may
not fix your problem, but it removes the most obvious reason why
it may not work.


John P.
-- 
huiac@camtech.net.au
john@huiac.apana.org.au
http://www.mdt.net.au/~john Debian Linux admin & support:technical services



Reply to: