Navigacija
Lista poslednjih: 16, 32, 64, 128 poruka.

wireless i pppoe konekcija

[es] :: Linux :: wireless i pppoe konekcija

Strane: 1 2

[ Pregleda: 9799 | Odgovora: 32 ] > FB > Twit

Postavi temu Odgovori

Autor

Pretraga teme: Traži
Markiranje Štampanje RSS

potajaco
Aleksandar Potajac
Banja Luka

Član broj: 48034
Poruke: 40
*.broadband.blic.net.



Profil

icon wireless i pppoe konekcija 05.01.2006. u 14:53 - pre 222 meseci
dakle kao sto stoji u naslovu imam problema sa podesavanjem pppoe konekcije ....
imam suse linux 9.3 i instalirao sam rp-pppoe-3.7 patch koji je potreban da bi se ostvarila pppoe konekcija ... njega sam dobro konfigurisao (bar mislim)
moj AP radi u client modu i kada ga pingam dobijem normalan odziv, sto znaci da komunicira sa mreznom karticom... e sada sledece sto je potrebno uraditi je napisati scriptu i kada je pozivam da ona ostvari konekciju ....
probao sam sa dve scripte (jedna od provajdera i jedna koja radi kod frenda) :

1.

#!/bin/sh
sleep 5
exec /usr/sbin/pppd pty \
'/usr/local/rp-pppoe/sbin/pppoe -I <ethX> -S BLICNET -m 1412 -T 120' \
nobsdcomp noaccomp noauth nodetach defaultroute \
lcp-echo-interval 30 lcp-echo-failure 2 \
nomppc mppe required,stateless \
user <username>

kada pozovem ovu scriptu javi mi da je nepoznata komanda "sleep" a kada izbrisem tu liniju javi za sledecu da ne valja ....

2.

user ( korisnicko ime )
pty "/usr/sbin/pppoe -I eth0 -T 80 1412 -S BLICNET"
noipdefault
usepeerdns
defaultroute
lcp-echo-interval 30
lcp-echo-failure 3
connect /bin/true
require-mppe-128
refuse-chap
refuse-pap
refuse-eap
persist
mtu 1492
noaccomp
default-asyncmap

e sada kada startujem ovu scriptu dobijem ovakav odgovor:

linux:/etc/ppp/peers # pppd call blicnet
Serial connection established.
Using interface ppp1
Connect: ppp1 <--> /dev/pts/2
pppoe: Timeout waiting for PADO packets
Modem hangup
Connection terminated.
Script /usr/sbin/pppoe -I eth0 -T 80 1412 -S BLICNET-VRB1 finished (pid 13343), status = 0x1


e sada ako nema ima neke ideje nek mi javi ...
unapred hvala

pozdrav
 
Odgovor na temu

Ned123
Nenad Bošnjak
Senior System Administrator
PIXOMONDO Images
Stuttgart, Germany

Član broj: 64971
Poruke: 835
*.broadband.blic.net.

Sajt: www.linkedin.com/in/nenad..


+28 Profil

icon Re: wireless i pppoe konekcija 06.01.2006. u 07:48 - pre 222 meseci
Pokušaj kompajlirati rp-pppoe iz sorsa. Ja sa susetovom verzijom nikad nisam uspio pokrenuti pppoe konekciju sa BLIC-om (ni iz 10.0). Mani se skripti sa blicovog sajta. Odradi pppoe-setup i samo u /etc/ppp/pppoe.conf dodaj PPPD_EXTRA="require-mppe". Konekciju pokrećeš sa pppoe-start i gasiš sa pppoe-stop. Možeš instalirati knemo i jednim klikom raditi ove dvije komande.
Više informacija na:
http://helpdesk.blic.net/viewtopic.php?t=108&start=0

PS: Koliko znam suse bi trebalo da ima ppp_mppe podršku u kernelu, tako da oko toga ne bi trebalo da imaš problema.
 
Odgovor na temu

potajaco
Aleksandar Potajac
Banja Luka

Član broj: 48034
Poruke: 40
*.broadband.blic.net.



Profil

icon Re: wireless i pppoe konekcija 06.01.2006. u 11:26 - pre 222 meseci
ma probano, kompajliram ja rp pppoe i kad kucam pppoe-status dobijem ovo :


