[an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive]
 
[an error occurred while processing this directive] [an error occurred while processing this directive]
Skåne Sjælland Linux User Group - http://www.sslug.dk Home   Subscribe   Mail Archive   Forum   Calendar   Search
MhonArc Date: [Date Prev] [Date Index] [Date Next]   Thread: [Date Prev] [Thread Index] [Date Next]   MhonArc
 

Er denne 'netstat -r' ok?

Tue, Jan 25, 2000 at 07:39:54PM +0100, skrev Frank Damgaard:
> Jeg har f.eks. :
> 
> 195.249.8.18    0.0.0.0         255.255.255.255 UH    0      0        0 ppp0
> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
> 0.0.0.0         0.0.0.0         0.0.0.0         U     0      0        0 ppp0

Jeg vil gerne lige spørge herinde, om min 'netstat -r' ser forskriftsmæssig ud?

forbindelsen nede:
sslug@sslug:/home/kim > netstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
dialdr.isdal.ho *               255.255.255.255 UH        0 0          0 sl0
ns.isdal.home   *               255.255.255.255 UH        0 0          0 dummy0
192.168.0.0     *               255.255.255.0   U         0 0          0 eth0
192.168.0.0     *               255.255.255.0   U         0 0          0 sl0
loopback        *               255.0.0.0       U         0 0          0 lo
default         *               0.0.0.0         U         0 0          0 sl0

forbindelsen oppe:
sslug@sslug:/home/kim > netstat -r
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
ns.isdal.home   *               255.255.255.255 UH        0 0          0 dummy0
ppp1-8.image.dk *               255.255.255.255 UH        0 0          0 ppp0
192.168.0.0     *               255.255.255.0   U         0 0          0 eth0
212.54.64.0     *               255.255.255.0   U         0 0          0 ppp0
loopback        *               255.0.0.0       U         0 0          0 lo
default         *               0.0.0.0         U         0 0          0 ppp0

På mig virker ovenstående lidt som et overflødighedshorn. Jeg spekulerer på,
om 'dummy0'-interfacet kan undværes i forbindelse med DNS og diald? 

Og jeg har desuden det velkendte problem med 'modprobe: can't find tap0-tap15'.
Jeg har søgt i SSLUG's emailarkiv, men jeg kom ingen vegne, da tråden døde ud?
Har nogen fundet en løsning på 'tapN'-problemet? Der var lidt på www.deja.com,
men jeg kan ikke italiensk, sååå. :-)

-- 
  ,~,        
  (v)       -> SuSE Linux 6.2 <- 
 /( )\            
  W^W    Kim Isdal Knudsen - Vanløse

 
Home   Subscribe   Mail Archive   Index   Calendar   Search

 
 
Questions about the web-pages to <www_admin>. Last modified 2005-08-10, 20:58 CEST [an error occurred while processing this directive]
This page is maintained by [an error occurred while processing this directive]MHonArc [an error occurred while processing this directive] # [an error occurred while processing this directive] *