Česta promena IP adrese sa Telekomovim ADSL-om...

Koristim Huawei HG510 koji sam dobio od Telekoma i ADSL 256/64 sa dinamičkom IP adresom. Kompjuter mi je povezan sa modemom preko LAN1, a modem nije u bridge modu, dakle sam uspostavlja konekciju. Problem je što mi se često menja WAN IP adresu, a ne resetujem modem ili nešto slično. Pod često mislim nekada svakih 5 minuta, nekada po 5 sati ostane ista, nekada se promeni svakih sat vremena i sl. Kada se IP promeni moram opet da se ulogujem sa MSN-om, Skype-om i sl. Naravno svaki download se prekine, ako server ne dozvoljava da nastavim moram iz početka. Da li Telekom tako često menja IP adrese i drugim korisnicima i da nije možda problem kod mene? Inače slabljenje (Attenuation) mi je 30.5dB za downstream, a 11.6 za upstream. Da nije možda to razlog za nestabilnu vezu koji može da dovede do pucanja veze i ponovnog povezivanja odnosno dodele druge IP adrese?

Taj attenuation mi se ne cini preterano velikim. Jeste velik (meni je trenutno up/down - 8/2) ali modem bi trebalo da dobro drzi vezu. Da li se desava da modem gubi vezu (mozes primetiti po signalnim lampicama da ponovo radi konektovanje)? Najlakse je da udjes u setup modema kad se to desi jer nema sanse da se veza uspostavi za sekundu dve i da vidis u kojoj fazi procesa logovanja je modem.

Kad se to desi kod mene samo lampica za internet prestane da svetli ostale(power,lan,ADSL) svetle.
Sta utice na visok attenuation,kucna ili telekomova instalacija?

Nisam primetio da modem ponovo radi konektovanje ali ću probati da ga ulovim dok bude menjao IP adresu pa da u setup-u vidim šta radi. Gledao sam i njegov log ali ne razumem neke delove. Trenutno u logu:

System Log

