Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I have a problem with Diald 0.99.4 on RH 6.0
It trigged by a pop3 client I my LAN 192.168.1.12 and it is accessing the pop-server 188.8.131.52.
Everything is going OK. The link goes up and the POP client thus what I should and stops sending.
The link goes down due idle and everything seems OK
BUT a couples of minutes later DIALD gets trigged by a packet.
Here it starts
Nov 26 20:33:34 Server_L1 diald: Trigger: tcp 192.168.1.12/1501 184.108.40.206/110
Nov 26 20:33:34 Server_L1 diald: Calling site 220.127.116.11
Nov 26 20:33:36 Server_…..
Nov 26 20:43:44 Server_L1 diald: Closing down idle link.
Nov 26 20:43:46 Server_L1 pppd: Terminating on signal 2.
Nov 26 20:43:46 Server_L1 pppd: Connection terminated.
Nov 26 20:43:46 Server_L1 pppd: Connect time 9.7 minutes.
Nov 26 20:43:46 Server_L1 pppd: Sent 1182 bytes, received 1280 bytes.
Nov 26 20:43:47 Server_L1 pppd: Exit.
Nov 26 20:43:47 Server_L1 diald: Disconnected. Call duration 583 seconds.
Nov 26 20:43:47 Server_L1 diald: IP transmitted 933 bytes and received 1101 bytes.
Nov 26 20:43:47 Server_L1 diald: Closing /dev/ttyS1
Nov 26 20:43:48 Server_L1 diald: running ip-down script '/etc/sysconfig/network-scripts/pppfw_down 'sl0' '255.255.255.255' '18.104.22.168' '22.214.171.124''
Nov 26 20:43:48 Server_L1 diald: Delaying 5 seconds before clear to dial.
<< The link is down >>
Nov 26 20:53:42 Server_L1 diald: Trigger: tcp 126.96.36.199/110 192.168.1.12/1501
Nov 26 20:53:42 Server_L1 diald: Calling site 188.8.131.52
Where have that packed 184.108.40.206/110 192.168.1.12/1501 been ?
The link is down how than a packed arrive from “outside” and then brink up the link ?