Stranica: 7/12.

Re: WLAN Iskon problem.

Postano: 01 stu 2012, 13:23
Postao/la Heisenberg
nakon stavljene komande, output je:

Kod: Označi sve

Selecting previously unselected package pppoe.
(Reading database ... 141965 files and directories currently installed.)
Unpacking pppoe (from pppoe_3.8-3ubuntu1_amd64.deb) ...
Setting up pppoe (3.8-3ubuntu1) ...
Processing triggers for man-db ...

Re: WLAN Iskon problem.

Postano: 01 stu 2012, 13:25
Postao/la shicy
mora bit još outputa

Re: WLAN Iskon problem.

Postano: 01 stu 2012, 13:26
Postao/la Heisenberg
Shicy je napisao/la:mora bit još outputa
nema nista drugo.

Re: WLAN Iskon problem.

Postano: 01 stu 2012, 13:26
Postao/la iweb
@shicy - mislim da nakon triggera za man-db je završena instalacija paketa i da ga vrati nazad u shell
simke je napisao/la:ja to radom ovako.
konfiguriras pppoe sa (pppoe ili rp-pppoe paket)

Kod: Označi sve

sudo pppoe-setup
napravis skriptu /etc/ppp/ip-pre-up

Kod: Označi sve

#!/bin/sh
/sbin/route del default
i chmod-as je da je može izvšavat. i onda

Kod: Označi sve

pppoe-start
naravno, spojen na wlan prije pppoe-start.
Shicy je napisao/la:sve ti piše.
ovo chmodanje ti je ovo:

Kod: Označi sve

sudo chmod +x /etc/ppp/ip-pre-up

Re: WLAN Iskon problem.

Postano: 01 stu 2012, 13:29
Postao/la Heisenberg

Kod: Označi sve

matej@matej-Aspire-7551:~$ sudo pppoe-setup
Welcome to the Roaring Penguin PPPoE client setup.  First, I will run
some checks on your system to make sure the PPPoE client is installed
properly...

Oh, dear, I don't see the file '/etc/ppp/pppoe.conf' anywhere.  Please
re-install the PPPoE client.

Re: WLAN Iskon problem.

Postano: 01 stu 2012, 13:49
Postao/la Heisenberg
matej je napisao/la:

Kod: Označi sve

matej@matej-Aspire-7551:~$ sudo pppoe-setup
Welcome to the Roaring Penguin PPPoE client setup.  First, I will run
some checks on your system to make sure the PPPoE client is installed
properly...

Oh, dear, I don't see the file '/etc/ppp/pppoe.conf' anywhere.  Please
re-install the PPPoE client.
kako da reinstaliram pppoe client?

Re: WLAN Iskon problem.

Postano: 01 stu 2012, 14:28
Postao/la zole052
ukucaj

Kod: Označi sve

sudo gedit /etc/ppp/pppoe.conf
u njega pastaj ovo

Kod: Označi sve

#***********************************************************************
#
# pppoe.conf
#
# Configuration file for rp-pppoe.  Edit as appropriate and install in
# /etc/ppp/pppoe.conf
#
# NOTE: This file is used by the pppoe-start, pppoe-stop, pppoe-connect and
#       pppoe-status shell scripts.  It is *not* used in any way by the
#       "pppoe" executable.
#
# Copyright (C) 2000 Roaring Penguin Software Inc.
#
# This file may be distributed under the terms of the GNU General
# Public License.
#
# LIC: GPL
# $Id$
#***********************************************************************

# When you configure a variable, DO NOT leave spaces around the "=" sign.

# Ethernet card connected to DSL modem
ETH=eth1

# PPPoE user name.  You may have to supply "@provider.com"  Sympatico
# users in Canada do need to include "@sympatico.ca"
# Sympatico uses PAP authentication.  Make sure /etc/ppp/pap-secrets
# contains the right username/password combination.
# For Magma, use xxyyzz@magma.ca
USER=bxxxnxnx@sympatico.ca

# Bring link up on demand?  Default is to leave link up all the time.
# If you want the link to come up on demand, set DEMAND to a number indicating
# the idle time after which the link is brought down.
DEMAND=no
#DEMAND=300

# DNS type: SERVER=obtain from server; SPECIFY=use DNS1 and DNS2;
# NOCHANGE=do not adjust.
DNSTYPE=SERVER

# Obtain DNS server addresses from the peer (recent versions of pppd only)
# In old config files, this used to be called USEPEERDNS.  Changed to
# PEERDNS for better Red Hat compatibility
PEERDNS=yes

DNS1=
DNS2=

# Make the PPPoE connection your default route.  Set to
# DEFAULTROUTE=no if you don't want this.
DEFAULTROUTE=yes

### ONLY TOUCH THE FOLLOWING SETTINGS IF YOU'RE AN EXPERT