Date/Time Facility Severity Message
1st day 12:34:17 user debug udhcpc: Sending discover...
1st day 12:34:18 user debug udhcpc: Sending discover...
1st day 12:34:35 user warn dnsprobe[583]: dns query failed
1st day 12:34:45 user alert kernel: Intrusion -> IN=ppp_8_35_1 OUT= MAC= SRC=41.232.30.206 DST=91.150.99.119 LEN=48 TOS=0x00 PREC=0x00 TTL=118 ID=2023 DF PROTO=TCP SPT=1556 DPT=46554 WINDOW=65535 RES=0x00 SYN URGP=0
1st day 12:35:08 user warn dnsprobe[583]: dns query failed
1st day 12:35:22 user debug udhcpc: Sending discover...
1st day 12:35:24 user debug udhcpc: Sending discover...
1st day 12:35:26 user debug udhcpc: Sending discover...
1st day 12:36:30 user debug udhcpc: Sending discover...
1st day 12:36:32 user debug udhcpc: Sending discover...
1st day 12:36:34 user debug udhcpc: Sending discover...
1st day 12:37:14 user warn dnsprobe[583]: dns query failed
1st day 12:37:38 user debug udhcpc: Sending discover...
1st day 12:37:40 user debug udhcpc: Sending discover...
1st day 12:37:43 user debug udhcpc: Sending discover...
1st day 12:38:18 user warn dnsprobe[583]: dns query failed
1st day 12:38:20 user warn dnsprobe[583]: dns query failed
1st day 12:38:22 user warn dnsprobe[583]: dns query failed
1st day 12:38:22 user notice dnsprobe[583]: Primary DNS server Is Down... Switching To Secondary DNS server
1st day 12:38:46 user debug udhcpc: Sending discover...
1st day 12:38:48 user debug udhcpc: Sending discover...
1st day 12:38:50 user debug udhcpc: Sending discover...
1st day 12:38:53 user notice dnsprobe[583]: Switching Back To Primary DNS server
1st day 12:39:24 user alert kernel: Intrusion -> IN=ppp_8_35_1 OUT= MAC= SRC=124.189.225.56 DST=91.150.99.119 LEN=52 TOS=0x00 PREC=0x00 TTL=101 ID=42420 DF PROTO=TCP SPT=2458 DPT=46554 WINDOW=65535 RES=0x00 SYN URGP=0
1st day 12:39:54 user debug udhcpc: Sending discover...
1st day 12:39:56 user debug udhcpc: Sending discover...
1st day 12:39:58 user debug udhcpc: Sending discover...
1st day 12:41:02 user debug udhcpc: Sending discover...
1st day 12:41:04 user debug udhcpc: Sending discover...
1st day 12:41:06 user debug udhcpc: Sending discover...
1st day 12:42:00 user warn dnsprobe[583]: dns query failed
1st day 12:42:10 user debug udhcpc: Sending discover...
1st day 12:42:13 user debug udhcpc: Sending discover...
1st day 12:42:14 user debug udhcpc: Sending discover...
1st day 12:42:15 daemon crit pppd[480]: Clear IP addresses. Connection DOWN.
1st day 12:42:17 user debug syslog: ip route del default table 100
1st day 12:42:17 user debug syslog: ip route add default dev ppp_8_35_1 table 100
1st day 12:42:21 daemon notice pppd[480]: PPP: Start to connect ...
1st day 12:42:21 user debug syslog: ip route del default table 100
1st day 12:42:21 user debug syslog: ip route add default dev ppp_8_35_1 table 100
1st day 12:42:22 daemon crit pppd[480]: PPP server detected.
1st day 12:42:22 user debug syslog: ip route del default table 100
1st day 12:42:22 user debug syslog: ip route add default dev ppp_8_35_1 table 100
1st day 12:42:22 daemon crit pppd[480]: PPP session established.
1st day 12:42:22 user debug syslog: ip route del default table 100
1st day 12:42:22 user debug syslog: ip route add default dev ppp_8_35_1 table 100
1st day 12:42:22 daemon crit pppd[480]: PPP LCP UP.
1st day 12:42:22 user debug syslog: ip route del default table 100
1st day 12:42:22 user debug syslog: ip route add default dev ppp_8_35_1 table 100
1st day 12:42:23 daemon crit pppd[480]: Clear IP addresses. PPP connection DOWN.
1st day 12:42:23 user debug syslog: ip route del default table 100
1st day 12:42:23 user debug syslog: ip route add default dev ppp_8_35_1 table 100
1st day 12:42:23 daemon crit pppd[480]: Received valid IP address from server. Connection UP.
1st day 12:42:23 user debug syslog: route del default 2>/dev/null
1st day 12:42:23 user debug syslog: route del default 2>/dev/null
1st day 12:42:23 user debug syslog: route add default gw 77.46.206.1 2>/dev/null
1st day 12:42:23 user debug syslog: iptables -A FWD_UTILIZE -o ppp_8_35_1 -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
1st day 12:42:23 user debug syslog: iptables -A FWD_UTILIZE -i ppp_8_35_1 -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
1st day 12:42:23 user debug syslog: iptables -t nat -D POSTROUTING -o ppp_8_35_1 -s 192.168.1.0/255.255.255.0 -j MASQUERADE 2>/dev/null
1st day 12:42:23 user debug syslog: iptables -t nat -A POSTROUTING -o ppp_8_35_1 -s 192.168.1.0/255.255.255.0 -j MASQUERADE
1st day 12:42:23 user debug syslog: iptables -t nat -I PRE_VRTSVR 1 -i ppp_8_35_1 -p tcp --dport 19999:20000 -j DNAT --to 192.168.1.2 2>/dev/null
1st day 12:42:23 user debug syslog: iptables -I FWD_IN 1 -i ppp_8_35_1 -p tcp -d 192.168.1.2 --dport 19999:20000 -j ACCEPT 2>/dev/null
1st day 12:42:24 user debug syslog: iptables -t nat -I PRE_VRTSVR 1 -i ppp_8_35_1 -p udp --dport 19999:20000 -j DNAT --to 192.168.1.2 2>/dev/null
1st day 12:42:24 user debug syslog: iptables -I FWD_IN 1 -i ppp_8_35_1 -p udp -d 192.168.1.2 --dport 19999:20000 -j ACCEPT 2>/dev/null
1st day 12:42:24 user debug syslog: echo 1 > /proc/sys/net/ipv4/conf/ppp_8_35_1/rp_filter
1st day 12:42:24 user debug syslog: iptables -A INPUT -p ALL -i ppp_8_35_1 -m state --state ESTABLISHED,RELATED -j ACCEPT
1st day 12:42:24 user debug syslog: iptables -A FWD_IN -p ALL -i ppp_8_35_1 -m state --state ESTABLISHED,RELATED -j ACCEPT
1st day 12:42:24 user debug syslog: iptables -A INPUT -i ppp_8_35_1 -p tcp --syn -m limit --limit 6/h -j LOG --log-level 1 --log-prefix="Intrusion -> "
1st day 12:42:24 user debug syslog: iptables -A FWD_IN -i ppp_8_35_1 -p tcp --syn -m limit --limit 6/h -j LOG --log-level 1 --log-prefix="Intrusion -> "
1st day 12:42:24 user debug syslog: iptables -A INPUT -i ppp_8_35_1 -j DROP 2>/dev/null
1st day 12:42:24 user debug syslog: iptables -A FWD_IN -i ppp_8_35_1 -j DROP 2>/dev/null
1st day 12:42:24 user debug syslog: ip route flush table 128
1st day 12:42:24 user debug syslog: ip rule delete from 91.150.99.119 table 128
1st day 12:42:24 user debug syslog: ip rule add from 77.46.206.8 table 128 2>/dev/null
1st day 12:42:24 user debug syslog: ip route add default via 77.46.206.1 dev ppp_8_35_1 table 128 2>/dev/null
1st day 12:42:24 user debug syslog: ip route add 192.168.1.0/24 dev br0 table 128 2>/dev/null
1st day 12:42:24 user debug syslog: ip route flush table 100
1st day 12:42:24 user debug syslog: ip route add 192.168.1.0/24 dev br0 table 100
1st day 12:42:24 user debug syslog: ip route add default dev ppp_8_35_1 table 100
1st day 12:42:24 user debug syslog: iptables -t mangle -A OUTPUT -j MARK --set-mark 3 -p udp --dport 53
1st day 12:42:24 user debug syslog: iptables -t mangle -A OUTPUT -j MARK --set-mark 3 -p 2
1st day 12:42:24 user debug syslog: iptables -t mangle -A OUTPUT -j MARK --set-mark 3 -p udp --sport 161
1st day 12:42:25 user debug syslog: iptables -t mangle -A OUTPUT -j MARK --set-mark 3 -p udp --sport 520
1st day 12:42:25 user debug syslog: iptables -t mangle -A OUTPUT -j MARK --set-mark 3 -p udp --dport 67:68
1st day 12:43:04 user alert kernel: Intrusion -> IN=ppp_8_35_1 OUT= MAC= SRC=190.138.93.213 DST=77.46.206.8 LEN=48 TOS=0x00 PREC=0x00 TTL=105 ID=61216 DF PROTO=TCP SPT=50019 DPT=19264 WINDOW=65535 RES=0x00 SYN URGP=0
1st day 12:43:07 user alert kernel: Intrusion -> IN=ppp_8_35_1 OUT= MAC= SRC=190.138.93.213 DST=77.46.206.8 LEN=48 TOS=0x00 PREC=0x00 TTL=105 ID=61233 DF PROTO=TCP SPT=50019 DPT=19264 WINDOW=65535 RES=0x00 SYN URGP=0
1st day 12:43:14 user alert kernel: Intrusion -> IN=ppp_8_35_1 OUT= MAC= SRC=190.138.93.213 DST=77.46.206.8 LEN=48 TOS=0x00 PREC=0x00 TTL=105 ID=61266 DF PROTO=TCP SPT=50019 DPT=19264 WINDOW=65535 RES=0x00 SYN URGP=0
1st day 12:43:18 user debug udhcpc: Sending discover...
1st day 12:43:20 user debug udhcpc: Sending discover...
1st day 12:43:22 user debug udhcpc: Sending discover...
1st day 12:43:35 user warn dnsprobe[583]: dns query failed
1st day 12:43:37 user warn dnsprobe[583]: dns query failed
1st day 12:44:06 user alert kernel: Intrusion -> IN=ppp_8_35_1 OUT= MAC= SRC=190.138.93.213 DST=77.46.206.8 LEN=48 TOS=0x00 PREC=0x00 TTL=105 ID=61469 DF PROTO=TCP SPT=50059 DPT=19264 WINDOW=65535 RES=0x00 SYN URGP=0
1st day 12:44:09 user alert kernel: Intrusion -> IN=ppp_8_35_1 OUT= MAC= SRC=190.138.93.213 DST=77.46.206.8 LEN=48 TOS=0x00 PREC=0x00 TTL=105 ID=61479 DF PROTO=TCP SPT=50059 DPT=19264 WINDOW=65535 RES=0x00 SYN URGP=0
1st day 12:44:26 user debug udhcpc: Sending discover...
1st day 12:44:28 user debug udhcpc: Sending discover...
1st day 12:44:30 user debug udhcpc: Sending discover...
1st day 12:45:34 user debug udhcpc: Sending discover...
1st day 12:45:36 user debug udhcpc: Sending discover...
1st day 12:45:38 user debug udhcpc: Sending discover...
1st day 12:45:43 user warn dnsprobe[583]: dns query failed
1st day 12:45:45 user warn dnsprobe[583]: dns query failed
1st day 12:45:47 user warn dnsprobe[583]: dns query failed
1st day 12:45:47 user notice dnsprobe[583]: Primary DNS server Is Down... Switching To Secondary DNS server
1st day 12:46:19 user warn dnsprobe[583]: dns query failed
1st day 12:46:20 user notice dnsprobe[583]: Switching Back To Primary DNS server
1st day 12:46:42 user debug udhcpc: Sending discover...
1st day 12:46:44 user debug udhcpc: Sending discover...
1st day 12:46:46 user debug udhcpc: Sending discover...
1st day 12:47:50 user debug udhcpc: Sending discover...
1st day 12:47:52 user debug udhcpc: Sending discover...
1st day 12:47:54 user debug udhcpc: Sending discover...
1st day 12:48:26 user warn dnsprobe[583]: dns query failed
1st day 12:48:58 user debug udhcpc: Sending discover...
1st day 12:49:00 user debug udhcpc: Sending discover...
1st day 12:49:02 user debug udhcpc: Sending discover...
1st day 12:49:30 user warn dnsprobe[583]: dns query failed
1st day 12:50:06 user debug udhcpc: Sending discover...
1st day 12:50:08 user debug udhcpc: Sending discover...
1st day 12:50:10 user debug udhcpc: Sending discover...
1st day 12:51:14 user debug udhcpc: Sending discover...
1st day 12:51:16 user debug udhcpc: Sending discover...
1st day 12:51:18 user debug udhcpc: Sending discover...
1st day 12:51:36 user warn dnsprobe[583]: dns query failed
1st day 12:51:38 user warn dnsprobe[583]: dns query failed
1st day 12:51:40 user warn dnsprobe[583]: dns query failed
1st day 12:51:40 user notice dnsprobe[583]: Primary DNS server Is Down... Switching To Secondary DNS server
1st day 12:52:11 user notice dnsprobe[583]: Switching Back To Primary DNS server
1st day 12:52:22 user debug udhcpc: Sending discover...
1st day 12:52:24 user debug udhcpc: Sending discover...
1st day 12:52:26 user debug udhcpc: Sending discover...
1st day 12:53:14 user warn dnsprobe[583]: dns query failed
1st day 12:53:15 user alert kernel: Intrusion -> IN=ppp_8_35_1 OUT= MAC= SRC=190.138.93.213 DST=77.46.206.8 LEN=48 TOS=0x00 PREC=0x00 TTL=106 ID=2095 DF PROTO=TCP SPT=50382 DPT=19264 WINDOW=65535 RES=0x00 SYN URGP=0
1st day 12:53:30 user debug udhcpc: Sending discover...
1st day 12:53:32 user debug udhcpc: Sending discover...
1st day 12:53:34 user debug udhcpc: Sending discover...
1st day 12:53:47 user warn dnsprobe[583]: dns query failed
1st day 12:54:38 user debug udhcpc: Sending discover...
1st day 12:54:40 user debug udhcpc: Sending discover...
1st day 12:54:42 user debug udhcpc: Sending discover...
1st day 12:54:51 user warn dnsprobe[583]: dns query failed
1st day 12:55:24 user warn dnsprobe[583]: dns query failed
1st day 12:55:26 user warn dnsprobe[583]: dns query failed
1st day 12:55:46 user debug udhcpc: Sending discover...
1st day 12:55:48 user debug udhcpc: Sending discover...
1st day 12:55:50 user debug udhcpc: Sending discover...
1st day 12:56:54 user debug udhcpc: Sending discover...
1st day 12:56:56 user debug udhcpc: Sending discover...
1st day 12:56:58 user debug udhcpc: Sending discover...
1st day 12:58:02 user debug udhcpc: Sending discover...
1st day 12:58:04 user debug udhcpc: Sending discover...
1st day 12:58:06 user debug udhcpc: Sending discover...
1st day 12:59:10 user debug udhcpc: Sending discover...
1st day 12:59:12 user debug udhcpc: Sending discover...
1st day 12:59:14 user debug udhcpc: Sending discover...
1st day 13:00:07 user warn dnsprobe[583]: dns query failed
1st day 13:00:18 user debug udhcpc: Sending discover...
1st day 13:00:20 user debug udhcpc: Sending discover...
1st day 13:00:22 user debug udhcpc: Sending discover...
1st day 13:00:40 user warn dnsprobe[583]: dns query failed
1st day 13:01:26 user debug udhcpc: Sending discover...
1st day 13:01:28 user debug udhcpc: Sending discover...
1st day 13:01:30 user debug udhcpc: Sending discover...
1st day 13:01:44 user warn dnsprobe[583]: dns query failed
1st day 13:02:17 user warn dnsprobe[583]: dns query failed
1st day 13:02:34 user debug udhcpc: Sending discover...
1st day 13:02:36 user debug udhcpc: Sending discover...
1st day 13:02:38 user debug udhcpc: Sending discover...
1st day 13:03:42 user debug udhcpc: Sending discover...
1st day 13:03:44 user debug udhcpc: Sending discover...
1st day 13:03:46 user debug udhcpc: Sending discover...
1st day 13:04:50 user debug udhcpc: Sending discover...
1st day 13:04:52 user debug udhcpc: Sending discover...
1st day 13:04:54 user debug udhcpc: Sending discover...
1st day 13:04:54 user warn dnsprobe[583]: dns query failed
1st day 13:04:56 user warn dnsprobe[583]: dns query failed
1st day 13:04:58 user warn dnsprobe[583]: dns query failed
1st day 13:04:58 user notice dnsprobe[583]: Primary DNS server Is Down... Switching To Secondary DNS server
1st day 13:05:29 user notice dnsprobe[583]: Switching Back To Primary DNS server
1st day 13:05:58 user debug udhcpc: Sending discover...
1st day 13:06:00 user debug udhcpc: Sending discover...
1st day 13:06:02 user debug udhcpc: Sending discover...
1st day 13:07:07 user debug udhcpc: Sending discover...
1st day 13:07:08 user debug udhcpc: Sending discover...
1st day 13:07:10 user debug udhcpc: Sending discover...
1st day 13:07:30 user alert kernel: Intrusion -> IN=ppp_8_35_1 OUT= MAC= SRC=77.96.35.42 DST=77.46.206.8 LEN=48 TOS=0x00 PREC=0x00 TTL=107 ID=25359 DF PROTO=TCP SPT=4526 DPT=5900 WINDOW=64240 RES=0x00 SYN URGP=0
1st day 13:08:06 user warn dnsprobe[583]: dns query failed

