[ Date Index ][
Thread Index ]
[ <= Previous by date / thread ] [ Next by date / thread => ]
neil wrote: > > Linuxconf was looking for the modem on /dev/modem when it should have been > looking at /dev/tty0 which is where KPPP ws looking. Other apps seemingly > took their queue from linuxconf/DrakConf and looked at /dev/modem for I/O - > hence the disappointment. Now you mention it.... been there, I ended up linking /dev/modem to /dev/tty0 as apps seem to vary. This isn't an ideal approach as some locking of the device file is cooperative, one locks /dev/modem, one locks /dev/tty0 (by creating files in /var/lock....), but for a desktop box it made life easier. > This is my first message from a Linux box direct to the Internet - I've > always had to use proxies until now. Great > ppp0 Link encap:Point-to-Point Protocol > inet addr:62.64.170.120 P-t-P:62.64.191.200 Mask:255.255.255.255 > UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 > RX packets:246 errors:7 dropped:0 overruns:0 frame:7 errors 7 - hmm I just backed up my entire disk over a Wireless LAN, and have less errors on that interface (zero actually). Probably just a handshake problem or something, have a look next time, and see if it does the same, but I wouldn't let it worry you, probably line noise or something. > Thanks for the help Simon - I'd be grateful if you'd cast your eyes over the > above just to be sure that I've got the thing working properly! Ta. "netstat -a" is your friend..... learn to understand it's output.... 23:28:52 srw srw $ netstat -a | head -20 Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 1 0 localhost:1697 localhost:www CLOSE_WAIT tcp 0 0 localhost:imap2 localhost:1696 ESTABLISHED tcp 0 0 localhost:1696 localhost:imap2 ESTABLISHED localhost who cares.... it talks to itself. tcp 1 0 wretched.demon.co.:1695 nnrp-08.news.demon:nntp CLOSE_WAIT I talked to a newsserver recently.... zzzZZZZ tcp 24 0 wretched.demon.co.:1693 212.1.130.5:https CLOSE_WAIT I talked to a secure web server... zzzzZZZZZ tcp 0 0 *:1668 *:* LISTEN My goodness I listen on all IP interfaces for port 1668..... 23:23:35 srw srw $ fuser 1668/tcp 1668/tcp: 8970 23:31:12 srw srw $ ps -ef | grep 8970 srw 8970 8917 0 21:49 ? 00:00:08 /usr/bin/kicq -restore kicqrc.4 srw 9457 9431 0 23:31 pts/0 00:00:00 grep 8970 Okay so that was just my kicq program, I kind of trust it (Actually he makes me nervous, but I like ICQ). tcp 0 0 wlinux1:1667 192.169.1.3:ssh ESTABLISHED tcp 0 60 linux1:ssh 192.169.1.3:1033 ESTABLISHED tcp 0 0 localhost:953 *:* LISTEN tcp 0 0 linux1:domain *:* LISTEN tcp 0 0 wlinux1:domain *:* LISTEN tcp 0 0 localhost:domain *:* LISTEN Hehe all internal interfaces... zzzZZZ tcp 0 0 *:X *:* LISTEN This is filtered in my ipchains. tcp 0 0 localhost:ssh *:* LISTEN tcp 0 0 linux1:ssh *:* LISTEN tcp 0 0 wlinux1:ssh *:* LISTEN More internal... tcp 0 0 wretched.demon.co:https *:* LISTEN tcp 0 0 wretched.demon.c:sunrpc *:* LISTEN Wow Simon's Linux box listens on port 111 on all IP interfaces. However this isn't portmapper, and if you touch my port 111 you'll be on my blacklist of nasty hackers. You need to understand all the "*:" entries, and any entries listing the IP address/name of your Internet interface. This tells you what incoming connections your box will accept. Top of the BAD list are; Port 53 (domain), Port 111 (sunrpc), and 20/21 (ftp), you really don't want these listening to the Internet connected Interface unless you have spent lots of time securing the box. On a good week I'd scan your box with "nmap" and maybe nessus, but it's been a bad week. Try me when I've finished the current "assignment". Simon -- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe.