Skocz do zawartości

Witaj!

Zaloguj lub Zarejestruj się aby uzyskać pełny dostęp do forum.

Zdjęcie
- - - - -

Dostęp do routera


  • Zaloguj się, aby dodać odpowiedź
14 odpowiedzi w tym temacie

#1 szychlunwks

szychlunwks
  • 6 postów

Napisano 14 stycznia 2011 - 21:20

Witam, chciałbym dostać się do ustawień routera (d-link dl-524), aby "otworzyć" pewne porty. Standardowo wystaczy wpisać w adres przeglądarki 192.168.0.1 i powinny ukazać się ustawienia routera, tak to przynajmiej rozumiem. Czy na macbooku jest inny sposób, żeby tam się dostać ? z góry dziekuję za pomoc

#2 kubaamm

kubaamm
  • 252 postów
  • SkądPL|USA

Napisano 14 stycznia 2011 - 21:21

musisz wpisac ip routera(bramy) przewaznie jest to: 192.168.0.1 lub 192.168.2.1 <

#3 szychlunwks

szychlunwks
  • 6 postów

Napisano 14 stycznia 2011 - 21:27

właśnie to robię, tzn wpisuję adres ip routera. niby się ładuje a po chwili kmunikat:
BŁĄD

Żądany URL nie może zostać sprowadzony

Podczas sprowadzania URL-a: [url]http://192.168.0.1/[/url]

wystąpił następujący błąd:

Nie można zrealizować połączenia
System zwrócił następującą wartość:
(101) Network is unreachable
Serwer źródłowy lub sieć mogą być nieczynne. Spróbuj ponowić żądanie później.
Generated Fri, 14 Jan 2011 20:24:39 GMT by px02.telsten.com (squid)

#4 kubaamm

kubaamm
  • 252 postów
  • SkądPL|USA

Napisano 14 stycznia 2011 - 21:31

właśnie to robię, tzn wpisuję adres ip routera. niby się ładuje a po chwili kmunikat:
BŁĄD

Żądany URL nie może zostać sprowadzony

Podczas sprowadzania URL-a: http://192.168.0.1/

wystąpił następujący błąd:

Nie można zrealizować połączenia
System zwrócił następującą wartość:
(101) Network is unreachable
Serwer źródłowy lub sieć mogą być nieczynne. Spróbuj ponowić żądanie później.
Generated Fri, 14 Jan 2011 20:24:39 GMT by px02.telsten.com (squid)


to dziwne, sprobuj wpisac : 192.168.1.1 badz 192.168.2.1 , ten blad co ci sie wyswietla przewaznie ejst to blad niezaktualizowanego routera

#5 szychlunwks

szychlunwks
  • 6 postów

Napisano 14 stycznia 2011 - 21:39