Da ne bi došlo do zabune datum i vreme u logu su ustvari broj dana i sati od poslednjeg startovanja. Kapiram ovaj deo da ne može da kontaktira primarni DNS server pa da pređe na sekundarni i kasnije opet proba primarni ali ne razumem šta se dešava u ostatku loga. Mada mi se, kada malo razmislim, čini da je problem u DNS serverima koji su mi uvek
Primary DNS Server: 212.200.191.166
Secondary DNS Server: 212.200.190.166 .
Da li neko zna da li mogu da koristim neke druge DNS servere i ako mogu koje?
Pratio sam i IP adrese i danas su izgledale ovako:

10.5.2008 13:46:39
LAN: 192.168.1.2
WAN: 77.46.207.100
10.5.2008 14:01:48
WAN: 77.46.206.150
10.5.2008 14:47:39
WAN: 77.46.179.115
10.5.2008 16:48:42
WAN: 77.46.228.188
10.5.2008 16:53:44
WAN: 79.101.198.204
10.5.2008 17:24:03
WAN: 212.200.215.157
10.5.2008 17:44:09
WAN: 77.46.206.172
10.5.2008 17:59:16
WAN: 77.46.228.28
10.5.2008 18:14:32
WAN: 77.46.207.15
10.5.2008 18:39:52
WAN: 77.46.213.118
10.5.2008 19:15:12
WAN: 79.101.143.191
10.5.2008 19:30:16
WAN: 77.46.213.39
10.5.2008 19:50:52
WAN: 79.101.215.181
10.5.2008 20:00:57
WAN: 77.46.207.194
10.5.2008 20:11:00
WAN: 212.200.215.58
10.5.2008 20:26:06
WAN: 77.46.221.188
10.5.2008 20:56:20
WAN: 77.46.178.153
10.5.2008 21:01:25
WAN: 77.46.179.130
10.5.2008 21:11:35
WAN: 212.200.215.157
10.5.2008 21:31:43
WAN: 77.46.213.68
10.5.2008 21:41:58
WAN: 79.101.215.204
10.5.2008 22:27:22
WAN: 91.150.99.119
10.5.2008 22:57:43
WAN: 77.46.206.8
10.5.2008 23:27:57
WAN: 77.46.167.138 .