linux:/etc/ppp/peers # pppoe-status
Note: You have enabled demand-connection; pppoe-status may be inaccurate.
pppoe-status: Link is down (can't read pppoe PID file /var/run/pppoe.conf-pppoe.pid.pppoe)

... znam ja da od njihovih scripti nema nista ...
ali ova druga nije njihova .... a kod mene nece da radi dok poznajem covjeka kod kojeg radi perfektno
 
Odgovor na temu

Ned123
Nenad Bošnjak
Senior System Administrator
PIXOMONDO Images
Stuttgart, Germany

Član broj: 64971
Poruke: 835
*.broadband.blic.net.

Sajt: www.linkedin.com/in/nenad..


+28 Profil

icon Re: wireless i pppoe konekcija 06.01.2006. u 11:52 - pre 222 meseci
Citat:
potajaco: ma probano, kompajliram ja rp pppoe i kad kucam pppoe-status dobijem ovo :


linux:/etc/ppp/peers # pppoe-status
Note: You have enabled demand-connection; pppoe-status may be inaccurate.
pppoe-status: Link is down (can't read pppoe PID file /var/run/pppoe.conf-pppoe.pid.pppoe)

... znam ja da od njihovih scripti nema nista ...
ali ova druga nije njihova .... a kod mene nece da radi dok poznajem covjeka kod kojeg radi perfektno

E ovako, ukucaj:
DEBUG=1 pppoe-start
i postuj /tmp/xxxx/debug.txt ili kako se već zove fajl, koga napravi debug.
 
Odgovor na temu

potajaco
Aleksandar Potajac
Banja Luka

Član broj: 48034
Poruke: 40
*.broadband.blic.net.



Profil

icon Re: wireless i pppoe konekcija 06.01.2006. u 15:23 - pre 222 meseci
e ovako .... nakon te komande sam dobio sledeci "podugacak" tekst u kojem nisam bas nesto mnogo skuzio:

---------------------------------------------
* The following section contains information about your system
Fri Jan 6 15:49:09 CET 2006
Output of uname -a
Linux linux 2.6.11.4-20a-default #1 Wed Mar 23 21:52:37 UTC 2005 i686 i686 i386 GNU/Linux
---------------------------------------------
* The following section contains information about your network
* interfaces. The one you chose for PPPoE should contain the words:
* 'UP' and 'RUNNING'. If it does not, you probably have an Ethernet
* driver problem.
Output of ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:0B:6A:1F:6A:CC
inet addr:192.168.2.5 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::20b:6aff:fe1f:6acc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:4582 (4.4 Kb)
Interrupt:3 Base address:0x4f00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:52 errors:0 dropped:0 overruns:0 frame:0
TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3360 (3.2 Kb) TX bytes:3360 (3.2 Kb)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

---------------------------------------------
* The following section contains information about kernel modules
* If the module for your Ethernet card is 'tulip', you might
* want to look for an updated version at http://www.scyld.com
Output of lsmod
Module Size Used by
nls_iso8859_1 4096 1
nls_cp437 5760 1
vfat 12800 1
fat 37916 1 vfat
usb_storage 63680 1
af_packet 20744 0
ppp_async 11136 0
crc_ccitt 2176 1 ppp_async
ppp_generic 28180 1 ppp_async
slhc 7424 1 ppp_generic
appletalk 34612 2
ax25 58476 2
ipx 27184 2
ipt_LOG 6912 0
ipt_limit 2432 0
ipt_pkttype 1792 0
subfs 7296 2
i915 18560 1
drm 60052 2 i915
bttv 146448 0
video_buf 20356 1 bttv
firmware_class 9472 1 bttv
i2c_algo_bit 8968 1 bttv
v4l2_common 5760 1 bttv
btcx_risc 4744 1 bttv
tveeprom 12824 1 bttv
i2c_core 21776 3 bttv,i2c_algo_bit,tveeprom
videodev 9088 1 bttv
usbserial 28008 0
nvram 8200 0
snd_pcm_oss 57632 0
snd_mixer_oss 18944 1 snd_pcm_oss
ipt_state 2048 0
usbhid 41312 0
ip6t_REJECT 6784 0
ipt_REJECT 6656 0
iptable_mangle 2816 0
iptable_filter 2944 0
ip6table_mangle 2432 0
ip_nat_ftp 3072 0
iptable_nat 22236 1 ip_nat_ftp
ip_conntrack_ftp 72592 1 ip_nat_ftp
ip_conntrack 42168 4 ipt_state,ip_nat_ftp,iptable_nat,ip_conntrack_ftp
ip_tables 20352 8 ipt_LOG,ipt_limit,ipt_pkttype,ipt_state,ipt_REJECT,iptable_mangle,iptable_filter,iptable_nat
ip6table_filter 2816 0
ip6_tables 18304 3 ip6t_REJECT,ip6table_mangle,ip6table_filter
ipv6 236672 11 ip6t_REJECT
edd 10080 0
evdev 8832 0
joydev 9664 0
sg 36256 0
st 37788 0
sr_mod 16548 0
video1394 17612 0
ohci1394 31492 1 video1394
raw1394 28140 0
ieee1394 97976 3 video1394,ohci1394,raw1394
capability 3256 0
nls_utf8 2048 2
ntfs 167184 2
8139too 24192 0
mii 4864 1 8139too
ehci_hcd 31624 0
sd_mod 17936 2
scsi_mod 125256 5 usb_storage,sg,st,sr_mod,sd_mod
uhci_hcd 30224 0
snd_intel8x0 31808 0
intel_agp 21532 1
snd_ac97_codec 71416 1 snd_intel8x0
agpgart 32296 3 drm,intel_agp
snd_pcm 93832 3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer 24452 1 snd_pcm
snd 60548 6 snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore 8928 1 snd
snd_page_alloc 9988 2 snd_intel8x0,snd_pcm
parport_pc 38212 1
lp 11076 0
parport 33864 2 parport_pc,lp
dm_mod 56316 0
hsfusbcd2 61848 0
hsfmc97sis 52752 0
hsfmc97ati 50704 0
hsfmc97ali 57108 0
hsfmc97via 54296 0
hsfmc97ich 56080 0
hsfpcibasic2 61328 0
hsfserial 22052 7 hsfusbcd2,hsfmc97sis,hsfmc97ati,hsfmc97ali,hsfmc97via,hsfmc97ich,hsfpcibasic2
hsfengine 1320340 1 hsfserial
hsfosspec 97256 12 hsfusbcd2,hsfmc97sis,hsfmc97ati,hsfmc97ali,hsfmc97via,hsfmc97ich,hsfpcibasic2,hsfserial,hsfengine
usbcore 108760 8 usb_storage,usbserial,usbhid,ehci_hcd,uhci_hcd,hsfusbcd2,hsfosspec
hsfsoar 58368 7 hsfusbcd2,hsfmc97sis,hsfmc97ati,hsfmc97ali,hsfmc97via,hsfmc97ich,hsfpcibasic2
reiserfs 242928 1
ide_cd 37892 0
cdrom 36640 2 sr_mod,ide_cd
ide_disk 16640 5
piix 9988 0 [permanent]
ide_core 120020 4 usb_storage,ide_cd,ide_disk,piix
---------------------------------------------
* The following section lists your routing table.
* If you have an entry which starts with '0.0.0.0', you probably
* have defined a default route and gateway, and pppd will
* not create a default route using your ISP. Try getting
* rid of this route.
Output of netstat -n -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
---------------------------------------------
Contents of /etc/resolv.conf
* The following section lists DNS setup.
* If you can browse by IP address, but not name, suspect
* a DNS problem.
nameserver 217.23.192.9
nameserver 217.23.192.14
---------------------------------------------
* The following section lists /etc/ppp/options.
* You should have NOTHING in that file.
Contents of /etc/ppp/options
# /etc/ppp/options
#
# Not every option is listed here, see man pppd for more details. This file
# is read by the pppd, it is an error when it is not present.
#
# Use the following command to see the active options:
# grep -v ^# /etc/ppp/options | grep -v ^$
#

# The name of this server. Often, the FQDN is used here.
#name <host>

# Enforce the use of the hostname as the name of the local system for
# authentication purposes (overrides the name option).
#usehostname

# If no local IP address is given, pppd will use the first IP address
# that belongs to the local hostname. If "noipdefault" is given, this
# is disabled and the peer will have to supply an IP address.
noipdefault

# With this option, pppd will accept the peer's idea of our local IP
# address, even if the local IP address was specified in an option.
#ipcp-accept-local

# With this option, pppd will accept the peer's idea of its (remote) IP
# address, even if the remote IP address was specified in an option.
#ipcp-accept-remote

# Run the executable or shell command specified after pppd has terminated
# the link. This script could, for example, issue commands to the modem
# to cause it to hang up if hardware modem control signals were not
# available.
# If mgetty is running, it will reset the modem anyway. So there is no need
# to do it here.
#disconnect "chat -- \d+++\d\c OK ath0 OK"

# Increase debugging level (same as -d). The debug output is written
# to syslog LOG_LOCAL2.
#debug

# Enable debugging code in the kernel-level PPP driver. The argument n
# is a number which is the sum of the following values: 1 to enable
# general debug messages, 2 to request that the contents of received
# packets be printed, and 4 to request that the contents of transmitted
# packets be printed.
#kdebug n

# noauth means do not require the peer to authenticate itself, this must
# be set if you want to use pppd to connect to the internet. In this case
# *you* must authenicate yourself to the peer(internet provider), so do
# not disable this setting unless you are the dial-in server which where
# the peer has to autenticate to.
noauth

# Use hardware flow control (i.e. RTS/CTS) to control the flow of data
# on the serial port.
crtscts

# Specifies that pppd should use a UUCP-style lock on the serial device
# to ensure exclusive access to the device.
lock

# Use the modem control lines.(is default)
modem
# The opposite: local
#
# Description:
# Don't use the modem control lines. With this option, pppd will ignore the
# state of the CD (Carrier Detect) signal from the modem and will not change
# the state of the DTR (Data Terminal Ready) signal.
#
# You need to disable modem and enable local if you want to connect to anoter
# system without using a modem:
#local

# async character map -- 32-bit hex; each bit is a character
# that needs to be escaped for pppd to receive it. 0x00000001
# represents '\x01', and 0x80000000 represents '\x1f'.
# To allow pppd to work over a rlogin/telnet connection, ou should escape
# XON (^Q), XOFF (^S) and ^]: (The peer should use "escape ff".)
#asyncmap 200a0000
asyncmap 0

# needed for some ISDN Terminaladaters, namely ELSA, those seem to have
# problems with asyncmap negotiation, so you can turn off this procedure
# in case your ISDN box has trouble with it, by enabling this option.
# You have to disable the asyncmap <x> option to be sure to have it
# active. If you use wvdial, set the ISDN parameter in /etc/wvdial.conf
# instead.
#default-asyncmap

# Set the MRU [Maximum Receive Unit] value to <n> for negotiation. pppd
# will ask the peer to send packets of no more than <n> bytes. The
# minimum MRU value is 128. The default MRU value is 1500. A value of
# 296 is recommended for slow links (40 bytes for TCP/IP header + 256
# bytes of data). The value 1492 is for DSL connections (PPP Default -
# PPPoE Header: 1500 - 8 = 1492)
# mru 1492

# Set the MTU [Maximum Transmit Unit] value to <n>. Unless the peer
# requests a smaller value via MRU negotiation, pppd will request that
# the kernel networking code send data packets of no more than n bytes
# through the PPP network interface. The value 1492 is for DSL connections
# (PPP Default - PPPoE Header: 1500 - 8 = 1492)
# mtu 1492

# Set the interface netmask to <n>, a 32 bit netmask in "decimal dot"
# notation (e.g. 255.255.255.0).
#netmask 255.255.255.0

# Don't fork to become a background process (otherwise pppd will do so
# if a serial device is specified).
nodetach

# If this option is given, pppd will send an LCP echo-request frame to
# the peer every n seconds. Under Linux, the echo-request is sent when
# no packets have been received from the peer for n seconds. Normally
# the peer should respond to the echo-request by sending an echo-reply.
# This option can be used with the lcp-echo-failure option to detect
# that the peer is no longer connected.
lcp-echo-interval 30

# If this option is given, pppd will presume the peer to be dead if n
# LCP echo-requests are sent without receiving a valid LCP echo-reply.
# If this happens, pppd will terminate the connection. Use of this
# option requires a non-zero value for the lcp-echo-interval parameter.
# This option can be used to enable pppd to terminate after the physical
# connection has been broken (e.g., the modem has hung up) in
# situations where no hardware modem control lines are available.
lcp-echo-failure 4

# Send up to 60 LCP configure-request during negotiation. With a value
# of 2 for lcp-restart below, this might take up to 2 minutes.
lcp-max-configure 60

# Resend unanswered LCP requests after 2 seconds.
lcp-restart 2

# Specifies that pppd should disconnect if the link is idle for n seconds.
idle 600

# Specifies the maximal number of attempts to connect to the server. This
# is useful for dial on demand. Default value is 10.
#maxfail 3

# Disable the IPXCP and IPX protocols.
noipx

# In the file /etc/ppp/filters are some active-filter rules. See man pppd
# and man tcpdump for more informations.
file /etc/ppp/filters

#-------------------------------------------------------------------------
# The next two options are only interesting for you if you are admin of
# a system with other users that use ppp, and those users are normally
# never allowed to add default route, or you do not want users to
# replace the default route.
#-------------------------------------------------------------------------

# enable this to prevent users from attempting to add a default route.
# Use this option with caution: If the user needs to use a program like
# wvdial, he will not be able to connect because wvdial forces defaulroute
# but this is rejected by this option and the user will not be able to
# connect to the internet.
#nodefaultroute

# enable this to prevent users from replacing an existing default route.
#noreplacedefaultroute

#-------------------------------------------------------------------------
# All options below only make sense if you configure pppd to be a dial-in
# server, so don't touch these if you want dial into your provider with
# PPP!
#-------------------------------------------------------------------------

# Set the assumed name of the remote system for authentication purposes
# to <n>.
#remotename <n>

# Add an entry to this system's ARP [Address Resolution Protocol]
# table with the IP address of the peer and the Ethernet address of this
# system. {proxyarp,noproxyarp}
#proxyarp

# Use the system password database for authenticating the peer using
# PAP. Note: mgetty already provides this option. If this is specified
# then dialin from users using a script under Linux to fire up ppp wont work.
#login

# Specify which DNS Servers the incoming Win95 or WinNT Connection should use
# Two Servers can be remotely configured
#ms-dns 192.168.1.1
#ms-dns 192.168.1.2

# Specify which WINS Servers the incoming connection Win95 or WinNT should use
#ms-wins 192.168.1.50
#ms-wins 192.168.1.51

---------------------------------------------
* The following section identifies your Ethernet interface
* and user name. Some ISP's need 'username'; others
* need '[email protected]'. Try both
ETH=eth0; USER=potajac
---------------------------------------------
* The following section shows the pppd command we will invoke
pppd invocation
/usr/bin/setsid /usr/sbin/pppd pty '/usr/sbin/pppoe -p /var/run/pppoe.conf-pppoe.pid.pppoe -I eth0 -T 80 -U -m 1412 ' noipdefault noauth default-asyncmap defaultroute hide-password nodetach mtu 1492 mru 1492 noaccomp nodeflate nopcomp novj novjccomp user potajac lcp-echo-interval 20 lcp-echo-failure 3 debug
---------------------------------------------
using channel 3
Using interface ppp0
Connect: ppp0 <--> /dev/pts/2
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
pppoe: Timeout waiting for PADO packets
Modem hangup
Connection terminated.
Script /usr/sbin/pppoe -p /var/run/pppoe.conf-pppoe.pid.pppoe -I eth0 -T 80 -U -m 1412 -D /tmp/pppoe-debug-8038/pppoe-debug.txt-0 finished (pid 8114), status = 0x1
---------------------------------------------
* The following section is an extract from your log.
* Look for error messages from pppd, such as
* a lack of kernel support for PPP, authentication failure
* etc.
Extract from /var/log/messages
Jan 3 23:51:20 linux pppd[8116]: Exit.
Jan 3 23:51:23 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:51:23 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:51:23 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:51:23 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:51:23 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:51:23 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:51:23 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:51:23 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:51:23 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:51:23 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:52:40 linux pppd[9073]: pppd 2.4.3 started by root, uid 0
Jan 3 23:52:40 linux pppd[9073]: Using interface ppp0
Jan 3 23:52:40 linux pppd[9073]: local IP address 10.112.112.112
Jan 3 23:52:40 linux pppd[9073]: remote IP address 10.112.112.113
Jan 3 23:53:07 linux pppd[9155]: pppd 2.4.3 started by potajac, uid 0
Jan 3 23:53:07 linux pppd[9155]: Serial connection established.
Jan 3 23:53:07 linux pppd[9155]: Using interface ppp1
Jan 3 23:53:07 linux pppd[9155]: Connect: ppp1 <--> /dev/pts/2
Jan 3 23:53:42 linux pppoe[9156]: Timeout waiting for PADO packets
Jan 3 23:53:42 linux pppd[9155]: Modem hangup
Jan 3 23:53:42 linux pppd[9155]: Connection terminated.
Jan 3 23:53:42 linux pppd[9155]: Script /usr/sbin/pppoe -I eth0 -T 80 1412 -S BLICNET-VRB1 finished (pid 9156), status = 0x1
Jan 3 23:53:50 linux pppd[9155]: Terminating on signal 2
Jan 3 23:53:50 linux pppd[9155]: Exit.
Jan 3 23:56:24 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:56:24 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:56:24 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:56:24 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:56:24 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:56:24 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:56:24 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:56:24 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:56:24 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:56:24 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 3 23:56:54 linux pppd[12714]: pppd 2.4.3 started by root, uid 0
Jan 3 23:56:54 linux pppd[12714]: Using interface ppp0
Jan 3 23:56:54 linux pppd[12714]: local IP address 10.112.112.112
Jan 3 23:56:54 linux pppd[12714]: remote IP address 10.112.112.113
Jan 3 23:57:32 linux pppd[12809]: pppd 2.4.3 started by potajac, uid 0
Jan 3 23:57:32 linux pppd[12809]: Serial connection established.
Jan 3 23:57:32 linux pppd[12809]: Using interface ppp1
Jan 3 23:57:32 linux pppd[12809]: Connect: ppp1 <--> /dev/pts/4
Jan 3 23:58:07 linux pppoe[12810]: Timeout waiting for PADO packets
Jan 3 23:58:07 linux pppd[12809]: Modem hangup
Jan 3 23:58:07 linux pppd[12809]: Connection terminated.
Jan 3 23:58:07 linux pppd[12809]: Script /usr/sbin/pppoe -I eth0 -T 80 1412 -S BLICNET-VRB1 finished (pid 12810), status = 0x1
Jan 3 23:58:43 linux pppd[12809]: Terminating on signal 2
Jan 3 23:58:43 linux pppd[12809]: Modem hangup
Jan 3 23:58:43 linux pppd[12809]: Connection terminated.
Jan 3 23:58:43 linux pppd[12809]: Exit.
Jan 4 00:01:23 linux pppd[13342]: pppd 2.4.3 started by potajac, uid 0
Jan 4 00:01:23 linux pppd[13342]: Serial connection established.
Jan 4 00:01:23 linux pppd[13342]: Using interface ppp1
Jan 4 00:01:23 linux pppd[13342]: Connect: ppp1 <--> /dev/pts/2
Jan 4 00:01:25 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 4 00:01:25 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 4 00:01:25 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 4 00:01:25 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 4 00:01:25 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 4 00:01:25 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 4 00:01:25 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 4 00:01:25 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 4 00:01:25 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 4 00:01:25 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 4 00:01:58 linux pppoe[13343]: Timeout waiting for PADO packets
Jan 4 00:01:58 linux pppd[13342]: Modem hangup
Jan 4 00:01:58 linux pppd[13342]: Connection terminated.
Jan 4 00:01:58 linux pppd[13342]: Script /usr/sbin/pppoe -I eth0 -T 80 1412 -S BLICNET-VRB1 finished (pid 13343), status = 0x1
Jan 4 00:02:21 linux pppd[13342]: Terminating on signal 2
Jan 4 00:02:21 linux pppd[13342]: Exit.
Jan 4 00:04:42 linux pppd[13811]: pppd 2.4.3 started by potajac, uid 0
Jan 4 00:04:42 linux pppd[13811]: Serial connection established.
Jan 4 00:04:42 linux pppd[13811]: Using interface ppp1
Jan 4 00:04:42 linux pppd[13811]: Connect: ppp1 <--> /dev/pts/2
Jan 4 00:05:02 linux pppd[13811]: Terminating on signal 2
Jan 4 00:05:02 linux pppd[13811]: Modem hangup
Jan 4 00:05:02 linux pppd[13811]: Connection terminated.
Jan 4 00:05:02 linux pppd[13811]: Child process /usr/sbin/pppoe -I eth0 -T 80 1412 -S BLICNET-VRB1 (pid 13812) terminated with signal 2
Jan 4 00:05:02 linux pppd[13811]: Exit.
Jan 6 15:43:32 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:43:32 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:43:32 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:43:32 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:43:32 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:43:32 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:43:32 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:43:32 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:43:32 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:43:32 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:45:14 linux pppd[7086]: pppd 2.4.3 started by potajac, uid 0
Jan 6 15:45:14 linux pppd[7086]: Serial connection established.
Jan 6 15:45:14 linux pppd[7086]: Using interface ppp0
Jan 6 15:45:14 linux pppd[7086]: Connect: ppp0 <--> /dev/pts/2
Jan 6 15:45:49 linux pppoe[7094]: Timeout waiting for PADO packets
Jan 6 15:45:49 linux pppd[7086]: Modem hangup
Jan 6 15:45:49 linux pppd[7086]: Connection terminated.
Jan 6 15:45:49 linux pppd[7086]: Script /usr/sbin/pppoe -I eth0 -T 80 1412 -S BLICNET-VRB1 finished (pid 7094), status = 0x1
Jan 6 15:46:39 linux pppd[7086]: Terminating on signal 2
Jan 6 15:46:39 linux pppd[7086]: Modem hangup
Jan 6 15:46:39 linux pppd[7086]: Connection terminated.
Jan 6 15:46:39 linux pppd[7086]: Exit.
Jan 6 15:47:04 linux pppd[7730]: pppd 2.4.3 started by potajac, uid 0
Jan 6 15:47:04 linux pppd[7730]: Serial connection established.
Jan 6 15:47:04 linux pppd[7730]: Using interface ppp0
Jan 6 15:47:04 linux pppd[7730]: Connect: ppp0 <--> /dev/pts/2
Jan 6 15:47:39 linux pppoe[7731]: Timeout waiting for PADO packets
Jan 6 15:47:39 linux pppd[7730]: Modem hangup
Jan 6 15:47:39 linux pppd[7730]: Connection terminated.
Jan 6 15:47:39 linux pppd[7730]: Script /usr/sbin/pppoe -I eth0 -T 80 1412 -S BLICNET-VRB1 finished (pid 7731), status = 0x1
Jan 6 15:48:12 linux pppd[7730]: Terminating on signal 2
Jan 6 15:48:12 linux pppd[7730]: Modem hangup
Jan 6 15:48:12 linux pppd[7730]: Connection terminated.
Jan 6 15:48:12 linux pppd[7730]: Exit.
Jan 6 15:48:33 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:48:33 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:48:33 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:48:33 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:48:33 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:48:33 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:48:33 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:48:33 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:48:33 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:48:33 linux init: cannot execute "/usr/local/sbin/pppoe-blic.sh"
Jan 6 15:49:10 linux pppd[8113]: pppd 2.4.3 started by potajac, uid 0
Jan 6 15:49:10 linux pppd[8113]: using channel 3
Jan 6 15:49:10 linux pppd[8113]: Using interface ppp0
Jan 6 15:49:10 linux pppd[8113]: Connect: ppp0 <--> /dev/pts/2
Jan 6 15:49:11 linux pppd[8113]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
Jan 6 15:49:13 linux pppd[8113]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
Jan 6 15:49:15 linux pppd[8113]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
Jan 6 15:49:17 linux pppd[8113]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
Jan 6 15:49:19 linux pppd[8113]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
Jan 6 15:49:21 linux pppd[8113]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
Jan 6 15:49:23 linux pppd[8113]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
Jan 6 15:49:25 linux pppd[8113]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
Jan 6 15:49:27 linux pppd[8113]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
Jan 6 15:49:29 linux pppd[8113]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
Jan 6 15:49:31 linux pppd[8113]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
Jan 6 15:49:33 linux pppd[8113]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
Jan 6 15:49:35 linux pppd[8113]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
Jan 6 15:49:37 linux pppd[8113]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
Jan 6 15:49:39 linux pppd[8113]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
Jan 6 15:49:41 linux pppd[8113]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
Jan 6 15:49:43 linux pppd[8113]: sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x720b3df7>]
Jan 6 15:49:45 linux pppoe[8114]: Timeout waiting for PADO packets
Jan 6 15:49:45 linux pppd[8113]: Modem hangup
Jan 6 15:49:45 linux pppd[8113]: Connection terminated.
Jan 6 15:49:45 linux pppd[8113]: Script /usr/sbin/pppoe -p /var/run/pppoe.conf-pppoe.pid.pppoe -I eth0 -T 80 -U -m 1412 -D /tmp/pppoe-debug-8038/pppoe-debug.txt-0 finished (pid 8114), status = 0x1
Jan 6 15:49:45 linux pppd[8113]: Exit.
Fri Jan 6 15:49:45 CET 2006
---------------------------------------------
* The following section is a dump of the packets
* sent and received by rp-pppoe. If you don't see
* any output, it's an Ethernet driver problem. If you only
* see three PADI packets and nothing else, check your cables
* and modem. Make sure the modem lights flash when you try
* to connect. Check that your Ethernet card is in
* half-duplex, 10Mb/s mode. If all else fails,
* try using pppoe-sniff.
rp-pppoe debugging dump
rp-pppoe-3.7
15:49:10.238 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
SourceAddr 00:0b:6a:1f:6a:cc DestAddr ff:ff:ff:ff:ff:ff
01 01 00 00 01 03 00 04 b2 1f 00 00 ............

15:49:15.237 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
SourceAddr 00:0b:6a:1f:6a:cc DestAddr ff:ff:ff:ff:ff:ff
01 01 00 00 01 03 00 04 b2 1f 00 00 ............

15:49:25.236 SENT PPPoE Discovery (8863) PADI sess-id 0 length 12
SourceAddr 00:0b:6a:1f:6a:cc DestAddr ff:ff:ff:ff:ff:ff
01 01 00 00 01 03 00 04 b2 1f 00 00 ............



e sada sledeca zanimljiva stvar je da sam nakon malo cackanja , pitaj boga cega vise dobio ovakav odgovor na komandu pppoe-status:



linux:/home/potajac # pppoe-status
Note: You have enabled demand-connection; pppoe-status may be inaccurate.
pppoe-status: Link is up and running on interface ppp0
ppp0 Link encap:Point-to-Point Protocol
inet addr:217.23.199.XX P-t-P:217.23.207.129 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1450 Metric:1
RX packets:7 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:2 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:55 (55.0 b) TX bytes:171 (171.0 b)


znaci da sam se konektovao cim mi je dodijelio IP ali kada probam pingat google dosta mu treba da izbaci da ga ne moze naci a ne kao inace odmah ..


P.S. izvinjavam se zbog predugackog posta

 
Odgovor na temu

Ned123
Nenad Bošnjak
Senior System Administrator
PIXOMONDO Images
Stuttgart, Germany

Član broj: 64971
Poruke: 835
*.broadband.blic.net.

Sajt: www.linkedin.com/in/nenad..


+28 Profil

icon Re: wireless i pppoe konekcija 06.01.2006. u 16:56 - pre 222 meseci
Link bi ti tebao biti u redu. Još uvijek imaš blicove skripte u sistemu, izbaci sve to.
Ja na čist suse 9.1 i 10.0 (inače koristim Slackware, a na njemu je to malo komplikovanije), instaliram iz sorsa rp-pppoe, otkucam pppoe-setup, odgovorim na pitanja, dodam već pomenutu opciju u pppoe.conf, otkucam pppoe-start i eto me na internetu.
Rp-pppoe skini sa:
http://www.roaringpenguin.com/penguin/open_source_rp-pppoe.php
a ne sa susetovog repozitorija.
PS: Za dugačke fajlove upotrebi opciju "Upload uz poruku".

[Ovu poruku je menjao Ned123 dana 06.01.2006. u 18:03 GMT+1]
 
Odgovor na temu

potajaco
Aleksandar Potajac
Banja Luka

Član broj: 48034
Poruke: 40
*.broadband.blic.net.



Profil

icon Re: wireless i pppoe konekcija 06.01.2006. u 17:27 - pre 222 meseci
ma znam da imam scripte, posle sam ih izbacio ali jos uvjek ne radi ....
ukucam pppoe-status i dobijem kao ono gore .... stvarno ne kontam ..... izgleda kao da sam konektovan, dobijem svoj IP ali ne mogu ni pingat

P.S.
namjerno nisam hteo upload :)
 