nie działa ani jedno ani drugie : ( zauktializować routera nie mogę gdyż do pobrania jest tylko plik .exe

#6 kubaamm

kubaamm
  • 252 postów
  • SkądPL|USA

Napisano 14 stycznia 2011 - 21:45

a sproboj palaczyc sie przez wan(kabel)

#7 ex3v

ex3v

  • 1 884 postów
  • SkądWarszawa

Napisano 14 stycznia 2011 - 21:52

Ech... Wejdź w ustawienia sieciowe w preferencjach systemowych, wybierz wifi. Po prawej pokażą sie aktualne parametry połączenia, w tym brama domyslna, czyli adres routera.

#8 szychlunwks

szychlunwks
  • 6 postów

Napisano 15 stycznia 2011 - 00:09

w ustawieniach sieciowych widnieje adres routera, który już próbowałem

[url]http://img98.imageshack.us/i/zrzutekranu20110115godz.png/[/url]

[url]http://img98.imageshack.us/i/zrzutekranu20110115godz.png/[/url]

#9 Roberto

Roberto
  • 13 752 postów
  • SkądWrocław

Napisano 15 stycznia 2011 - 00:42

a na pewno masz to włączone w routerze, że możesz go konfigurować przez wi-fi? AFAIK da się coś takiego ustawić, więc może tak jest domyślnie? po kablu próbowałeś?

#10 szychlunwks

szychlunwks
  • 6 postów

Napisano 15 stycznia 2011 - 01:07

wiem, że można bo kiedyś ten właśnie router był konfigurowany normalnie z kompa
po kablu próbowałem jednak wtedy nie mam internetu...
internet mam z sieci kablowej, która łączy się przez proxy może to coś pomoże ?


skorzystałem z tego:
[url]http://myapple.pl/internet-i-sieci/165894-narzedzie-do-diagnozowania-problemow-z-siecia_.html[/url]

i oto co uzyskałem

Summary of Noteworthy Events –
Major Abnormalities
You are listed on a significant DNS blacklist
A detected in-network HTTP cache incorrectly caches information
Minor Aberrations
Certain TCP protocols are blocked in outbound traffic
An HTTP proxy was detected based on address difference
An HTTP proxy was detected based on added or changed HTTP traffic
The detected HTTP proxy blocks malformed HTTP requests
Content filters or compression proxies appear to be present in the network
A detected in-network HTTP cache exists in your network
Your computer's clock is substantially fast
Address-based Tests –
NAT detection (?): NAT Detected
Your global IP address is 212.122.223.73 while your local one is 192.168.0.127. You are behind a NAT. Your local address is in unroutable address space.
Your machine numbers TCP source ports sequentially. The following graph shows connection attempts on the X-axis and their corresponding source ports used by your computer on the Y-axis.

The NAT or some other process renumbers TCP ports. The following graph shows connection attempts on the X-axis and their corresponding source ports on the Y-axis as seen by our server.

Local Network Interfaces (?): OK
Your computer reports the following network interfaces, with the following IP addresses for each one:
en1: (an ethernet interface)
192.168.0.127 (a private IPv4 address)
fe80::226:bbff:fe1a:5547 [macbookpro-64b9e8cbdf20.local] (a link-local IPv6 address)
lo0: (a local loopback interface)
127.0.0.1 (an IPv4 loopback address)
fe80::1 (a link-local IPv6 address)
::1 (an IPv6 loopback address)
DNS-based host information (?): Warning
You are not a Tor exit node for HTTP traffic.
You are listed on the following Spamhaus blacklists: XBL
The SORBS DUHL believes you are using a statically assigned IP address.
Reachability Tests –
TCP connectivity (?): Note
Direct TCP access to remote FTP servers (port 21) is allowed.
Direct TCP access to remote SSH servers (port 22) is allowed.
Direct TCP access to remote SMTP servers (port 25) is allowed.
Direct TCP access to remote DNS servers (port 53) is allowed.
Direct TCP access to remote HTTP servers (port 80) is allowed.
Direct TCP access to remote POP3 servers (port 110) is allowed.
Direct TCP access to remote RPC servers (port 135) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote NetBIOS servers (port 139) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote IMAP servers (port 143) is allowed.
Direct TCP access to remote SNMP servers (port 161) is allowed.
Direct TCP access to remote HTTPS servers (port 443) is allowed.
Direct TCP access to remote SMB servers (port 445) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.
Direct TCP access to remote secure IMAP servers (port 585) is allowed.
Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.
Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.
Direct TCP access to remote POP/SSL servers (port 995) is allowed.
Direct TCP access to remote OpenVPN servers (port 1194) is allowed.
Direct TCP access to remote PPTP Control servers (port 1723) is allowed.
Direct TCP access to remote SIP servers (port 5060) is allowed.
Direct TCP access to remote BitTorrent servers (port 6881) is allowed.
Direct TCP access to remote TOR servers (port 9001) is allowed.
UDP connectivity (?): OK
Basic UDP access is available.
The applet was able to send fragmented UDP traffic.
The applet was able to receive fragmented UDP traffic.
Direct UDP access to remote DNS servers (port 53) is allowed.
Direct UDP access to remote NTP servers (port 123) is allowed.
Direct UDP access to remote OpenVPN servers (port 1194) is allowed.
Direct UDP access to remote MSSQL servers (port 1434) is allowed.
Traceroute (?): OK
It takes 18 network hops for traffic to pass from our server to your system, as shown below. For each hop, the time it takes to traverse it is shown in parentheses.
10.209.112.3 (0 ms)
ec2-75-101-160-174.compute-1.amazonaws.com (0 ms)
216.182.232.64 (0 ms)
*
*
*
xe-9-0-0.edge2.Washington1.Level3.net (2 ms)
vlan80.csw3.Washington1.Level3.net (1 ms)
ae-72-72.ebr2.Washington1.Level3.net (1 ms)
ae-41-41.ebr2.Frankfurt1.Level3.net (91 ms)
ae-47-47.ebr1.Dusseldorf1.Level3.net (94 ms)
ae-1-100.ebr2.Dusseldorf1.Level3.net (92 ms)
ae-3-3.ebr2.Berlin1.Level3.net (104 ms)
ae-22-52.car2.Berlin1.Level3.net (104 ms)
212.162.11.26 (112 ms)
z-poznan-gw1-pcws.Bydgoszcz-COM.rtr.pionier.gov.pl (117 ms)
89.191.159.150 (118 ms)
212.122.223.73 (117 ms)
Path MTU (?): OK
The path between your network and our system supports an MTU of at least 1500 bytes, and the path between our system and your network has an MTU of 1500 bytes.
Network Access Link Properties +
Network latency measurements (?): Latency: 120ms Loss: 0.0%
TCP connection setup latency (?): 120ms
Network background health measurement (?): no transient outages
Network bandwidth measurements (?): Upload 6.8 Mbit/sec, Download 12 Mbit/sec
Network buffer measurements (?): Uplink 160 ms, Downlink 85 ms
HTTP Tests –
Address-based HTTP proxy detection (?): Warning
Your browser's HTTP connections come from 212.122.223.79 while non-browser HTTP connections originate from 212.122.223.73, indicating that your web browser has a proxy manually configured.
Header-based HTTP proxy detection (?): Warning
Changes to headers or contents sent between the applet and our HTTP server show the presence of an otherwise unadvertised HTTP proxy.
The following headers had their capitalization modified by the proxy:
Content-Length: 1279
Connection: close
Content-Type: text/html; charset=ISO-8859-2
The following headers were added by the proxy to HTTP responses:
Via: [1.1 px02.telsten.com:3128 (squid)]
X-Cache: [MISS from px02.telsten.com]
Proxy-Connection: [keep-alive]
Vary: accept-language
Accept-Ranges: bytes
Content-Language: pl
The detected proxy reordered the headers sent from the server.
The detected HTTP proxy changed images that were sent from our server.
The detected HTTP proxy changed either the headers the applet sent or the HTTP response from the server. We have captured the changes for further analysis.
The HTTP proxy removed the cookie from the connection.
HTTP proxy detection via malformed requests (?): Warning
Deliberately malformed HTTP requests do not arrive at our server. This suggests that the proxy we detected on your network path was either unable to parse or refused to forward the deliberately bad request.
Filetype-based filtering (?): Note
None of the test files were transmitted successfully.
HTTP caching behavior (?): Warning
We detected the presence of an in-network transparent HTTP cache that caches data which was directly requested by the applet.
Strongly uncacheable data was cached between you and our server, even when the data was requested directly and explicitly. This suggests that there is an HTTP cache in the network which examines and caches web traffic. Since this content was not supposed to be cached, the HTTP cache is probably operating incorrectly.
Weakly uncacheable data was cached between you and our server, even when the data was requested directly and explicitly. This suggests that there is an HTTP cache in the network which examines and caches web traffic. Since this content was not supposed to be cached, the HTTP cache is probably operating incorrectly.
Weakly cacheable data was cached between you and our server, even when the data was requested directly and explicitly. This suggests that there is an HTTP cache in the network which examines and caches web traffic.
Strongly cacheable data was not cached between you and our server when it was explicitly fetched.
JavaScript-based tests (?): OK
The applet was not run from within a frame.
Your web browser reports the following cookies for our web page:
netAlizEd = BaR (set by our server)
netalyzrStatus = running (set by our server)
Your web browser was unable to fetch an image using IPv6.
DNS Tests +
Restricted domain DNS lookup (?): OK
Unrestricted domain DNS lookup (?): OK
Direct DNS support (?): OK
Direct EDNS support (?): OK
DNS resolver address (?): OK
DNS resolver properties (?): Lookup latency 700ms
DNS glue policy (?): OK
DNS resolver port randomization (?): OK
DNS lookups of popular domains (?): OK
DNS external proxy (?): OK
DNS results wildcarding (?): OK
IPv6 Tests +
DNS support for IPv6 (?): OK
IPv6 Connectivity (?): No IPv6 Support
IPv6 TCP connectivity (?): Not Executed
IPv6 and Your Web Browser (?): No IPv6 Support
IPv6 Path MTU (?): Not Executed
IPv6 Traceroute (?): Not Executed
Host Properties –
System clock accuracy (?): Warning
Your computer's clock is 526 seconds fast.
Browser properties (?): OK
The following parameters are sent by your web browser to all web sites you visit:
User Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_6; pl-pl) AppleWebKit/533.19.4 (KHTML, like Gecko) Version/5.0.3 Safari/533.19.4
Accept: application/xml,application/xhtml+xml,text/html; q=0.9,text/plain; q=0.8,image/png,*/*; q=0.5
Accept Language: pl-pl
Accept Encoding: gzip, deflate
Accept Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Java identifies your operating system as Mac OS X.
Uploaded Data (?): OK
The following additional content was uploaded by the applet:
modified_Fedora-10-i686-Live.torrent
modified_eicar-standard-av-test-file.com
modified_netalyzr.exe
modified_netalyzr.mp3
raw_http_content
transcoded_image10
transcoded_image11
transcoded_image12
transcoded_image5
transcoded_image6
transcoded_image7
transcoded_image8
transcoded_image9

#11 Roberto

Roberto
  • 13 752 postów
  • SkądWrocław

Napisano 15 stycznia 2011 - 01:09

internet to naprawdę trochę niezależna sprawa od sieci domowej. próbowałeś po kablu i co? bo nie za bardzo rozumiem.

#12 ex3v

ex3v

  • 1 884 postów
  • SkądWarszawa

Napisano 15 stycznia 2011 - 10:33

A jak nie zadziała po kablu, to bierzemy dlugopis i resetujemy dziada, ile to jest ustawić router od nowa...

#13 ftpd

ftpd

    Nie.


  • 24 537 postów
  • Płeć:
  • SkądPoznań

Napisano 15 stycznia 2011 - 18:18

Nie zauważyliście, że on ma 'network is unreachable'? Pingasz w ogóle ten router?

#14 szychlunwks

szychlunwks
  • 6 postów

Napisano 17 stycznia 2011 - 14:01

Po kablu nie ma dostępu do internetu w ogóle Restart routera próbowałem, bez zmian a sens jest taki, że właśnie nie mogę go ustawić bo nie mogę wejść do ustawień na macbooku internet jest, na ipodzie jest tylko na drugim lapku już nie ma... widzi połączenie ale nie łączy

#15 Roberto

Roberto
  • 13 752 postów
  • SkądWrocław

Napisano 17 stycznia 2011 - 15:25

szychlunwks - aktualnie to walczysz raczej żeby utworzyć sobie sieć domową. więc pytanie czy po kablu możesz się połączyć z routerem, a nie z internetem. router to nie internet.




Użytkownicy przeglądający ten temat: 1

0 użytkowników, 1 gości, 0 anonimowych