Nisam mnogo upućen u to ali koliko znam i razumem na slabljenje signala utiče cela mreža znači i deo kod tebe, a i Telekomov deo. Utiču čak i drugi korisnici (mnogo kablova jedan pored drugog, el. magnetna indukcija...). :) Na Telekomovom sajtu sam pročitao čak i da tropolne telefonske utičnice treba ukloniti jer unose veliko slabljenje, predpostavljam zbog parazitne kapacitivnosti jer su masivne. Razdaljina od priključka do centrale takođe igra ulogu, lošu, a i spliter je važna stavka.

_{[Ovu poruku je menjao ac1bd4 dana 10.05.2008. u 23:58 GMT+1]}

Možeš da koristiš drugi dns. Probaj sa:
prim: 195.178.32.2
sec: 212.200.13.13

Ali problem nije u tome, već izgleda da je na nižem nivou. Atenuacija jeste velika. Koliki ti je SNR?

---

SNR je 33.4/26.5 up/down. Sada ću promeniti DNS pa ču da vidim da li je do toga. Da li je moguće da utorrent pravi probleme? Čini mi se da se IP adresa menja samo kada utorrent skida nešto (što je skoro uvek).

Drugi DNS serveri nisu ništa promenili. I dalje se IP adresa jako često menja. Ne znam šta bi moglo da reši problem. Da li neko može da protumači log modema?

