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'm playing arround with Dante-Client for some time now but I'm not able to configure it properly because every software I start via Dante-Client ends with the error "Connection reset by peer" or "network unreachable".
My Lan consists only of 2 Pc's . One running WinXp and the Proxyserver (192.168.1.1) and one running Debian Linux (192.168.1.2).
The strange thing is, my Linux Pc can use the built-in proxy configuration of Firefox and similar programs. If I start Firefox with Dante , in the Proxyserver logs i can see that it is resolving the IP for the given hostname, but the client never gets this Information. (Connection reset by peer).
I think that I have to set the routes for accepting connections, but I don't know how I have to set them.
The explanation in the dante.conf file down below does not help me either. Perhaps someone can explain to me what I am doing wrong.
#debug: 1 # uncomment to enable debugging
logoutput: stdout # users usually don't want to be bothered with that.
# What protocol should be used for resolving hostnames? It's important
# to set this right.
resolveprotocol: udp # default
#resolveprotocol: tcp # set this if your socksserver only supports socksv4.
#resolveprotocol: fake # set this if your clients can't access nameserver,
# neither directly nor proxied.
# the routes
# specifying routes for accepting remote connections (via bind()) is
# difficult since we can't know what the "to:" address is
# until we actually get the connection Since we support letting
# the client accept connections both via the proxyserver and
# "directly" at the same time, we have two options though:
# a) specify a route for bind (only) first going via the proxyserver.
# This will also handle "direct" connections.
# b) specify a route for bind (only) first going "direct".
# This means clients will only be able to accept "direct"
# we want to accept remote connections via the proxyserver.
# from: 0.0.0.0/0 to: 0.0.0.0/0 via: 192.168.1.1 port = 1080
# command: bind
# we do not want to accept remote connections via the proxyserver.
# from: 0.0.0.0/0 to: 0.0.0.0/0 via: direct
# command: bind
# have a route making all connections to loopback addresses be direct.
from: 0.0.0.0/0 to: 127.0.0.1/0 via: direct
command: connect udpassociate # everything but bind, bind confuses us.
# Our net is the 10.0.0.0/8 net, let clients going to local address go
# direct, not via server.
from: 192.168.1.0/0 to: 192.168.1.0/255.255.255.0 via: direct
# clients going anywhere else go via server listening at
# IP address 10.1.1.1, port 1080. Note that unless you have
# specified a direct connection for DNS, or the socksserver is resolvable
# without network traffic, you can't give a hostname for the socksserver,
# you must give a IP address. (the reasons for that are logical enough,
# you would create a loop otherwise.)
from: 0.0.0.0/0 to: 0.0.0.0/0 via: 192.168.1.1 port = 1080
protocol: tcp udp # server supports tcp and udp.
proxyprotocol: socks_v5 # server supports socks v4 and v5.
method: none #username # we are willing to authenticate via
# method "none", not "username".