Gustavo, On Wed, Nov 15, 2006 at 11:14:23PM -0300, Gustavo Rios wrote: >i have followed pppoe(4) instructions on setting it up. It works >perfectly.
as long as it works :) >But, i am very confused with the output for the netstat -rn >command (only relevant part) > >Internet: >Destination Gateway Flags Refs Use Mtu >Interface >default 0.0.0.1 UGS 1 8 - pppoe0 this routing table entry has 0/0 in destination (prints as "default"), and 0.0.0.1/32 as gateway. That is the kinda line you would find on most of the systems. The word "default" netstat prints instead of 0/0 are probably appropriate here, as it really means "any address that didn't match any other destination in my routing table". >0.0.0.1 default UH 1 0 - pppoe0 this routing table entry has 0.0.0.1/32 as destination and 0/0 as gateway >127/8 127.0.0.1 UGRS 0 0 33224 lo0 >127.0.0.1 127.0.0.1 UH 1 0 33224 lo0 >224/4 127.0.0.1 URS 0 0 33224 lo0 > >For ifconfig -a, we have (only relevant part too): > >pppoe0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1492 > dev: bge0 state: session > sid: 0xf0e2 PADI retries: 1 PADR retries: 0 time: 00:00:44 > sppp: phase network authproto pap authname > "[EMAIL PROTECTED]" > groups: pppoe egress > inet6 fe80::211:11ff:fee3:927e%pppoe0 -> prefixlen 64 scopeid 0x6 > inet 201.78.17.238 --> 0.0.0.1 netmask 0xffffffff > >I am not able to understand the cycle between 0.0.0.1 to default and >default to 0.0.0.1 entries for the routing information. I would guess that for the "host" route (ipv4 only), the only necessary knowledge it the interface through which the packet needs to be sent. At least in case of p2p interfaces. So the "gateway" is left at 0/0. Netstat, perhaps unfortunately, prints 0/0 as "default". >I am very confused. -- Pawel.
