Discussion:
/sbin/route -interface issues w.r.t. routed,gated ...
(too old to reply)
Andreas Hallmann
2006-09-22 09:45:01 UTC
Permalink
Hi all,

setting up static route's with the -interface option works well ...
as long as you don't start a routing deamon.

I set up

route add default -interface gw.ahatec.de
route add -host aa.bb.cc.dd -interface gw.ahatec.de

using an interface's IP/Hostname
(pppoe0 in that case, but le0 show same behavier)

set up a metric
ifconfig pppoe0 metric 2

routing works well ...

starting either routed or gated
thoose route's stay in kernel but where droped by gated/routed.

with gated, /var/log/messages tells me:
...gated[..].. interface not found for
66.66.66.66/255.255.255.255 gw 217.173.147.11 Kernel

while routed cries about some ifp missing.
A quick look at the source tells me, he is also not finding an interface
for pppoe0's address.

appending a "-hopcount 2" to thoose route lines doesn't help either.

This is NetBSD 3.0_RC2, but the problem seams to exist for a longer time...

Why is the interface structure for pppoe0 not found ???
Any Idea's ??

BTW.: -HOPCOUNT option to route is not documented.

Thankx

AHA

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Andreas_Hallmann
2006-09-24 18:26:40 UTC
Permalink
Post by Andreas Hallmann
while routed cries about some ifp missing.
What is the exact routed message?
input.c: logbad(0,"missing USE_PASSIFNAME; only %d bytes",
input.c: msglim(use_authp, from, "missing password from %s",
parms.c: return "missing Keyid";
parms.c: return "missing second timestamp";
rdisc.c: logbad(0,"missing USE_PASSIFNAME; only %d bytes",
trace.c: msglog("missing trace file name");
Martin
Dear Martin, sorry for my late answer,..., due to me experiments I was not
available under my primary ip for a while.

Non of thoose, the exact message is:

Sep 22 08:33:33 newby routed[717]: static route 0.0.0.0 --> 217.173.147.11 impossibly lacks ifp

Moreover it seams, that a routed host, is not able to remove a static default route
he got durring boot up. I had to remove it to get it up working as expected.

Thankx
AHA

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Martin Husemann
2006-09-27 20:42:03 UTC
Permalink
Post by Andreas_Hallmann
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

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Andreas Hallmann
2006-09-29 21:32:55 UTC
Permalink
Post by Martin Husemann
Post by Andreas_Hallmann
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

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Martin Husemann
2006-09-29 22:10:44 UTC
Permalink
Post by Andreas Hallmann
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.
Hmm, can you add debug code to sbin/routed/if.c:if_link and check if
pppoe0 gets added to the interface list? The other problem could be
that it's ifp->int_dstaddr gets out of sync, you could check with
a printf in if.c:iflookup, in the POINTTOPOINT case by printing
ifp->int_dstaddr and addr.

Martin


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de
Loading...