diald config?
Henry A. Leinhos
yellowdog-general@lists.terrasoftsolutions.com
Wed Feb 19 08:55:01 2003
I've checked the system logs, and I do, indeed, get a bunch of messages:
> [root@blueg3 docs]# tail -n 100 /var/log/messages
> Feb 19 14:03:51 blueg3 diald[19826]: ignore parsing error. Got token
> 'udp.route'. Not a known udp service port.
> Feb 19 14:03:51 blueg3 diald[19826]: parse string: 'udp
> udp.source=udp.route'
<snip> - alot more errors related to "'udp.route'. Not a known udp
service port"
> Feb 19 14:03:51 blueg3 diald[19827]: Creating FIFO
> Feb 19 14:03:51 blueg3 diald[19827]: Could not open fifo file
> /var/adm/diald/prism
> Feb 19 14:03:51 blueg3 diald[19827]: Could not open TCP socket:
> Address already
> in use
(I can see that I need to set the FIFO file properly)
After that, I get a bunch of output from modprobe that module tapXX
can't be found (the ethertap device), and then it loads the SLIP device:
> Feb 19 14:03:52 blueg3 diald[19827]: Proxy device established on
> interface sl0
> Feb 19 14:03:52 blueg3 diald[19827]: start sl0: SIOCSIFMETRIC:
> Operation not
> supported
> Feb 19 14:03:52 blueg3 /etc/hotplug/net.agent: NET unregister event not
> supported
> Feb 19 14:03:52 blueg3 diald[19827]: Diald initial setup completed.
> Feb 19 14:03:52 blueg3 /etc/hotplug/net.agent: invoke ifup sl0
> Feb 19 14:04:08 blueg3 su(pam_unix)[19886]: session opened for user
> root by
> henry(uid=1001)
> Feb 19 14:06:21 blueg3 diald[19827]: Trigger: udp
> 192.168.0.64/32880
> 208.187.77.8/53
>
I can see the interface in ifconfig (the tun0 device is from MOL, and my
fake IP addresses for the interface are 192.168.0.64/65):
> [root@blueg3 docs]# /sbin/ifconfig
> eth0 Link encap:Ethernet HWaddr 00:05:02:0F:B8:C2
> inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:237308 errors:10 dropped:7 overruns:0 frame:7
> TX packets:305869 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
> RX bytes:44998062 (42.9 Mb) TX bytes:107482400 (102.5 Mb)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:1007 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1007 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
> RX bytes:250311 (244.4 Kb) TX bytes:250311 (244.4 Kb)
>
> sl0 Link encap:Serial Line IP
> inet addr:192.168.0.64 P-t-P:192.168.0.65 Mask:255.255.255.255
> UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> tun0 Link encap:Ethernet HWaddr 00:FF:AB:94:3A:50
> inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b
>
If I try to ping an outside IP address, the logs then show:
> Feb 19 14:06:21 blueg3 diald[19827]: Trigger: udp
> 192.168.0.64/32880
> 208.187.77.8/53
> Feb 19 14:06:21 blueg3 diald[19827]: Calling site 192.168.0.65
> Feb 19 14:06:21 blueg3 kernel: irda_setup timed out on 1st byte
> Feb 19 14:06:21 blueg3 last message repeated 2 times
> Feb 19 14:06:22 blueg3 diald[19827]: Connect script failed.
> Feb 19 14:06:22 blueg3 diald[19827]: Closing /dev/ttyS1
I'm fairly certain that I have changed the /etc/diald/device.conf file
to look at /dev/usb/ttyACM0 instead of any /dev/ttyS* devices, but I
need to check that. I'm not sure about all the errors, though.
>On Tue, 18 Feb 2003, Henry A. Leinhos wrote:
>
>>/ It does requre SLIP (to set up the proxy connection to the fake
>/>/ interface), but I don't think I'm getting any kernel messages regarding
>/>/ missing SLIP. On top of it all the published mailing list
>/>/ (majordomo@vger.rutgers.edu <mailto:majordomo@vger.rutgers.edu>) kicks back subscription requests with a
>/>/ "user unknown" error (hrumph). What I am seeing right now is that diald
>/
>vger moved. the current machine is vger.kernels.org
>
>>/ sets up the interface properly and detects access to it, but is getting
>/>/ hosed up trying to dial or talk to pppd (as witnessed by the diald log
>/>/ entries regarding "connecting to ...", but timing out). Anyone else
>/>/ have any experience with this?
>/>/
>/
>The log should point you iin the general dirction. IS there anything
>being logged? I seem to remember copious amounts of info in syslog.
>
>-n
>