Newbiealert die Zweite - Internet Gateway erstellen

[DaJ23]

Also folgendes Liebe Leute :rolleyes:

Im Vorfeld möchte ich mich noch mal für die damalige Hilfe mit der Proxy Einrichtung bedanken,
das hat soweit alles gut geklappt (mal abgesehen davon das ich unmenschlich viel Zeit dafür gebraucht habe) :) :cool:
nur gingen dann die Hälfte der Windows Internet Programme nicht mehr (Trillian etc.)
Da ich für einen (bzw. bald wahrscheinlich 2) Rechner in einem Netzwerk eh keinen Proxy geschweige denn
Cache brauche, dachte ich, weil es soviel Spaß gemacht hat, setz ich das alles noch mal auf (tschuldigt meinen Sarkasmus)
nur dieses mal als Gateway/Router. Daten bleiben die gleichen wie in meinem Vorherigen Thread... also fli4l etc. laufen
nicht, bzw. müsste ich zuviel daran rumkonfigurieren bis ich die Hardware zum laufen bekomme.
Also weiterhin SuSE 8.1 Prof.




YaST @ Helios (ui-ncurses-2.6.18)
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq qqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
xlqqqqqqqqqqqqqqqqqqqqk Network cards configuration x
xx Network card setupx lNetwork cards to configureqqqqqqqqqqqqqqqqqqqqqk x
xx x x lAvailable are:qqqqqqqqqqqqqqqqqqqqqqqqqqqqqk x x
xxConfigure your x x xOther (not detected) x x x
xxnetwork card here. x x x x x x
xx Adding a network x x x x x x
xxcard: x x x x x x
xxChoose a network x x x x x x
xxcard from the list x x x x x x
xxof detected network x x x x x x
xxcards. If your x x x x x x
xxnetwork card was notx x x x x x
xxautodetected, selectx x x x x x
xxOther (not detected)x x x x x x
xxthen press Configurex x x x x x
xx. x x x x x x
xx Editing or x x x x x x
xxdeleting: x x x x x x
xxIf you press Edit, x x x x x x
xxan additional dialogx x x x x x
xxin which to change x x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj x x
xxthe configuration x x [Configure...] x x
xxopens. x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj x
xx x lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqk x
xx x xAlready configured devices: x x
xx x x * Realtek RTL-8029(AS) x x
xx x x Configured as eth0 with address x x
xx x x 192.168.172.1 x x
xx x x * 3Com 3C905C-TX Fast Etherlink for PC x x
xx x x Management NIC x x
xx x x Configured as eth1 with address x x
xx x x 192.168.171.1 x x
xx x x x x
xx x x x x
xx x x x x
xx x x x x
xx x x x x
xx x x x x
xx x x x x
xx x x x x
xx x x x x
xx x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj x
xx x [Change...] x
xx x x
xmqqqqqqqqqqqqqqqqqqqqj [ Back ] [Abort] [Finish] x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq qqqqqqqqqqqqqqqqqqqqqqqqqqqqqj




YaST @ Helios (ui-ncurses-2.6.18)
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq qqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
xlqqqqqqqqqqqqqqqqqqqqk Network address setup x
xx Configure your IP x x
xxaddress. x x
xx You can select x x
xxdynamic address x x
xxassignment, if you x x
xxhave a DHCP server x x
xxrunning on your x x
xxlocal network. x x
xx Also select this x x
xxif you do not have ax x
xxstatic IP address x x
xxassigned by the x x
xxsystem administratorx Network device eth0 x
xxor your cable or DSLx x
xxprovider. x lChoose the setup methodqqqqqqqqqqqqqqqqqk x
xx Network addresses x x x x
xxwill then be x x ( ) Automatic address setup (via DHCP) x x
xxobtained x x x x
xxautomatically from x x (x) Static address setup x x
xxthe server. x x IP Address Subnet mask x x
xx Clicking Next x x 192.168.172.1aaaa 255.255.255.0aaaaa x x
xxcompletes the x x x x
xxconfiguration. x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj x
xx Otherwise, networkx x
xxaddresses must be x lDetailed settingsqqqqqqqqqqqqqqqqqqqqqqqk x
xxassigned manually. x x x x
xx Enter the IP x x [Host name and name server] x x
xxaddress (e.g., x x [ Routing ] x x
xx192.168.100.99) for x x x x
xxyour computer, the x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj x
xxnetwork mask x x
xx(usually x x
xx255.255.255.0), and,x x
xxoptionally, the x x
xxdefault gateway IP x x
xxaddress. x x
xx Contact your x x
xxnetwork x x
xxadministrator for x x
xxmore information x x
xxabout the network x x
xxconfiguration. x x
xx x x
xmqqqqqqqqqqqqqqqqqqqqj [Back] [Abort] [Next] x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq qqqqqqqqqqqqqqqqqqqqqqqqqqqqqj