Odgovor na temu

Zeleni Obad

Član broj: 17621
Poruke: 78
*.broadband.blic.net.



Profil

icon Re: wireless i pppoe konekcija06.01.2006. u 21:49 - pre 222 meseci
Ako dodjeljuje dinamicki IP - imas vezu; daj rute i uredjaje s "ifconfig" i "netstat -rn" da pogledamo to malo. Usput, SuSE 9.3 dodje s podrskom za pppoe i MPPE, tako da nisi morao to cackati/brinuti :)
 
Odgovor na temu

Ned123
Nenad Bošnjak
Senior System Administrator
PIXOMONDO Images
Stuttgart, Germany

Član broj: 64971
Poruke: 835
*.broadband.blic.net.

Sajt: www.linkedin.com/in/nenad..


+28 Profil

icon Re: wireless i pppoe konekcija 06.01.2006. u 22:50 - pre 222 meseci
Citat:
Zeleni Obad: Usput, SuSE 9.3 dodje s podrskom za pppoe i MPPE, tako da nisi morao to cackati/brinuti :)

Ne znam zašto, ali ja se, čak i na suse 10.0, nisam mogao konektovati sa susetovim rp-pppoe. Tek kad sam sa Slackware particije prebacio kompajlirane fajlove za rp-pppoe sve je proradilo (na Susetu nisam imao development pakete u tom momentu).
Citat:
potajaco: ma znam da imam scripte, posle sam ih izbacio ali jos uvjek ne radi ....
ukucam pppoe-status i dobijem kao ono gore .... stvarno ne kontam ..... izgleda kao da sam konektovan, dobijem svoj IP ali ne mogu ni pingat