# How long pppoe-start waits for a new PPP interface to appear before
# concluding something went wrong.  If you use 0, then pppoe-start
# exits immediately with a successful status and does not wait for the
# link to come up.  Time is in seconds.
#
# WARNING WARNING WARNING:
#
# If you are using rp-pppoe on a physically-inaccessible host, set
# CONNECT_TIMEOUT to 0.  This makes SURE that the machine keeps trying
# to connect forever after pppoe-start is called.  Otherwise, it will
# give out after CONNECT_TIMEOUT seconds and will not attempt to
# connect again, making it impossible to reach.
CONNECT_TIMEOUT=30

# How often in seconds pppoe-start polls to check if link is up
CONNECT_POLL=2

# Specific desired AC Name
ACNAME=

# Specific desired service name
SERVICENAME=

# Character to echo at each poll.  Use PING="" if you don't want
# anything echoed
PING="."

# File where the pppoe-connect script writes its process-ID.
# Three files are actually used:
#   $PIDFILE       contains PID of pppoe-connect script
#   $PIDFILE.pppoe contains PID of pppoe process
#   $PIDFILE.pppd  contains PID of pppd process
CF_BASE=`basename $CONFIG`
PIDFILE="/var/run/$CF_BASE-pppoe.pid"

# Do you want to use synchronous PPP?  "yes" or "no".  "yes" is much
# easier on CPU usage, but may not work for you.  It is safer to use
# "no", but you may want to experiment with "yes".  "yes" is generally
# safe on Linux machines with the n_hdlc line discipline; unsafe on others.
SYNCHRONOUS=no

# Do you want to clamp the MSS?  Here's how to decide:
# - If you have only a SINGLE computer connected to the DSL modem, choose
#   "no".
# - If you have a computer acting as a gateway for a LAN, choose "1412".
#   The setting of 1412 is safe for either setup, but uses slightly more
#   CPU power.
CLAMPMSS=1412
#CLAMPMSS=no

# LCP echo interval and failure count.
LCP_INTERVAL=20
LCP_FAILURE=3

# PPPOE_TIMEOUT should be about 4*LCP_INTERVAL
PPPOE_TIMEOUT=80

# Firewalling: One of NONE, STANDALONE or MASQUERADE
FIREWALL=NONE

# Linux kernel-mode plugin for pppd.  If you want to try the kernel-mode
# plugin, use LINUX_PLUGIN=/etc/ppp/plugins/rp-pppoe.so
LINUX_PLUGIN=

# Any extra arguments to pass to pppoe.  Normally, use a blank string
# like this:
PPPOE_EXTRA=""

# Rumour has it that "Citizen's Communications" with a 3Com
# HomeConnect DSL Modem DualLink requires these extra options:
# PPPOE_EXTRA="-f 3c12:3c13 -S ISP"

# Any extra arguments to pass to pppd.  Normally, use a blank string
# like this:
PPPD_EXTRA=""


########## DON'T CHANGE BELOW UNLESS YOU KNOW WHAT YOU ARE DOING
# If you wish to COMPLETELY overrride the pppd invocation:
# Example:
# OVERRIDE_PPPD_COMMAND="pppd call dsl"

# If you want pppoe-connect to exit when connection drops:
# RETRY_ON_FAILURE=no
snimi i to je to pa ponovo pokreni pppoe-setup

Re: WLAN Iskon problem.

Postano: 01 stu 2012, 14:52
Postao/la Heisenberg
sta da stavim za interface?
INTERFACE

>>> Enter the Ethernet interface connected to the DSL modem
For Solaris, this is likely to be something like /dev/hme0.
For Linux, it will be ethn, where 'n' is a number.
(default eth0):

Re: WLAN Iskon problem.

Postano: 01 stu 2012, 15:00
Postao/la zole052
matej je napisao/la:sta da stavim za interface?
INTERFACE

>>> Enter the Ethernet interface connected to the DSL modem
For Solaris, this is likely to be something like /dev/hme0.
For Linux, it will be ethn, where 'n' is a number.
(default eth0):
jel ti ne citas sto ti govorimo
http://www.linuxzasve.com/forum/viewtop ... 30#p116102
ili ti neradi sa eth0?

Re: WLAN Iskon problem.

Postano: 01 stu 2012, 15:02
Postao/la Heisenberg
zole052 je napisao/la:
matej je napisao/la:sta da stavim za interface?
INTERFACE

>>> Enter the Ethernet interface connected to the DSL modem
For Solaris, this is likely to be something like /dev/hme0.
For Linux, it will be ethn, where 'n' is a number.
(default eth0):
jel ti ne citas sto ti govorimo
http://www.linuxzasve.com/forum/viewtop ... 30#p116102
ili ti neradi sa eth0?
stigao sam do passworda, i kad pisem, nis se ne vidi, tj. ne pojavljuje se nista na ekranu..