YaST @ Helios (ui-ncurses-2.6.18)
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq qqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
xlqqqqqqqqqqqqqqqqqqqqk Network address setup x
xx Configure your IP x x
xxaddress. x x
xx You can select x x
xxdynamic address x x
xxassignment, if you x x
xxhave a DHCP server x x
xxrunning on your x x
xxlocal network. x x
xx Also select this x x
xxif you do not have ax x
xxstatic IP address x x
xxassigned by the x x
xxsystem administratorx Network device eth1 x
xxor your cable or DSLx x
xxprovider. x lChoose the setup methodqqqqqqqqqqqqqqqqqk x
xx Network addresses x x x x
xxwill then be x x ( ) Automatic address setup (via DHCP) x x
xxobtained x x x x
xxautomatically from x x (x) Static address setup x x
xxthe server. x x IP Address Subnet mask x x
xx Clicking Next x x 192.168.171.1aaaa 255.255.255.0aaaaa x x
xxcompletes the x x x x
xxconfiguration. x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj x
xx Otherwise, networkx x
xxaddresses must be x lDetailed settingsqqqqqqqqqqqqqqqqqqqqqqqk x
xxassigned manually. x x x x
xx Enter the IP x x [Host name and name server] x x
xxaddress (e.g., x x [ Routing ] x x
xx192.168.100.99) for x x x x
xxyour computer, the x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj x
xxnetwork mask x x
xx(usually x x
xx255.255.255.0), and,x x
xxoptionally, the x x
xxdefault gateway IP x x
xxaddress. x x
xx Contact your x x
xxnetwork x x
xxadministrator for x x
xxmore information x x
xxabout the network x x
xxconfiguration. x x
xx x x
xmqqqqqqqqqqqqqqqqqqqqj [Back] [Abort] [Next] x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq qqqqqqqqqqqqqqqqqqqqqqqqqqqqqj




YaST @ Helios (ui-ncurses-2.6.18)
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq qqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
xlqqqqqqqqqqqqqqqqqqqqk Host name and name server configuration x
xx Insert the host w x
xxname and domain namex x
xxfor your computer. x x
xxName server list andx x
xxdomain search list x x
xxare optional. x x
xx A name server is ax x
xxcomputer that x x
xxtranslates host x x
xxnames into IP x x
xxaddresses. This x x
xxvalue must be x x
xxentered as an IP x x
xxaddress (e.g., x x
xx10.10.0.1), not as ax lHost name and domain nameqqqqqqqqqqqqqqqqqqqqqqqk x
xxhost name. x xHost name Domain name x x
xx Search domain is x xHeliosaaaaaaaaaaaaaaaaaGlobalNode.netaaaaaaaaaaax x
xxthe domain name x x[ ] Change host name via DHCP x x
xxwhere host name x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj x
xxsearching starts. x x
xxThe primary search x lName servers and domain search listqqqqqqqqqqqqqk x
xxdomain is usually x xName server 1 Domain search 1 x x
xxthe same as the x x217.237.149.161aaaaaaaaGlobalNode.netaaaaaaaaaaax x
xxdomain name of your x xName server 2 Domain search 2 x x
xxcomputer (e.g., x x194.25.2.129aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaax x
xxsuse.de). There may x xName server 3 Domain search 3 x x
xxbe additional searchx xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaax x
xxdomains (e.g., x x[ ] Update name servers and search list via DHCPx x
xxsuse.com). x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj x
xx If you are using x x
xxDHCP to get an IP x x
xxaddress, check x x
xxwhether to get a x x
xxhost name via DHCP x x
xxor to set name x x
xxservers and searchedx x
xxdomains via DHCP. v x
xx If you plan to usex x
xxa dial-up Internet x x
xxconnection and have x x
xxset up your x x
xxconnection to use x x
xxdynamic DNS x x
xmqqqqqqqqqqqqqqqqqqqqj [Back] [Abort] [Next] x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq qqqqqqqqqqqqqqqqqqqqqqqqqqqqqj