Mislim da je problem u utorrent-u. Kada je on aktivan IP se menja jako često.

Da, problem izaziva utorrent. Kada saznam kako da ga podesim i promenim to javljam... Hvala svima na pomoći.

Sasvim je moguce da problem ne izaziva uTorrent. Pogledaj da li ti se to raskidanje i ponovo uspostavljanje PPPoE veze (jer je to ono sto ti inicira dodeljivanje nove IP adrese) desava i kada ti je kompjuter iskljucen. Meni se recimo desava. I nema veze ni sa modemom ni sa kompjuterom (probana 4 modema, 3 operativna sistema, modemi u ruter i bridge modu ... sve moguce kombinacije...)

Ako se i tebi desava kada je kompjuter iskljucen : najbolje je da uradis copy&paste svih parametara (attenuacija i sl.) kao i celog Log-a modema i posaljes na [email protected] (ili neku drugu adresu, ako uspes da dodjes do neke druge...hmmm...).

Ideja je da pokusas da preskocis prvu liniju njihovog tech. supporta, jer nece moci nista da ti pomognu a samo ces gubiti vreme i zivce.

P.S. ovaj problem je daleko rasprostranjeniji nego sto se misli - no fakat je da 95% korisnika ADSL-a i ne zna koja im je javna IP adresa, a kamoli sta je to LOG modema i kako da dodje do njega...