Jesi li podesio DNS servere? Unesi ih u toku pppoe-setup.

[Ovu poruku je menjao Ned123 dana 06.01.2006. u 23:55 GMT+1]
 
Odgovor na temu

Zeleni Obad

Član broj: 17621
Poruke: 78
*.broadband.blic.net.



Profil

icon Re: wireless i pppoe konekcija 07.01.2006. u 01:43 - pre 222 meseci
Pa, ne znam za roaming penguin-a [nikada nisam koristio taj program za konektovanje] ali sam siguran da SuSE 9.3 (i 9.2 i 9.1) imaju podrsku u kernelu za pppoe i za MPPE.

Ako je "nakacio" kao sto se vidi iz onog loga, onda samo treba vidjeti da mozda firewall ne pravi problem (mislim da je SuSEfirewall2 u pitanju u tom linux-u, po "default"-u) ili mozda bas resolv.conf nema pravilan nameserver, ili rute nisu dobro podesene, ali da sacekamo da okaci jos ifconfig i netstat, pa da onda vidimo...
 
Odgovor na temu

Zeleni Obad

Član broj: 17621
Poruke: 78
*.broadband.blic.net.



Profil

icon Re: wireless i pppoe konekcija07.01.2006. u 06:04 - pre 222 meseci
@potajaco: btw, za drugu skriptu, tu "od druga" :), iza SSID-a dodaj u nastavku jos i "-D dumplog.txt" da vidimo sta se desava s pregovorima modema :D
 