YaST @ Helios (ui-ncurses-2.6.18)
lqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq qqqqqqqqqqqqqqqqqqqqqqqqqqqqqk
xlqqqqqqqqqqqqqqqqqqqqk Routing configuration x
xx The routing can bex x
xxset up in this x x
xxdialog. The default x x
xxroute matches every x x
xxpossible x x
xxdestination, but x x
xxpoorly. If any otherx x
xxentry exists that x x
xxmatches the requiredx x
xxaddress, it will be x Default gateway x
xxused instead of the x aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaav x
xxdefault route. The x x
xxidea of the default x lRouting tableqqqqqqqqqqqqqqqqqqqqqqqqqqqqk x
xxroute is simply to x x[ ] Expert configuration x x
xxenable you to say x xlqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqkx x
xx"and everything elsex xxDestinationxDummy or GatewayxNetmask xx x
xxshould go here". x xxeth1 xnet x192.168.17xx x
xx Enable the IP x xx xx x
xxforwarding if the x xx xx x
xxsystem is a router. x xx xx x
xx x xx xx x
xx x xx xx x
xx x xx xx x
xx x xx xx x
xx x xx xx x
xx x xx xx x
xx x xx xx x
xx x xmtqqqqqqqqqqqqqqqqqqqqqqqqqqquqqqqqqqqqqjx x
xx x x [Add][Edit][Delete] x x
xx x mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqj x
xx x x
xx x [x] Enable IP forwarding x
xx x x
xx x x
xx x x
xx x x
xx x x
xx x x
xx x x
xx x x
xx x x
xx x x
xx x x
xmqqqqqqqqqqqqqqqqqqqqj [Back] [Abort] [Next] x
mqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqq qqqqqqqqqqqqqqqqqqqqqqqqqqqqqj



eth1 net 192.168.171.0 netmask 255.255.255.0 gw 192.168.172.1

Nun aus meiner Vorherigen Arbeit habe ich ja relativ schnell gelernt und der Internet Zugang
vom Gateway RECHNER2 klappt soweit auch tadellos:




Helios:~ # ping www.google.de
PING www.google.akadns.net (66.102.9.104) from 217.81.47.213 : 56(84) bytes of data.
64 bytes from 66.102.9.104: icmp_seq=1 ttl=245 time=93.6 ms
64 bytes from 66.102.9.104: icmp_seq=2 ttl=245 time=92.7 ms
64 bytes from 66.102.9.104: icmp_seq=3 ttl=245 time=92.3 ms
64 bytes from 66.102.9.104: icmp_seq=4 ttl=245 time=92.0 ms
64 bytes from 66.102.9.104: icmp_seq=5 ttl=245 time=92.6 ms

--- www.google.akadns.net ping statistics ---
5 packets transmitted, 5 received, 0% loss, time 4048ms
rtt min/avg/max/mdev = 92.005/92.680/93.662/0.615 ms

Nur habe ich nun ein kleines Netzwerkproblem.... wo ich mal wieder nicht weiterkomme...
außerdem weiß ich nicht ob das daran schuld ist das mein RECHNER1 mit der
Standardgateway Eintragung 192.168.171.1 deshalb nicht ins Netz kommt.




Ping wird ausgeführt für 192.168.171.1 mit 32 Bytes Daten:

Antwort von 192.168.171.1: Bytes=32 Zeit=16ms TTL=64
Antwort von 192.168.171.1: Bytes=32 Zeit<10ms TTL=64
Antwort von 192.168.171.1: Bytes=32 Zeit<10ms TTL=64
Antwort von 192.168.171.1: Bytes=32 Zeit<10ms TTL=64




Helios:~ # ping 192.168.171.2
PING 192.168.171.2 (192.168.171.2) from 192.168.171.1 : 56(84) bytes of data.

--- 192.168.171.2 ping statistics ---
44 packets transmitted, 0 received, 100% loss, time 43016ms

Ich kann an meiner Routing Table bisher auch nichts finden was daran falsch sein könnte