Ukoliko vam je Telekom Srbija Vaš Internet servis provajder, i ukoliko ste zakupili paket sa dinamičkom IP adresom, sasvim je normalno da posle svakog vašeg konektovanja dobijete drugačiju IP adresu, stoga ne vidim u čemu je problem, osim ukoliko ne želite dinamičku IP adresu, za šta se podnosi poseban zahtev i plaća dodatna pretplata.

Pozdrav.

Pa, problematicno je to sto kazes: "posle svakog vaseg konektovanja". Ruter bi trebao da je non-stop konektovan preko PPPoE na ISAM/DSLAM opremu kod Telekoma, pa samim tim da "drzi" tu jednu (koja god bila) IP adresu, zar ne?

Problem je sto kod Telekoma, izgleda ne bas malom broju korisnika, PPPoE veza puca bez nekog vidnog razloga (svi parametri veze OK, jacina signala odlicna, ukace se preko ADSL2+ protokola.... ) i to je ono sto iritira. Poneakad mi se to desi 10-tak puta za 4-5 sati, a ponekad tek 2-3 puta dnevno.

Dakle, nije problem sto se menja dinamicka adresa, couldn't care less - to je samo posledica toga sto PPPoE veza na relaciji ruter (bio on Telekomov Huawei, Thomson, TP-Link, ZyXEL, Linksys... nema razlike!) Telekom ISAM/DSLAM oprema puca "sama od sebe".