Odgovor na temu

potajaco
Aleksandar Potajac
Banja Luka

Član broj: 48034
Poruke: 40
*.broadband.blic.net.



Profil

icon Re: wireless i pppoe konekcija 07.01.2006. u 13:09 - pre 222 meseci

linux:/home/potajac # ifconfig
eth0 Link encap:Ethernet HWaddr 00:0B:6A:1F:6A:CC
inet addr:192.168.2.6 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::20b:6aff:fe1f:6acc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:155 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:14288 (13.9 Kb)
Interrupt:3 Base address:0xcf00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:72 errors:0 dropped:0 overruns:0 frame:0
TX packets:72 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4664 (4.5 Kb) TX bytes:4664 (4.5 Kb)

ppp1 Link encap:Point-to-Point Protocol
inet addr:10.112.112.112 P-t-P:10.112.112.113 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b



linux:/home/potajac # netstat -rn
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
10.112.112.113 0.0.0.0 255.255.255.255 UH 0 0 0 ppp1
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 10.112.112.113 0.0.0.0 UG 0 0 0 ppp1




evo ti netstat i ifconfig a probacu da dodam tu liniju :)

 
Odgovor na temu

Zeleni Obad

Član broj: 17621
Poruke: 78
*.broadband.blic.net.



Profil