Helios:~ # route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
217.5.98.57 * 255.255.255.255 UH 0 0 0 ppp0
192.168.171.0 * 255.255.255.0 U 0 0 0 eth1
192.168.172.0 * 255.255.255.0 U 0 0 0 eth0
default 217.5.98.57 0.0.0.0 UG 0 0 0 ppp0

Das einzige was etwas komisch ist, ist das Netstat?!



Helios:~ # netstat in
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 192.168.171.1:ssh 192.168.171.2:1046 ESTABLISHED
Active UNIX domain sockets (w/o servers)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ] DGRAM 881 /var/lib/dhcp/dev/log
unix 9 [ ] DGRAM 879 /dev/log
unix 2 [ ] DGRAM 7301
unix 2 [ ] DGRAM 6910
unix 2 [ ] DGRAM 2439
unix 2 [ ] DGRAM 2301
unix 2 [ ] DGRAM 2300
unix 3 [ ] STREAM CONNECTED 2165
unix 3 [ ] STREAM CONNECTED 2164
unix 3 [ ] STREAM CONNECTED 2161
unix 3 [ ] STREAM CONNECTED 2160
unix 3 [ ] STREAM CONNECTED 2157
unix 3 [ ] STREAM CONNECTED 2156
unix 3 [ ] STREAM CONNECTED 2153
unix 3 [ ] STREAM CONNECTED 2152
unix 3 [ ] STREAM CONNECTED 2149
unix 3 [ ] STREAM CONNECTED 2148
unix 3 [ ] STREAM CONNECTED 2145
unix 3 [ ] STREAM CONNECTED 2144
unix 3 [ ] STREAM CONNECTED 2141
unix 3 [ ] STREAM CONNECTED 2140
unix 3 [ ] STREAM CONNECTED 2137
unix 3 [ ] STREAM CONNECTED 2136
unix 3 [ ] STREAM CONNECTED 2133
unix 3 [ ] STREAM CONNECTED 2132
unix 3 [ ] STREAM CONNECTED 2128
unix 3 [ ] STREAM CONNECTED 2127
unix 3 [ ] STREAM CONNECTED 2123
unix 3 [ ] STREAM CONNECTED 2122
unix 3 [ ] STREAM CONNECTED 2119
unix 3 [ ] STREAM CONNECTED 2118
unix 3 [ ] STREAM CONNECTED 2115
unix 3 [ ] STREAM CONNECTED 2114
unix 3 [ ] STREAM CONNECTED 2111
unix 3 [ ] STREAM CONNECTED 2110
unix 3 [ ] STREAM CONNECTED 2107
unix 3 [ ] STREAM CONNECTED 2106
unix 3 [ ] STREAM CONNECTED 2103
unix 3 [ ] STREAM CONNECTED 2102
unix 3 [ ] STREAM CONNECTED 2098
unix 3 [ ] STREAM CONNECTED 2097
unix 3 [ ] STREAM CONNECTED 2095
unix 3 [ ] STREAM CONNECTED 2094
unix 3 [ ] STREAM CONNECTED 2091
unix 3 [ ] STREAM CONNECTED 2090
unix 3 [ ] STREAM CONNECTED 2088
unix 3 [ ] STREAM CONNECTED 2087
unix 2 [ ] DGRAM 1886
unix 2 [ ] DGRAM 1068