Da li ti je sada jasno u cemu je problem?

desiti

***
Ukoliko ste konektovani non-stop, IP adresa se može menjati više puta u toku korišćenja, ali se može desiti da veza pukne nekoliko puta (zavisi od broja korisnika koji su u tom trenutku konektovani). Možete uzeti statičku IP adresu, koja je stabilnija, uz odgovarajuću mesečnu pretplatu i naknadu za stupanje u ugovorni odnos.

Pozdrav.

To nije prevelika atenuacija, bar za SmartAX MT882 sasvim je prihvatljiva i u granicama normalnog slabljenja ... meni sa ovim parametrima:

SNR Margin Down/Up(dB) 33.5/37.5
Attenuation Down/Up(dB) 30.5/15.0

radi sve savrseno, stabilno i neprekidno mesecima sa svim protokolima a vidjao sam na paketima 1536/192 nesto ovako:

SNR Margin Down/Up(dB) 10.1/9.0
Attenuation Down/Up(dB) 51.0/39.0

gde opet sve radi stabilno.

E bas me zivo interesuje ste ste hteli da kazete recenicom: " IP adresa se može menjati više puta u toku korišćenja, ali se može desiti da veza pukne nekoliko puta (zavisi od broja korisnika koji su u tom trenutku konektovani)" ????

