On Thursday, September 23, 1999 2:58 AM, S.Toms
[SMTP:[EMAIL PROTECTED]] wrote:
Hello:
> The one that works is the 0.16 which was compiled for a slp type
> devices, the new one is the 0.99.1 I believe which is compiled for
> tap
> devices only, so no fallback to slp. I've gone thru your other email
> "Quick and dirty..." and have checked everything I can think of,
> still
> with the same results. Diald works fine, chat works fine and pppd
> work
> fine, it connects me to the internet, but nothing works, telnet, ftp,
> ping, http, nothing.
> I view the console on F10 and it reports no errors, I check
> /var/log/messages and the only things I can see are some SIOC errors
> or
> such as diald starts and makes a connection,
>
> diald[7273]: start tap0: SIOCSIFMETRIC: Operation not supported
> diald[7273]: start ppp0: SIOCSIFMETRIC: Operation not supported
> diald[7273]: stop tap0: SIOCDELRT: No such process
>
> which makes me believe its not connecting to the tap0 device, nor is
> it
> launching the modules for it (or something) everything else looks the
> same as the 0.16 connection. I've tried running it without creating
> the
> /dev/tapX with mknod as well as creating it, both report the same
> errors.
> The kernel is compiled for ethertap and af_packet modules, the
> correct
> entries are in the conf.modules file as below,
>
> alias tap0 ethertap
> options tap0 -o tap0 unit=0
> alias ppp-compress-21 bsd_comp
> alias ppp-compress-24 ppp_deflate
> alias ppp-compress-26 ppp_deflate
> alias net-pf-17 af_packet
>
> I've tried compileing the af_packet built-in as well as a module
and
> I'm
> receiving the same results as well. Does it have to be a module?
>
> With the 0.16 version, everything works fine, I unload 0.16 and
> install
> the new one using all the same config files and I get nothing. Are we
> sure
> I don't have to change anything in my config files for the tapX
> device
> connection?
You are using SuSE right? If so did you get the diald rpm for your
version of SuSE? I'm not at all familiar with that distribution but I
believe that it is quite different from plain RedHat.
Run ifconfig after starting diald and check if the tap0 device is
configured. By the excerpt of your syslog all seems OK those messages
are normal. And if diald and pppd are making the connection everything
must be OK, modules and all. af_packet doesn't need to be a module, but
if you loaded it it's working. Run lsmod to find out which modules are
loaded.
Are you using your old configuration files? Did you try with fresh
stock ones?
If everything is correct the problem is not with diald. Check your
resolv.conf, hosts, bind, and your packet filtering rules, they might
be blocking the connection.
I can't remember anything more...
---
Lazarus Long
<[EMAIL PROTECTED]>
PGP: <http://wwwkeys.pgp.net:11371/pks/lookup?op=index&search=0x5C1D
C205>
ICQ#: 30062012
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
