Anzeige:
Ergebnis 1 bis 11 von 11

Thema: Wie Linux-seitig NAT mit ADSL router konfigurieren?

  1. #1
    Registrierter Benutzer
    Registriert seit
    Sep 2001
    Beiträge
    725

    Wie Linux-seitig NAT mit ADSL router konfigurieren?

    Nabend,

    Hab ein speedtouch-510-ethernet-adsl-modem das auch ein wenig routen und natten kann.

    Was ich machen wollte ist ein NAT mit dem Internet und meinem Client aufzubauen.
    Dabei hat das modem ip:10.0.0.138 und ich 10.0.0.1.

    Das modem selbst unterstützt das, allerdings hab ich keinen Dunst, wie ich NAT nun unter Linux einrichten kann? Wahrscheinlich mit IPTables.

    Kennt jemand eine einache Lösung dieses Problems oder ein Tutorial - ich möchte nicht durch 300 Seiten iptables-doku durch müssen um sowas einfaches zu machen...

    Danke schon im Vorraus, mfg
    Geändert von Lin728 (19.08.17 um 08:18 Uhr)

  2. #2
    Registrierter Benutzer Avatar von klemens
    Registriert seit
    Nov 2002
    Ort
    Wien
    Beiträge
    2.061
    Kannst Du vielleicht genauer sagen, wer jetzt "natten" soll?
    Das Modem oder der Linuxrechner oder beide hintereinander??

    Standardwerk für einen Linux-NAT-Router ist:
    http://www.linuxforen.de/forums/showthread.php?t=60561

    (Die iptables-DOKU hat nur 299 Seiten und weniger )

  3. #3
    Registrierter Benutzer
    Registriert seit
    Sep 2001
    Beiträge
    725

    Hmmm

    Das modem hat nach aussen z.B. die IP 78.23.23.12 und nach "innen" 10.0.0.138.
    Mein Rechner hat 10.0.0.1.

    Was ich nun machen möchte ist, dass wenn z.B. eine Anfrage von aussen an das modem (78.23.23.12) kommt, diese Anfrage transparent zu meinem Rechner 10.0.0.1 durchgeleitet wird und genauso umgekehrt.

    Brauche dass, so dass ich z.B. von "aussen" (=Internet) x-traffic auf meinen heimrechner (10.0.0.1) forewarden kann, oder mich per ssh einloggen kann...

    gibts da eine einfache Lösung?

    Das modem kanns jedenfalls laut beschreibung:
    Code:
     
    About this on-line Help
    
    This on-line Help is intended to provide context related help for setting-up your SpeedTouch 500Series Multi-User DSL Gateway, understand its operation and exploring its advanced features.
    
    Additionally, these Help pages aim to provide general yet valuable information.
    
    For a Content List, click here.
    
    Next to this on-line Help more information can be found in your SpeedTouch 500Series product's:
    
        * Quick Installation and Setup and User's Guide
        * Application Notes and Technical papers
        * Help facility of its Command Line Interface
        * CLI Reference Guide 
    
    And the SpeedTouch support web pages at:
    
    www.speedtouch.com
    
    In case you want to know more on the SpeedTouch 500Series Multi-User DSL Gateway's features and supported functionalities, it is advised to read the SpeedTouch 500Series at a Glance section.
    
    To go directly to the context related help on the SpeedTouch 500Series web pages and configurable items, follow The SpeedTouch 500Series Web Pages link or follow one of the links in the Content List below.
    
    Content List
    
    The SpeedTouch 500Series at a Glance
    # Introducing DSL
    # Connection and Packet Services
    # IP Router and LAN Services
    # Universal Plug and Play (UPnP)
    
    The SpeedTouch 500Series Web Pages
    # Introduction and Overview
    # Basic Tasks
    # System Information
    # Connections
    # System Log
    # Advanced Tasks
    # Diagnostics
    # Easy Setup
    # IP Addresses
    # IP Routing
    # NAPT
    # DHCP
    # DNS
    # System
    # System Password
    # Templates
    # Language
    
    The SpeedTouch 500Series Advanced Features
    # Command Line Interface
    # Packet Firewalling
    # Packet Classification
    The SpeedTouch 500Series at a Glance
    
    Combining today's DSL technology with unique features as an integrated and programmable Firewall, advanced IP Router functionality and LAN services, yet easy configurable for all most common Internet connection services and featuring full UPnP support, the SpeedTouch 500Series Multi-User DSL Gateway is the ideal solution for demanding Internet users.
    Introducing DSL
    
    DSL is short for Digital Subscriber Line. This somewhat cryptic name is best explained in straightforward terms:
    
        * Line
          DSL uses the ordinary existing copper line, known as "local loop, running between your local premises and the telephone central office.
        * Subscriber
          That's you, the end-user. Because this is what Service Providers or operators call their customers.
        * Digital
          DSL is a digital transmission technology. To a certain extend, digital information is not affected by impairments on the telephone line, thus achieving a higher reliability.
    
    Compared to traditional analog or ISDN modems, DSL transfers information up to 200 times faster and even more depending on the applied DSL service, local loop length and loop quality.
    
    The popular term DSL refers to lot more than the raw "DSL Technology? alone. Indeed, on one hand DSL refers to advanced modulation and demodulation techniques, applied to the copper wire between a subscribers? home and the telephone service provider?s central office. The net result of this technology is a boost in bandwidth from a few tens of kilobits to a multiple of megabits.
    
    On the other hand, as the distance DSL covers is limited to only a few kilometers, a wide area communication infrastructure is required to transport data to ISPs and Corporate data centers. For this purpose, Asynchronous Transfer Mode (ATM) has been selected.
    
    ATM is a connection-oriented packet switching technology using fixed-size packets, called cells. These cells consist of a header and a payload and are switched through a private or public ATM network, depending on the contents of the header. End-to-end connections are formed by cross-connecting individual ATM segments in ATM switches.
    Connection and Packet Services
    
    As part of the DSL service provisioning the ISP configures a Connection Service at the remote end of each virtual channel.
    
    Connectivity to the Internet or an Enterprises? Intranet is by far the most important service offered by an ISP. To provide this end-to-end service your ISP will require the SpeedTouch 500Series to use of a certain frame format on the virtual channel running between the SpeedTouch 500Series and its access server. As a consequence, the SpeedTouch 500Series must be configured to correctly adhere to the Central Office settings and requirements.
    All these requirements can be collectively referred to as Connection Service and consist of a connection service name, the virtual channel identifier, the connection service type, and the ATM encapsulation type. Whether a connection is always-on or dial-up and the way IP configuration is accomplished in the remote end, is mostly implied in the connection service name. E.g. PPP is native dial-up and IP configuration happens via PPP-IPCP.
    
    The SpeedTouch 500Series supports all common Connection Services to be configured:
    
        * Ethernet over ATM (ETHoA) - RFC1483/Bridged
        * PPP over ATM (PPPoA) - RFC2364
        * IP over ATM (IPoA) - RFC1483/Routed
    
    Another important aspect refers to the way it should forwards frames or packets between the DSL line and LAN ports and vice versa. To accomplish this, the Connection Service offered on the DSL line needs to be ?attached? to the appropriate Packet Service in the SpeedTouch 500Series.
    
    A Packet Service be defined as: the actions that need to be performed on each data packet in order to filter or forward packets to the next device in the communication chain.
    
    Otherwise stated, a Packet Service is a combination of processes transferring data packets from one side of the SpeedTouch 500Series to the other side and vice versa. E.g. it will forward data packets from your PCs to remote destinations and vice versa. Yet all packet services will prevent communication between devices on your local network from escaping via the DSL line.
    
    Different Packet Services will be called upon depending on:
    
        * The port on which packets arrive e.g. LAN port or DSL port;
        * The type of data packets, i.e. whether it concerns IP packets, MAC frames or PPP frames;
        * Their properties e.g. unicast, multicast;
        * The actual configuration of your SpeedTouch 500Series. 
    
    Your SpeedTouch 500Series supports the following Packet Services:
    
        * Bridged Ethernet
        * Routed Ethernet
        * Bridged PPPoE
        * Routed PPPoE
        * PPPoE Relay
        * Relayed PPPoA
        * Routed PPPoA
        * Routed IPoA
        * Classical IP. 
    
    One or more of these Packet Services can be automatically configured at time of installation via the (embedded) Setup wizard, or via uploading the appropriate configuration file or configuration template.
    IP Router and LAN Services
    
    The SpeedTouch 500Series offers a broad range of IP functionality, going from (labeled) IP routing, logical multi-homing, Classless InterDomain Routing (CIDR) and Variable Length Subnet Masking (VLSM) over the built-in DHCP Server, DHCP Relay, DHCP Client and DNS Server and Proxy, up to support for advanced Network Address and Port Translation (NAPT) techniques and UPnP NAPT Traversal functionality, and an integrated Packet Firewall.
    Universal Plug and Play (UPnP)
    
    The SpeedTouch 500Series provides full support for UPnP and the UPnP Internet Gateway Device (IGD) standard. UPnP allows to easily access and control your SpeedTouch 500Series via an icon on your PC.  UPnP and its NAPT Traversal feature provides broadband users at home with a seamless way to participate in online games, videoconferencing and other peer-to-peer services.
    
    UPnP is supported on Windows XP natively. For Windows 98/ME and Windows 2000 UPnP is not supported. However installing DirectX8.1, or DirectX9.0 and later will enable games to use the UPnP NAPT Traversal feature.
    
    For more information on how you can use the SpeedTouch 500Series' UPnP functionality, you can check the SpeedTouch support pages at http://www.speedtouch.com/upnp.htm.
    The SpeedTouch 500Series Web Pages
    Introduction and Overview
    
    The SpeedTouch 500Series web pages allow you to overview and configure all most common SpeedTouch 500Series settings.
    
    The SpeedTouch 500Series web pages are accessible by the links presented in the left frame on each of the pages.
    
    The links are grouped in so-called tasks menus. The following tasks menus exist:
    Basic
    
    The Basic Tasks menu groups all links that are the most often used when working with the SpeedTouch 500Series. Following links are available:
    # System information
    This link allows you to:
    # Overview the basic SpeedTouch 500Series status overview
    # Overview the SpeedTouch 500Series service information
    # Overview the currently applied configuration profile information.
    # Overview some SpeedTouch 500Series system identifiers.
    # Connections
    This link allows you to:
    # Easily start/stop Routed PPPoA and Routed PPPoE (Relay) connection sessions.
    # System Log
    This link allows you to:
    # Overview system messages generated by the SpeedTouch 500Series.
    Advanced
    
    The Advanced Tasks menu groups all links that lead you to specific and advanced configurations and services the SpeedTouch 500Series provides. Following links are available:
    # Diagnostics
    This link allows you to:
    # Overview detailed diagnostics information on the SpeedTouch 500Series system variables and configuration
    # Display configuration information, status reports, statistics and properties of the SpeedTouch 500Series LAN and WAN interfaces and connections.
    # Perform diagnostical IP connectivity checks.
    # Easy Setup
    This link allows you to:
    # Start the embedded SpeedTouch Easy Setup wizard.
    # IP Addresses
    This link allows you to:
    # Overview or change the SpeedTouch 500Series IP configuration
    # IP Routing
    This link allows you to:
    # Overview or change the SpeedTouch 500Series IP routing table.
    # NAPT
    This link allows you to:
    # Overview or change static NAPT entries
    # Overview or change multi-NAT entries
    # Overview or change the NAPT default server for your network
    # Set UPnP policy.
    # DHCP
    This link allows you to:
    # Configure the SpeedTouch 500Series DHCP server
    # Configure the SpeedTouch 500Series DHCP relay
    # Configure the SpeedTouch 500Series DHCP client.
    # DNS
    This link allows you to:
    # Configure the SpeedTouch 500Series DNS server.
    # System
    This link allows you to:
    # Overview the SpeedTouch 500Series system software version
    # Check for System Software updates on the Internet
    # Back up your configuration.
    # Upload another configuration.
    # Restore the SpeedTouch 500Series default settings.
    # System Password
    This link allows you to:
    # Prevent unauthorized access to the SpeedTouch 500Series.
    # Templates
    This link allows you to:
    # Overview available configuration templates
    # Upload configuration templates to the SpeedTouch 500Series.
    # Language
    This link allows you to:
    # Upon availability, select another user interface language for the web pages.
    System Information
    
    The SpeedTouch 500Series System Information page - also serving as its home page - provides a quick overview of the device's connection status, configuration,  and shows some basic system statistics and settings.
    
    The System information page contains four tabs:
    
        * Diagnostics
        * Service Info
        * Configuration
        * System
    
    Diagnostics
    The Diagnostics table provides a one-view control on the system's integrity self test, Ethernet (and, if applicable, USB) connectivity test and DSL line synchronization test.
    
    For a full view of the system's status, you can go to the advanced Diagnostics web page.
    Service Info
    The Service Info table shows some details of the current DSL line status. Following information is given:
    
        * Line state
          Shows whether the DSL link is synchronized (Enabled) or not (Initializing).
        * Speed
          Shows the maximum available bandwidth of the DSL link in both up- and downstream direction.
        * Duration
          Shows the duration of the current "Enabled" Line state
        * Sent
          Shows the amount of Kilo Bytes sent since the establishment of the DSL link.
        * Read
          Shows the amount of Kilo Bytes received since the establishment of the DSL link.
    
    In addition, per connection configured, the local WAN and primary and secondary DNS server IP addresses are shown. For a list of the available dial-in connections, check the Connections web page.
    Configuration
    The Configuration table, shows the name of the region and ISP for which this configuration applies, the service name is provided, followed by a description of its functionality.
    System
    The System table shows following device specific parameters:
    
        * The SpeedTouch 500Series product name
        * The SpeedTouch 500Series unique MAC address
        * The SpeedTouch 500Series IP address
        * The SpeedTouch 500Series software version
        * The SpeedTouch 500Series hardware platform
        * The SpeedTouch 500Series serial number
        * The SpeedTouch 500Series product code.
    
    Note : MAC address is short for Medium Access Control address and is the standardized name for Ethernet address.
    Connections
    
    On this page a list of the available dial-in connections is presented.
    
    To establish a session:
    
       1. Select the appropriate connection you want to establish a session with.
       2. If needed, specify your user name and password for the user account at the ISP.
       3. Click Connect.
    
    The SpeedTouch 500Series will try to setup a session with its remote peer. The State field will show Trying as long as the session is not established. If the connection is established, the State field will change from Down to Up. At this point, the SpeedTouch 500Series is ready to forward and receive data via this connection.
    
    To terminate an active session (state is Up or Retrying):
    
       1. Select the appropriate connection you want to terminate a running or pending session for.
       2. Click Disconnect.
    
    System Log
    
    System log messages are used to provide a historical overview of events, errors, and messages generated during SpeedTouch 500Series operation.
    
    The System Log web page allows you to overview all syslog messages the SpeedTouch 500Series generated since its last reboot.
    
    By default the table is automatically refreshed every 30 seconds and shows all system log messages.
    
    Via the system log message table's bottom row you can select:
    # View All
    To view all system log messages the SpeedTouch 500Series has generated
    # View Important Only
    To view messages the SpeedTouch 500Series generated to notify a important system events:
    # Warnings
    # Error conditions
    # Critical conditions
    # Alerts, requiring immediate actions to solve
    # Emergency conditions, notifying the SpeedTouch 500Series being unusable for normal service
    # View Critical Only
    To view all critical messages, the SpeedTouch 500Series generated to notify an event that may have caused severe changes to the SpeedTouch 500Series' operational state:
    # Critical conditions
    # Alerts, requiring immediate actions to solve
    # Emergency conditions, notifying the SpeedTouch 500Series being unusable for normal service
    
    If you click Stop AutoRefresh, the automatic refresh of the table is stopped. An extra menu allows you to configure the refresh rate in seconds (30 seconds by default). Click AutoRefresh to apply your changes and to start automatic update of the table (using the new refresh rate).
    Diagnostics
    
    The SpeedTouch 500Series Diagnostics web page provides advanced information, counters and statistical data on the SpeedTouch 500Series system settings, and its LAN and WAN connections.
    
    The diagnostics are broken down into three expandable categories:
    
        * System
        * WAN
        * LAN
    
    Five clickable buttons are present on the Diagnostic web page. Use:
    
        * Help
          To pop up this help page.
        * Expand
          To expand all diagnostic categories.
        * Collapse
          To collapse all diagnostic categories.
        * IP connectivity
          To instantly check all SpeedTouch 500Series connections on IP connectivity.
        * Refresh
          To refresh the diagnostic information.
          Use the Refresh button
    
    System
    
    The System diagnostics shows detailed system information of the SpeedTouch 500Series.
    WAN
    
    The WAN diagnostics are subdivided into two sections: DSL and Connections.
    
    The DSL section provides detailed information on the characteristics, state, properties and statistics of the current DSL line synchronization state.
    
    The Connections section provides, per connection, a detailed overview of the connection's characteristics, IP connection parameters, Packet Service specific parameters, and ATM specific settings and statistics for your Internet connection services.
    LAN
    
    The LAN section provides, per Ethernet interface, its current working, and configuration mode. Moreover, statistics are provided on sent, received and failed Ethernet activity.
    Easy Setup
    
    Clicking the Easy Setup link will start the embedded SpeedTouch Easy Setup wizard that provides an easy way to prepare the SpeedTouch 500Series  for Internet connectivity in no time without the need of the SpeedTouch Setup CD-ROM.
    
    Depending on the installed Templates you can select from one or more semi-automatic scripts helping you to fully configure most aspects of the SpeedTouch 500Series with a minimum of effort and risk of wrong or insufficient configurations.
    IP Addresses
    
    The IP address table shows all IP addresses configured on any interface of the SpeedTouch 500Series. Some of the IP addresses are configured automatically at boot time, others are either manually configured or negotiated on the fly.
    
    For each IP address, the following information is provided:
    
        * The interface for which the IP address applies
        * The IP address and (sub)net mask
        * The IP address type
              o auto
                For IP addresses that are automatically assigned by the SpeedTouch 500Series
              o extra
                Manually added IP addresses
              o user
                The default main IP address of the SpeedTouch 500Series' IP host
              o CIP
                To identify the local IP address of a Classical IP interface
        * Whether NAPT is applied on the IP address (pat) or not (none).
    
    Via the IP address table you can also manually add, or delete IP addresses.
    IP Routing
    
    The IP Routing table presents the current content of the SpeedTouch 500Series  Routing Information Base (FIB). It contains all routes to all possible destinations and is consulted by the SpeedTouch 500Series anytime prior to sending or forwarding any packets.
    
    Similar to the IP address table, a number of IP Routes are pre-configured. Other routes are either added automatically by adding an IP address or via the address negotiation of a Packet Service connection session, or can be added manually.
    
    The SpeedTouch 500Series IP Routing mechanism is based on the labeled routing feature; an extension of the preceding source-routing capability. With label-based routing, packets can be validated against a set of user-defined rules and, if matching,  consequently classified by assigning a label, in order to apply specific routing rules to it. This way the SpeedTouch 500Series is capable of forwarding packets matching specific parameters according specific labeled routes. More information on Packet classification can be found in this Help's Packet Classification section (See Advanced Features for more information.
    
    Interface routes are routes assigned to one of the SpeedTouch 500Series interfaces rather than route to a fixed IP address (i.e. the gateway's IP address). This allows configuration of routes for destinations, for which at time of configuration the gateway IP address is not yet known, or the local peer interface is not assigned with an IP address. Interface routes are indicated in the IP Routing table with an asterisk.
    
    Only in special circumstances routes should be manually added/configured or deleted to/in or from the SpeedTouch 500Series' Forwarding Information Base.
    Network Address and Port Translation
    
    Network address (and Port)  translation (NAPT) is a technique used to share one IP address amongst several computers. For most common applications, enabling NAPT on a specific interface is adequate. From then on, all clients behind the NAPT router automatically share the same IP address. To run a server behind a NAPT router, extra configuration is needed. On the NAPT page, you can specify these settings.
    
    The NAPT web page contains four tabs:
    
        * NAPT Entries
        * Multi-NAT Entries
        * Default Server
        * UPnP
    
    NAPT Entries
    
    For outgoing connections, NAPT entries are created dynamically whenever information migrating through this connection tries to reach a foreign host. For incoming connections however this is not done, mainly for security reasons, so therefore the NAPT entries table allows you to specify static NAPT entries. A static NAPT entry will redirect all incoming connections on a specified address/port to an address/port in the local network.
    
    The SpeedTouch 500Series can have multiple IP addresses, therefore you can specify the IP address in the Outside IP box on which to perform NAPT, and the Outside port. Using 0.0.0.0 as outside IP address causes a template to be created, which will be valid for every one of the SpeedTouch 500Series' NAPT enabled IP addresses established AFTER the creation of the template. In the input boxes 'Inside IP' and 'Inside PORT' you can specify the local machine and port to which traffic needs to be redirected.
    
    The Protocol selection box is used to specify the protocol of the traffic expected to be received on the inside IP:PORT. Keep in mind that the Inside and Outside Ports only need to be specified for the TCP and UDP protocols. All other protocols don't need a port to be specified.
    
    Notice that saving static NAPT entries could be a problem if you work with dynamic IP addresses (for example, if you use a PPP link to connect to the internet, then the SpeedTouch 500Series  will get a different IP address every time you establish a connection). In this case the only way to be able to save your settings is to use a template, so that you don't have to specify which SpeedTouch 500Series  IP address to use.
    Geändert von Lin728 (21.08.17 um 17:00 Uhr)

  4. #4
    Registrierter Benutzer Avatar von klemens
    Registriert seit
    Nov 2002
    Ort
    Wien
    Beiträge
    2.061
    Das modem hat nach aussen z.B. die IP 78.23.23.12 und nach "innen" 10.0.0.138.
    Ok - Wenn Dein Modem die öffentliche IP hat, dann bist Du also bei der Lösung geblieben, das Modem als Router einzurichten - ist wichtig, weil das jetzt zuerst mit Modemkonfiguration zu tun hat und weniger mit Linux-Konfiguration.

    Network address (and Port) translation (NAPT) is a technique used to share one IP address amongst several computers. For most common applications, enabling NAPT on a specific interface is adequate. From then on, all clients behind the NAPT router automatically share the same IP address. To run a server behind a NAPT router, extra configuration is needed. On the NAPT page, you can specify these settings.
    Hört sich danach an.

    Ich habe das Modem selber nicht, aber die Einstellung eines Portforwarding ist allgemein:
    Port xy weiterleiten auf LAN-IP aaa.bbb.ccc.ddd

    Bei ssh könnte das so aussehen:

    Port 22 weiterleiten auf 10.0.0.1

    10.0.0.1 muss ins Internet können und sshd muss entsprechend konfiguriert sein und laufen.

  5. #5
    Registrierter Benutzer
    Registriert seit
    Sep 2001
    Beiträge
    725

    Hmmm?

    Und am Linux-Client muss ich nichts weiter machen? - weil genauso wie dus beschrieben hast hab ichs gemacht - nur funktionierts einfach nicht...

    Muss man am Linux-Client (10.0.0.1) nicht einstellen, dass man das weitergeleitet bekommt?
    Und wie kann man einstellen, dass der Linux-Rechner selbst über NAT nach draussen kommt - weil derzeit lasse ich mich noch nach aussen routen, indem ich die IP des modems als gateway eingestellt habe.


    lg
    Geändert von Lin728 (19.08.17 um 08:18 Uhr)

  6. #6
    Registrierter Benutzer Avatar von klemens
    Registriert seit
    Nov 2002
    Ort
    Wien
    Beiträge
    2.061
    Du versuchst nicht zufällig von "innen" über die eigene Internetverbindung auf den Rechner zu kommen? - Das geht normalerweise nicht.
    Das muss jemand von außen machen.

    Normalerweise muss man dem Linuxrechner nichts weiter sagen
    .) sshd muss eingerichtet sein
    .) eine Firewall darf das nicht blocken

    -- Wie Du den Rechner selbst ins Internet bringst, geht über pptp und die diversen Howto's (wenn es wahr ist, dass Du nicht zufällig einen von den gerüchteweisen pppoe-Accounts von inode hast)

    (was war das noch für eine Distribution?)

  7. #7
    Registrierter Benutzer
    Registriert seit
    Sep 2001
    Beiträge
    725

    Hmm...

    Erstmal ein riesengroßes Danke für deine Geduld! Ich weiß wie nervend solche posts sind, noch dazu wos normalerweise meistens an blöden Kleinigkeiten liegt...
    Danke!

    Das muss jemand von außen machen.
    (wenn es wahr ist, dass Du nicht zufällig einen von den gerüchteweisen pppoe-Accounts von inode hast)
    Jaja, sowieso von draußen. Meine Distro ist FC3.
    Nöö, ist ein Aon Account

    Ein Problem welches mir aufgefallen ist und irgendwie total komisch vorkommt:
    Das Modem kennt 2ip-adressen (welche nicht von mir besetz sind), eine hat einen Ping von 25ms und die andere von 0.25ms.
    Von aussen kann ich nur die mit 25ms pingen, bei der 0.25ms-adresse hab ich 100% packet loss. (so wies aussieht ist die eine der tunnel-server und die andere ist mein modem lokal - wahrscheinlich kommt nicht einmal das ICMP-zeugs durch).

    Was ich noch nicht ganz verstehe::
    Ich kann mir den Traffic per Gateway rausrouten lassen - aber wie krieg ich meinen Traffic per NAT raus? Ich muss doch dem Linux-Rechner irgendwie sagen, wohin er den Traffic weiterleiten soll - sonst weiß das doch nur das Modem und der Linux-Rechner kennt nur die modem-ip und ist beleidigt.
    Reinrouten geht anscheinend nicht - da regt sich das modem aus...

    ach ja, mit pptp hab ich am Linux-Rechner überhaupt nix mehr zu tun. Das modem wählt sich automatisch ein, sobald es Strom hat (und Ethernet eingestreckt ist) - ohne dass der Linux-Rechner irgendetwas damit zu tun hätte. Das einzige was ich bis jetzt gemacht habe, ist die default-gw auf das modem zu setzen.
    IP und nameserver bekommt der Linux-Rechner automatisch über den eingebauten dhcp-server im modem.


    danke für deine geduld und hilfe!
    lg
    Geändert von Lin728 (19.08.17 um 08:18 Uhr)

  8. #8
    Registrierter Benutzer Avatar von klemens
    Registriert seit
    Nov 2002
    Ort
    Wien
    Beiträge
    2.061
    Das Modem kennt 2ip-adressen (welche nicht von mir besetz sind), eine hat einen Ping von 25ms und die andere von 0.25ms.
    Ein Tunnel hat einmal 2 Adressen ;-) - wird die vis-a-vis-Stelle sein.
    (ich hab 172.xxx..... in Erinnerung als Gegenstelle). Diese wird von außen nicht pingbar sein.
    Wie gesagt, ich habe das Modem nicht, und kann jetzt auch nicht genau abschätzen, was sich tut - läuft bei mir etwas anders (ist ein Hardwarerouter an dem das alte Modem angeschlossen ist)

    aber wie krieg ich meinen Traffic per NAT raus?
    Das macht das Modem.

    Ich muss doch dem Linux-Rechner irgendwie sagen, wohin er den Traffic weiterleiten soll
    Das ist der default gatway.

    Mit route -n wirst einen Eintrag haben, in etwa:
    Code:
    0.0.0.0         10.0.0.138   0.0.0.0         UG    1      0        0 eth0
    Tipp:
    Stell einmal fest, ob das Modem wirklich Portforwarding kann. Das kann ich nicht sagen und sonst hat sich keiner gemeldet.
    Frag vielleicht bei adsl.at nach - da wird sich sicher wer auskennen.

    Dann müsstest feststellen, ob die sshd-Konfiguration/lokale Firewall da nicht dazwischen funkt.
    sshd wird in /etc/ssh/sshd_conf konfiguriert
    Firewall kannst leicht mit
    iptables -L
    nachschauen - wenn sich da viel tut, dann abschalten!


    (Nerven tust eigentlich nicht, aber ich werd jetzt ein Zeitl vom PC weg sein und glaub auch, dass ich zu wenig Ahnung von FC3 und dem Modem habe)

  9. #9
    Registrierter Benutzer
    Registriert seit
    May 2004
    Beiträge
    1.567

    Post

    geht es um das Speedtouch?

    du kannst eine Konfigurationsdatei per telnet oder webinterface in das Ding laden,
    diese muß die NAT Einträge enthalten ...
    hab einfach meinem Provider gesagt, daß ich das Configfile brauche,
    das die Einträge fürs Routing enthält - auf denen ihrer CD war nur das ohne NAT Einträge drauf - sie habens dann nach langem Fragen wozu ichs brauche rausgerückt und das hab ich mir draufgeschmissen - war zu faul es selbst zu schreiben

  10. #10
    Registrierter Benutzer
    Registriert seit
    May 2004
    Beiträge
    1.567

    Angry

    *argh* jetzt fällt mir erst auf, daß ich dieses Configfile auf irgeneinem Backupband habe und überhaupt nicht mehr am PC. Das müßte nämlich sogar mit allen Providern funken - hab es nicht ausgetauscht als ich den provider wechselte

    na ja ich kann dir mal die Tabelle geben:
    Code:
    IP route table  	
    	
    	
    Destination 		Source 		Gateway 		Intf
    	212.152.234.1/32 		81.189.71.229/32 		81.189.71.229 		DIALUP_PPP1
    	10.0.0.0/24 		10.0.0.138/32 		10.0.0.138 		eth0
    	default 		10.0.0.140/24 		81.189.71.229 		DIALUP_PPP1
    	212.152.234.1/32 		any 		81.189.71.229 		DIALUP_PPP1
    	81.189.71.229/32 		any 		81.189.71.229 		DIALUP_PPP1
    	10.0.0.138/32 		any 		10.0.0.138 		eth0
    	127.0.0.1/32 		any 		127.0.0.1 		loop
    	224.0.0.0/4 		any 		10.0.0.138* 		eth0
    	default 		any 		10.0.0.138* 		eth0
    10.0.0.138 Speedtouch
    10.0.0.140 mein PC

  11. #11
    Registrierter Benutzer
    Registriert seit
    Sep 2001
    Beiträge
    725

    Danke!!

    Danke! - Werd ich ausprobieren sobald ich zu Hause bin.

    Dein tipp mitadsl.at war auch wirklich gut - die haben mir dort einen Link gezeigt mit einem Config-File womit das Ding eigentlich NAT können sollte - werd ich auch geich ausprobieren *g*.

    lg
    Geändert von Lin728 (19.08.17 um 08:19 Uhr)

Ähnliche Themen

  1. [kernel 2.6.7 und suse9.0] Problem mit hotplug/udev? Kann booten, aber ....
    Von carnil im Forum Kompilieren von Kernel und Sourcen
    Antworten: 14
    Letzter Beitrag: 29.03.06, 09:33
  2. Allgemeine Frage, aber wichtig fuer mich!
    Von PCMCIA im Forum Linux Allgemein
    Antworten: 22
    Letzter Beitrag: 24.01.06, 20:21
  3. Benutzerzahlen
    Von HangLoose im Forum Meldungen und Mitglieder
    Antworten: 44
    Letzter Beitrag: 23.08.03, 05:03
  4. FreeBSD+isdn Router, krieg keine Verbindung zu stande
    Von ZeiTw1Nd3r im Forum Alternativen zu Linux
    Antworten: 2
    Letzter Beitrag: 19.07.02, 10:03
  5. Probleme mit xcdroast
    Von Dirk.M im Forum Linux Allgemein
    Antworten: 9
    Letzter Beitrag: 17.06.02, 16:22

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •