hello everybody !
i have just subscribed to this list, sorry if this has been
discussed before.
i was unable to find a faq or archive, so here goes my problem:
my setup consists of a server running 2.2.14 with diald 0.99.1
(precompiled from the suse 6.2 distro).
it connects two other boxes to the internet via a dialup ppp line
and has masquerading and routing.
now i need a default route to the isp's gateway. i can't put it in
route.conf, because it will not work when the host is unreachable,
which it is most of the time. so i have to create one on-the-fly
when diald connects.
diald does set a route to the remote host upon connection, but it's
not the default, and the other boxes don't know where to send their
stuff...
my isp's gateway always has the same address, but that doesn't help,
because i can't set this as default gateway on the other boxes
either when the link is not up...
am i overlooking something stupid ?
(i have noticed the addroute option, but i couldn't get it to work;
anyway, it seemed this option adds a route on starting diald, which
is not what i need.)
here are some other oddities i found in my syslog:
Mar 31 22:26:06 spunk diald[8633]: keepup parsing error. Got token
'tcp.ssl'. Not a known tcp service portMar 31 22:26:06 spunk
diald[8633]: parse string: 'tcp 120 tcp.dest=tcp.ssl'
Mar 31 22:26:06 spunk diald[8633]: keepup parsing error. Got token
'tcp.ssl'. Not a known tcp service portMar 31 22:26:07 spunk
diald[8633]: parse string: 'tcp 120 tcp.source=tcp.ssl'
(i think this is discussed in the faq. i will check my services
file...)
Mar 31 22:26:07 spunk modprobe: modprobe: Can't locate module tap0
Mar 31 22:26:07 spunk modprobe: modprobe: Can't locate module tap1
Mar 31 22:26:07 spunk modprobe: modprobe: Can't locate module tap2
Mar 31 22:26:07 spunk modprobe: modprobe: Can't locate module tap3
Mar 31 22:26:07 spunk modprobe: modprobe: Can't locate module tap4
Mar 31 22:26:07 spunk modprobe: modprobe: Can't locate module tap5
Mar 31 22:26:07 spunk modprobe: modprobe: Can't locate module tap6
Mar 31 22:26:07 spunk modprobe: modprobe: Can't locate module tap7
Mar 31 22:26:07 spunk modprobe: modprobe: Can't locate module tap8
Mar 31 22:26:07 spunk modprobe: modprobe: Can't locate module tap9
Mar 31 22:26:07 spunk modprobe: modprobe: Can't locate module tap10
Mar 31 22:26:07 spunk modprobe: modprobe: Can't locate module tap11
Mar 31 22:26:07 spunk modprobe: modprobe: Can't locate module tap12
Mar 31 22:26:07 spunk modprobe: modprobe: Can't locate module tap13
Mar 31 22:26:07 spunk modprobe: modprobe: Can't locate module tap14
Mar 31 22:26:07 spunk modprobe: modprobe: Can't locate module tap15
(this shows up whenever diald is started. is this related to the
"ethertap" devices option in the kernel config ? what do these
devices do ??)
Mar 31 22:26:07 spunk diald[8634]: start sl0: SIOCSIFMETRIC:
Operation not supported
Mar 31 22:26:07 spunk diald[8634]: start sl0: RTNETLINK answers:
File exists
(might this be the reason for my route problem ?)
Mar 31 22:27:19 spunk diald[8634]: start ppp0: SIOCSIFMETRIC:
Operation not supported
Mar 31 22:27:19 spunk diald[8634]: start ppp0: RTNETLINK answers:
File exists
Mar 31 22:27:20 spunk diald[8634]: start ppp0: RTNETLINK answers:
File exists
my very humble assumption is that the new kernels do some things
quite different from the older ones and diald gets a little bit
confused.
the kernel change files were of no use, nor was the diald faq :(
any help is greatly appreciated.
yours,
j�rn
--
J�rn Nettingsmeier
Kurf�rstenstr. 49
45138 Essen, Germany
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