Ich bin hier langsam wirklich am verzweifeln (Wie viele Monate versuch ich das Ding jetzt
zum laufen zu kriegen?) Und wenn Ichs Geld hätte würde ich den Mist auch einfach wegwerfen
und mir ein komplett neuen Server hier hinstellen wo gleich alles mit läuft.... aber es
geht ja einfach nicht :(

Also bitte, bitte.... wer sich mit der Konfiguration von Gateways, Routern, IPTables oder
anderweitig Netzwerkerfahrungen hat, der melde Sich bitte...

*sich schon fast nen Strick nimmt* :ugly:

[geronet]

192.168.171.0 * 255.255.255.0 U 0 0 0 eth1 192.168.172.0 * 255.255.255.0 U 0 0 0 eth0

Ist denn eth1 wirklich die Netzwerkkarte die zum Win2000-Rechner geht?
Was sagt
iptables -vL
iptables -t nat -vL
ifconfig
auf dem Router?

[DaJ23]

Vielen Dank erstmal wieder für die Meldung geronet, das es sich bei eth1 um die Netzwerkkarte handelt bin ich mir auch ganz sicher. Da ich es vorgestern Nacht noch hinbekommen habe das Rechner, Netzwerk und Internet, dank Eurer Hilfreichen Chatkomune liefen. Das erstemal das ich wieder im Internet bin ist aber erst leider Heute wieder möglich da, als ich am Samstag versuchte den nun endlich fertigen Gateway in dem Schrank einzubauen irgendwas schiefgelaufen sein muss. Dazu komm ich aber nochmal gleich, einfach nochmal zur Dokumentation und für Leute die Vielleicht später auch mal ähnliche Probleme haben, nun nochmal folgende Punkte.

1. Auf meinem Windows Client lief noch eine Software-Firewall (SyGate PE) und deshalb war das erreichen über den Ping nicht möglich.
2. Danach konnten nach etlichen Versuchen wenigstens Internetaddressen direkt mit den IPs vom Client her angesprochen werden.
(Auf dem Server: ping www.google.de -> IP übernommen und
auf dem Client direkt die IP angepingt... lief)
Also hatte ich nur noch ein Problem mit der DNS Namensauflösung, das Problem habe ich zur Zeit nur temporär gelöst indem ich auf dem Client direkt als DNS Server die Standard IPs der Telekom eingetragen hatte. Danach lief wirklich alles Problemlos (IRC, www, eMail, Trillian). Später hab ich dann vor DNSMASQ oder einen DNS Server auf dem Server zu installieren. Soweit kam ich aber leider jetzt nicht.

Nachdem ich den Server versucht habe in einen Schrank einzuschieben, muss wohl irgendwas schief gelaufen sein. Das komische ist.... Ich habe heute getestet, die Kabel habe ich nicht abgeknickt, die konnte Ich jetzt hier auf der Arbeit normal testen und Sie funktionierten. Vom Server aus konnte ich auch fast ohne Probleme (hat komischerweise nur etwas länger gedauert als vor dem Einbau) eine Internet Verbindung aufbauen. Nur ich konnte nichtmehr zwischen Gateway und Client pingen und vom Client (wieder alles umgestöpselt) auch keine Internet Verbindung aufbauen. Nun hab ich angst das irgendwie die Netzwerkkarte von meinem Clientrechner kaputt ist, ich habe an der Karte ja ansonsten nichts geändert und der Rechner lief wärend der ganzen Umbau aktion sogar noch. Ich werde heute Nachmittag das einmal mit einer Ersatzkarte testen nur Frag ich schonmal vorab ob jemand eine Idee hat woran das sonst noch liegen kann das das jetzt plötzlich nichtmehr läuft?! (Zuwenig Power im Netz (Strom?) oder Probleme bei Verbindungen von On-Board Realtek Karten (Client) mit 3Com Karten (Gateway) bekannt? (beide 100 MBit))

Find ich super das es Euch gibt Leute :cool:
(Solangsam machts auch Spaß was mit Linux zu lernen :wink:)

[DaJ23]

Ist mir fast peinlich das zuzugeben, andererseits kann ich auch nichts dafür, aber das das Netz nicht lief lag an der wie im vorherigen Post schon erwähnten Firewall die noch auf dem Client-PC installiert war... komisch fand ich nur das angezeigt wurde das Sie deaktiviert sei (Ist als Windows-Dienst eingetragen). Hab sie einfach Spaßeshalber einmal gestartet, wärenddessen im Hintergrund gepingt und dann wieder beendet und voilà... da war die Connection... Jetzt werd ich mich erstmal die Tage (ENDLICH!!!!!!!! :) :) :)) mal in die DNS Verwaltung von Linux einarbeiten.... Nun kann ichs auch mal etwas gelassener Angehen wenn das wenigstens schon läuft.

Wenn Ich hier als Newbee übrigens irgendwem auf den Nerv geh weil ich mich so bescheurt anstell oder so, dann sagt mir das mal bitte... Ich weiss mir ja auch nicht zu helfen, sollte jetzt auch keine Klage sein, nur weil mir ansonsten bisher kaum jemand helfen konnte (wollte :confused: ) oder ist das nur rein Subjektiv?

mfg DaJ23 :rolleyes: