Martin Husemann wrote:

> On Sun, Sep 24, 2006 at 08:26:40PM +0200, Andreas_Hallmann wrote:
> 
>>Sep 22 08:33:33 newby routed[717]: static route 0.0.0.0 --> 217.173.147.11 impossibly lacks ifp
> 
> 
> I think it is confused by the 0.0.0.0 source. I wonder if you could restart
> routed after the interface is up - maybe that would fix it?
> 
> Martin

I don't think it is confused by 0.0.0.0 -> 217.173.147.11
It only meens that 217.173.147.11 is the hop for the default route.

There is both sides of the pppoe-'tunnel' have there address.

it' s

my-net ---- (gateway)
                  |
               if pppoe0 address 217.173.147.11
                  |
                  |
               otherside gateway router x.y.z.a

If I replace the static route by a

	default route to x.y.z.a

and a route which tells us that x.y.z.a is reachable with next hop 
217.173.147.11

anything works.

But other sides router ip changes from time to time.

This is excactly what the interface directive in the route command was 
build for. Yust telling: Throw frames into my side of the pppoe tunnel, 
and they will end up at some router which does better.

I feel a shame that linux does it, Sunos does it, Cisco's of course , ...
but my real love netbsd fails.

Don't know what's up whit the other bsd's...

Have a good night...

	AHA