I've read that that's the case, but how'bout a accept parsing error with
tcp.http. It exists nowhere in my files(any of them). I'm using the redhat
rpm of diald preconfigured for ppp0. Could it be compiled in?
Jacob Joseph
----- Original Message -----
From: Tom Horan <[EMAIL PROTECTED]>
To: 'Nerijus' <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, June 10, 1999 4:26 AM
Subject: RE: tap
> 'keepup parsing error. Got token.....'
> this one just means that your filter file refers to a service tcp.ssl
which
> is not in your /etc/services
> you need to put an entry in your /etc/services for ssl - sorry I forget
the
> port no.
>
> I dont know about the tap - I think it has something to do with
> ethertap.....
>
> As for the SIOC errors - this has something to do kernel 2.2 as in it
> handles the routes itself.....
>
>
>
> Hope it helps....
>
>
> > -----Original Message-----
> > From: Nerijus [SMTP:[EMAIL PROTECTED]]
> > Sent: Wednesday, June 09, 1999 10:19 PM
> > To: [EMAIL PROTECTED]
> > Subject: tap
> >
> > Hello,
> >
> > I've setup diald 0.99 on RedHat 6 intel machine and it works,
> > but I get some errors in /var/log/messages.
> > I think it is related with tap interface (it can be used instead
> > of slip if I understand correctly?). I created /dev/tap0. What else
> > should I do (didn't find any documentation about it in diald, sorry if
> > I overlooked)?
> >
> > Jun 9 15:49:30 server diald[957]: keepup parsing error. Got token
> > 'tcp.ssl'. Not a known tcp service port.
> > Jun 9 15:49:30 server diald[957]: parse string: 'tcp 120
> > tcp.dest=tcp.ssl'
> > Jun 9 15:49:30 server diald[957]: keepup parsing error. Got token
> > 'tcp.ssl'. Not a known tcp service port.
> > Jun 9 15:49:30 server diald[957]: parse string: 'tcp 120
> > tcp.source=tcp.ssl'
> > Jun 9 15:49:30 server modprobe: can't locate module tap0
> > Jun 9 15:49:30 server modprobe: can't locate module tap1
> > Jun 9 15:49:30 server modprobe: can't locate module tap2
> > ...........
> > Jun 9 15:49:30 server modprobe: can't locate module tap15
> > Jun 9 15:49:30 server diald[958]: start sl0: SIOCSIFMETRIC: Operation
not
> > supported
> > Jun 9 15:49:38 server diald[958]: Trigger: tcp 192.168.0.1/61024
> > 212.59.0.23/110
> > Jun 9 15:49:38 server diald[958]: Calling site 192.168.0.2
> > Jun 9 15:49:39 server chat[981]: timeout set to 50 seconds
> >
> > Jun 9 15:52:43 server diald[958]: start sl0: SIOCSIFMETRIC: Operation
not
> > supported
> > Jun 9 15:52:43 server diald[958]: start sl0: SIOCADDRT: File exists
> > Jun 9 15:52:43 server diald[958]: start sl0: SIOCADDRT: File exists
> > Jun 9 15:52:44 server diald[958]: Delaying 30 seconds before clear to
> > dial.
> > Jun 9 15:52:52 server diald[958]: Trigger: udp 192.168.0.1/1049
> > 195.12.164.250/53
> > Jun 9 15:53:14 server diald[958]: Calling site 195.12.160.247
> >
> > Jun 9 15:54:21 server pppd[1110]: pppd 2.3.8 started by root, uid 0
> > Jun 9 15:54:21 server pppd[1110]: Using interface ppp0
> > Jun 9 15:54:21 server pppd[1110]: Connect: ppp0 <--> /dev/ttyS0
> > Jun 9 15:54:24 server pppd[1110]: Remote message: ^D^EM-t^B^F
> > Jun 9 15:54:24 server pppd[1110]: local IP address 195.12.160.47
> > Jun 9 15:54:24 server pppd[1110]: remote IP address 195.12.160.247
> > Jun 9 15:54:25 server diald[958]: New addresses: local 195.12.160.47,
> > remote 195.12.160.247, broadcast 0.0.0.0
> > Jun 9 15:54:25 server diald[958]: start ppp0: SIOCSIFMETRIC: Operation
> > not
> > supported
> >
> >
> > What do these errors mean?
> >
> > Regards,
> > Nerijus
> >
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-diald"
in
> > the body of a message to [EMAIL PROTECTED]
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
