Network problems

You think you have found a bug? Let us know about it.
doll0x032
Posts: 9
Joined: 23. Nov 2015, 13:39

Re: Network problems

Post by doll0x032 »

Yes, this is the way I do it: pppoe-setup -- configuring(once at the beginning), pppoe-start -- gettin up the network. I tried to write pppoe-start at the end of /etc/rc.d/rc.local but it did not work correctly.
doll0x032
Posts: 9
Joined: 23. Nov 2015, 13:39

Re: Network problems

Post by doll0x032 »

You were right about WICD. I had this problem with DNS another time, but this time connection was revived when I stoped WICD (service stop wicd). So I uninstalled it and now the problem was finally solved.
westms
Posts: 298
Joined: 17. Mar 2013, 18:51

Re: Network problems

Post by westms »

doll0x032 wrote:You were right about WICD. I had this problem with DNS another time, but this time connection was revived when I stoped WICD (service stop wicd). So I uninstalled it and now the problem was finally solved.
doll0x032 wrote:You were right about WICD. I had this problem with DNS another time, but this time connection was revived when I stoped WICD (service stop wicd). So I uninstalled it and now the problem was finally solved.
Hello.

Would you be so kind and show the contents of the files:
/etc/ppp/pppoe.conf , /etc/ppp/options , /etc/ppp/resolv.conf and /etc/rc.d/rc.inet1.conf .

Also I'm interested in the output of the command ifconfig ethN , after the interface is up and the connection is established, where N should be replaced with the interface number. Real existing IP and MAC addresses and user names in the files and the output you should mask then.

Thanks in advance


(This whole discussion could be moved to Misc or Problems, because it is not specifically a Salix error.)
doll0x032
Posts: 9
Joined: 23. Nov 2015, 13:39

Re: Network problems

Post by doll0x032 »

Hello!
Excuse my silence.
pppoe.conf:

Code: Select all

# Ethernet card connected to DSL modem
ETH='eth0'

# 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='my-user-name'

# 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=SPECIFY

# 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=no

DNS1=8.8.8.8
DNS2=8.8.4.4

# 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=STANDALONE

# 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=""
/etc/ppp/options:

uncommented items are:
asyncmap 0
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. On Ultrix, this option implies hardware
# flow control, as for the crtscts option. (This option is not fully
# implemented.)
modem

proxyarp
lcp-echo-interval 30
lcp-echo-failure 4

/etc/resolv.conf:
nameserver 8.8.8.8
nameserver 8.8.4.4

/etc/rc.d/rc.inet1.conf:
I have not redacted this file,, so it looks like
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]=""
DHCP_HOSTNAME[0]="", and so on
.........
.........

ifconfig eth0:
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.3 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 addr prefixlen 64 scopeid 0x20<link>
ether addr txqueuelen 1000 (Ethernet)
RX packets 6000 bytes 5060825 (4.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4585 bytes 630787 (616.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Post Reply