Meeting topic - security test

[Rocky McGaugh]

root at rocky:/etc/rc.d/rc2.d > ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:DA:7A:34:B6  
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:146268 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17067 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:10 Base address:0xe400 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:964874 errors:0 dropped:0 overruns:0 frame:0
          TX packets:964874 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 

root at rocky:/etc/rc.d/rc2.d > ping -f 192.168.1.100
PING 192.168.1.100 (192.168.1.100): 56 data bytes
--- 192.168.1.100 ping statistics ---
28054 packets transmitted, 28051 packets received, 0% packet loss
round-trip min/avg/max = 0.065/0.255/21.106 ms
root at rocky:/etc/rc.d/rc2.d > ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:DA:7A:34:B6  
          inet addr:192.168.1.100  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:146274 errors:0 dropped:0 overruns:0 frame:0
          TX packets:17067 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:10 Base address:0xe400 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:1021026 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1021026 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 

root at rocky:/etc/rc.d/rc2.d > 

unsure if its something weird i compile into the kernels, but i dont
ever remember linux NOT working this way. granted that it is improper,
but its the way it has always worked for me.

-- 
Rocky McGaugh                                      Atipa Linux Solutions
Product Development                                        www.atipa.com
rocky at smluc.org                                       rmcgaugh at atipa.com

On Thu, 23 Mar 2000, Christofer C. Bell wrote:

> 
> There is no need to drop the lo interface (and, in fact, this will break a
> lot of the machine).  In the Unix world, each network interface has a
> separate IP address assigned to it.  Additionally, you can assign aliases
> that consist of other IP addresses to these same interfaces.
> 

> In order to perform this verification, run nmap or ping or whatever you
> prefer against an IP address that is not bound to lo and occasionally
> enter the command 'ifconfig -a' at your prompt.  Note that the "RX
> packets" and "TX packets" values for the interface to which your the
> 
> --
> Chris