icon Re: wireless i pppoe konekcija07.01.2006. u 17:46 - pre 222 meseci
Sad ne vidim dodjeljeni IP (zato sto ga nije ni dodjelio kada si pozvao provajdera, je li... :)) a interfejs koji je naveden je ppp1. Zakljucujem da si koristio rp-pppoe prije pozivanja provajdera s "ppp call datoteka". Probaj ponovo, samo ovaj put "ocisti" sve daemone koji mozda rade u backgroundu prije "poziva" s: "# killall -9 pppd", pa tek onda probaj "ppp call". :D
 
Odgovor na temu

potajaco
Aleksandar Potajac
Banja Luka

Član broj: 48034
Poruke: 40
*.broadband.blic.net.



Profil

icon Re: wireless i pppoe konekcija 08.01.2006. u 20:04 - pre 222 meseci
pozdrav svima .....

evo upravo sam uspeo da se nakacim ali mi nije jasno kako ..... sve sam radio kao inace i odjednom probao da pingam google i dobio odziv ;)
sad se bojim iskljucit jer se mozda necu moci opet konektovat :) :) :) :)

ned123 i Zeleni Obad zahvaljujem na pomoci :)
 
Odgovor na temu

Zeleni Obad

Član broj: 17621
Poruke: 78
*.broadband.blic.net.