I takodje me interesuje kakve veze ima pucanje PPPoE veze na relaciji ISAM/DSLAM - moj ruter sa tim da li sam uzeo paket sa statickom ili dinamickom IP adresom?

Ja mogu da razumem da je odradjem keep_alive parametar na strani Telekoma na neki period (ne)aktivnosti ADSL korisnika, pa ako on nema nikakvu aktivnost smatra se da je korisnik iskljucio racunar i "oslobadja" se njegova adresa na DHCP-u i daje sledecem koji ce se konektovati (da ne ulazim sada u prolematiku zbog cega se to radi), ali ako imam neki protok (surfujem, downloadujem service pack za XP... sta god) - nebi smelo da se desava. A desava se.

Da ne napominjem da mi se to nije desavalo ranije ni sa 56K dial-up-om, gde sam umevao da ostanem na vezi od 21 do 07h vrlo cesto. A na ADSL-u se eto desava... Sta god da je uzrok - bruka je...

Koliki ti je CRC Down/Up
FEC Down/Up
HEC Down/Up

Ako su brojke prevelike onda je definitivno problem sa slabim signalom i velikim šumom

CRC Down/Up 3/0
FEC Down/Up 0/0
HEC Down/Up 162/0



A evo i:


SNR Margin Down/Up(dB) 48.0/42.0
Attenuation Down/Up(dB) 24.0/12.5

ja imam staticku IP adresu, a menja se na pola sata. modem (rooter) se resetuje sam od sebe. nema veze za li radi torrent ili rapidshare, koje je doba dana ili noci, da ,li skida nesto na firefoxu ili exploreru, ili surfujem ili jednostavno ne radim nista. on se na oko pola sata resetuje i menja mi adresu. ako je to privilegija dinamicke IP adrese koja je gore spomenuta, hvala, ne treba mi HOCU STATICNU. a i dinamicna se menja po ukljucenju modema, a ne sama od sebe. smao ne znam ima li rooter neki tajmer za automatsko resetovanje zato sto su inace telekomovi modemi njesra zivo i oni kao provajder su toliko jadni i nikakvi da su bruka za srpski internet. zabrana p2p i blokade modema. sta misle da smo nesmosobni da ih port forwardujemo. samo sada da provalim ovo i onda cu da odem u telekom da im pokazem modem kako teba da bude setovan i onda cu da ga polomim pred njima.

Staticka IP adresa po definiciji treba da ti je uvek ista, bez obzira koliko puta raskidao i uspostavljao PPPoE vezu. Ne moze da se "menja na pola sata".

A sto se raskidanja veze usled _resetovanja_ rutera na pola sata, to je prilicno drasticno i mozda ti jednostavno imas falican primerak modema? Ili se ruter pregreva - probaj da mu obezbedis bolji protok vazduha pa vidi da li ima neke promene.

Prvo odluči da li imaš ili nemaš statičku. Pošto mislim da je nemaš, možeš da je dobiješ ako si već rešio, uplatiš 4.720,00 za zasnivanje pretplatničkog odnosa sa statičkom adresom (sve je ovo iz Telekomovog cenovnika) i onda izabereš paket. Cene su 512/64 - 3.186,00 pa malo brže 1024/128 - 4.720,00 i najbrže 1536/192 - 6.490,00 dinara. Posle toga adresa neće da se menja ali će da ti bude problem rapidshare.

Ako stvarno odluče da zabrane p2p, onda forvardovanje portova ne pomaže.

Ipak mislim da imaš feleričan ruter pa počni odatle sa rešavanjem problema. Lomljenje rutera neće da ih potrese, sklopio si ugovor na bar godinu dana a njima je još i bolje ako platiš a ne koristiš.