Profil

icon Re: wireless i pppoe konekcija09.01.2006. u 02:59 - pre 222 meseci
:) valjda ce te talasi wireless-a posluziti; *nixi hoce - za uptime i stabilnost ne brini :) Vjerovatno si nehotice pravio konekciju cas s rp-om, cas s "direkt" s ppp daemonom; ovo je moglo da zeza firewall. Pripazi, dakle, uvijek, koji "node" trenutno ostvaruje konekciju (ppp0, ppp1...) - mislim da si sve bio fino podesio, samo te to malo bunilo...

[Ovu poruku je menjao Zeleni Obad dana 09.01.2006. u 04:01 GMT+1]
 
Odgovor na temu

Zeleni Obad

Član broj: 17621
Poruke: 78
*.broadband.blic.net.



Profil

icon Re: wireless i pppoe konekcija09.01.2006. u 03:26 - pre 222 meseci
Sad citam ovo sto napisah gore: radi se, naime, o cistom baljezganju :D , izuzev u dva slucaja - prvi, da je taj comp zapravo samo firewall/router (a nije, jer naglasio bi to negdje gore, zar ne? :)), i drugom, da comp automatski podize firewall pri boot-anju (a ovaj nije podesen sa $WAN-om kao eksternim interface-om, pa ti "ne da" prolaz i ako se "konektujes"), pa je sto trebas dodati samo "obaranje: firewall-a prije konekcije, te podizanje firewall-a nakon (ovo ako je comp router ili imas potrebu za firewall-om zbog servisa koji rade na tom compu); dakle samo u skripte [link-up, ili kako god se vec zovu ili ih nazoves] ili rucno obaraj i podizi podeseni firewall sa "# SuSEfirewall2 stop" i "# SuSEfirewall2 start". Mislim da te ovo zeza, najverovatnije...
 
Odgovor na temu

Zeleni Obad

Član broj: 17621
Poruke: 78
*.broadband.blic.net.



Profil

icon Re: wireless i pppoe konekcija 09.01.2006. u 05:33 - pre 222 meseci
Upravo sam pregledao neke svoje stare postove; ako koristis firewall, provjeri imas li slicnu/ovu liniju:

$IPT -t nat -A POSTROUTING -O $WAN -j MASQUERADE

SuSEfirewall2 koristis, naravno, ili si instalirao nesto drugo? :)

p.s. $WAN je, naravno, ppp0 ili interfejs preko kog god ti vec ide veza...
 
Odgovor na temu

potajaco
Aleksandar Potajac
Banja Luka

Član broj: 48034
Poruke: 40
*.broadband.blic.net.



Profil

icon Re: wireless i pppoe konekcija 09.01.2006. u 15:07 - pre 222 meseci
e ovako .. firewall uvjek oborim prije pozivanja one scriptice .... a dignem ga posle .....

medjutim desilo mi se ono cega sam se i bojao ... kada sam se nakacio prvi put veza mi je pucala par puta i konektovao sam se ponovo uspjesno .... sada uopste ne mogu vise da se konektujem .... oborim firelewall , pozovem scriptu uradim ifconfig i ne pise da mi je digao ppp0 ..... uopste ne kuzim zasto ..... probao sam posle toga da startujem pppoe-start i onda pogledam ifconfig i dignut je ppp1 .... sve mi se cini da se ppp0 vuce negde u pozadini pokusavajuci da ostvari vezu ......

ako imas neku ideju javi :)

pozdrav....
 
Odgovor na temu

potajaco
Aleksandar Potajac
Banja Luka

Član broj: 48034
Poruke: 40
*.broadband.blic.net.



Profil

icon Re: wireless i pppoe konekcija 09.01.2006. u 15:52 - pre 222 meseci
evo uspeo sam opet da se nakacim ali veza mi puca svakih 15-20 minuta ....

fazon je u tome da nakon poziva scripte sacekam koji minut i tek onda startujem pppoe ..... zvuci glupo ali tako je :)

jel ima neki nacin da odrzim vezu stalnom, dakle da dodam jos nesto u onu scriptu ..... Z O ti si govorio da se to moze uraditi :) poz
 
Odgovor na temu

Zeleni Obad

Član broj: 17621
Poruke: 78
*.broadband.blic.net.



Profil

icon Re: wireless i pppoe konekcija 09.01.2006. u 16:56 - pre 222 meseci
Samo jedan "virtual device" je potreban za konekciju - dakle, ili pozivaj s "rp-pppoe start", ili s "pppd call provajder"; svaki od njih pravi sljedeci virutal device, tj, ako rp-pppoe vec "radi", tj. povezuje u background-u preko, recimo, ppp0, ako potom probas ostvariti konekciju i preko pppd-a, kucajuci "pppd call 'ime-datoteke-u-/etc/ppp/peers'", napravice se novi "virutal device" koji ce vjerovatno da dobije numeraciju za broj vise (dakle, ppp1), i tako redom. Ovo ti zbunjuje firewall, kroz koji se ujedno i rutiraju paketi, i nemas konekciju iako ti pise da ti je dodijelilo IP kad provjeris uredjaje i rute mreza. Dakle, samo jedan poziv (menja sve :))!
Veza puca poslije 10-tak, 15 min jer - puca veza! Tesko da je to do linuxa/skripti (sem ako explicitno ne navedes u nekoj skripti da raskine vezu poslije odredjenog perioda; nisi to uradio? :)) Ako je to konstantno, sve sto mozes je:
a) kupis Mikrotik za 300EUR i miran si :))) (probas, naravno, prije kupovine, dan-dva, cisto da vidis da li je bilo do uredjaja)
b) bolja antena?
c) skripte (muka pravi majstora :)) - napisi nesto sto provjerava, recimo, ping i rekonektuje se ako je ping, recimo, peti put u razmaku od par sekundi prevelik; ili, napravi rekonekciju neovisno o kvalitetu veze (svakih 14min :)), uvali to u cron ili pokreci rucno, i rjesena stvar [zakrpljena, bolje receno :)].
 
Odgovor na temu

[es] :: Linux :: wireless i pppoe konekcija

Strane: 1 2

[ Pregleda: 9799 | Odgovora: 32 ] > FB > Twit

Postavi temu Odgovori

Navigacija
Lista poslednjih: 16, 32, 64, 128 poruka.