Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

pppoe with vyatta and external modem

Posted on 2011-03-08
6
Medium Priority
?
3,741 Views
Last Modified: 2012-05-11
I have Vyatta 6.1 running. I have an ethernet cable connected from my Vyatta to my external modem.

I have successfully managed to log in and get assigned my local and remote IP from my ISP. However I still do not seem to have any internet connectivity. I can not ping from my vyatta box to the outside world

Below is my configuration

interfaces {
    ethernet eth0 {
        duplex auto
        hw-id bc:30:5b:cf:96:84
        pppoe 0 {
            default-route auto
            mtu 1492
            name-server auto
            password ****************
            user-id email@hq43.btclick.com
        }
        smp_affinity auto
        speed auto
    }
    ethernet eth1 {
        address 192.168.0.150/24
        duplex auto
        hw-id bc:30:5b:cf:96:85
        smp_affinity auto
        speed auto
    }
    ethernet eth2 {
        duplex auto
        hw-id 00:10:18:94:42:48
        smp_affinity auto
        speed auto
    }
    ethernet eth3 {
        duplex auto
        hw-id 00:10:18:94:42:4a
        smp_affinity auto
        speed auto
    }
    loopback lo {
    }
}
service {
    nat {
        rule 2 {
            outbound-interface pppoe0
            source {
                address 192.168.0.0/16
            }
            type masquerade
        }
    }
    ssh {
        port 7711
        protocol-version v2
    }
}
system {
    host-name vyatta
    login {
        user vyatta {
            authentication {
                encrypted-password ****************
            }
            level admin
        }
    }
    ntp-server 0.vyatta.pool.ntp.org
    package {
        auto-sync 1
        repository community {
            components main
            distribution stable
            password ****************
            url http://packages.vyatta.com/vyatta
            username ""
        }
    }
    syslog {
        global {
            facility all {
                level notice
            }
            facility protocols {
                level debug
            }
        }
    }
    time-zone GMT
}

My routing table

vyatta@vyatta:~$ show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
       I - ISIS, B - BGP, > - selected route, * - FIB route

K>* 0.0.0.0/0 is directly connected, pppoe0
C>* 81.134.96.1/32 is directly connected, pppoe0
C>* 127.0.0.0/8 is directly connected, lo
C>* 192.168.0.0/24 is directly connected, eth1
C>* 192.168.1.0/24 is directly connected, eth0



Here is my ppoe details

vyatta@vyatta:~$ show interfaces pppoe pppoe0
pppoe0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1492 qdisc pfifo_fast state UNKNOWN qlen 100
    link/ppp
    inet 81.134.102.203 peer 81.134.96.1/32 scope global pppoe0

    RX:  bytes    packets     errors    dropped    overrun      mcast
            64          4          0          0          0          0
    TX:  bytes    packets     errors    dropped    carrier collisions
         17925        258          0          0          0          0

vyatta@vyatta:~$

I need to get this setup quick so employees can move into their new office. So any help is appreciated.

Thanks
0
Comment
Question by:saiyen_2002
  • 4
  • 2
6 Comments
 
LVL 35

Expert Comment

by:Duncan Roe
ID: 35081261
I am not familiar with the show command.
What is the output from ip route list?
Also why does show ip route claim eth0 is connected to network 192.168.1.0/24 but the devices listing does not give it an address?
What is this "show" command anyway?
0
 

Author Comment

by:saiyen_2002
ID: 35081667
Duncan, show is the command used from vyatta interface to show configurations.

Re the eth0 showing 192.168.1.0/24, that is my mistake in copying and pasting.

ip route list gives me

vyatta@vyatta:~$ ip route list
default dev pppoe0  scope link
81.134.96.1 dev pppoe0  proto kernel  scope link  src 81.130.76.103
127.0.0.0/8 dev lo  proto kernel  scope link  src 127.0.0.1
192.168.0.0/24 dev eth1  proto kernel  scope link  src 192.168.0.150
192.168.1.0/24 dev eth0  proto kernel  scope link  src 192.168.1.150

Open in new window


The address is DHCP from the ISP so it is different from above.

This is my /etc/ppp/peers/ppoe0

# Configuration file for PPP, using PPP over Ethernet (PPPOE)
# to connect to a DSL provider.
#
# This configuration file is automatically generated by the Vyatta
# configuration templates.  Please do not manually edit it.

# Default parameters not set by Vyatta templates:
#
# Require peer to provide the local IP address if it is not
# specified explicitly in the config file.
noipdefault

# Don't show the password in logfiles:
hide-password

# Standard Link Control Protocol (LCP) parameters:
lcp-echo-interval 20
lcp-echo-failure 3

# RFC 2516, paragraph 7 mandates that the following options MUST NOT be
# requested and MUST be rejected if requested by the peer:
# Address-and-Control-Field-Compression (ACFC)
noaccomp

# Asynchronous-Control-Character-Map (ACCM)
default-asyncmap

# Override any connect script that may have been set in /etc/ppp/options.
connect /bin/true

# Don't try to authenticate the remote node
noauth

# Don't try to proxy ARP for the remote endpoint. User can set proxy
# arp entries up manually if they wish.  More importantly, having
# the "proxyarp" parameter set disables the "defaultroute" option.
noproxyarp

# Parameters set or changed by the Vyatta templates go here:

pty "/usr/sbin/pppoe -m 1412 -I eth0"
ipparam pppoe0
debug
logfile /var/log/vyatta/ppp_pppoe0.log
mtu 1492
mru 1492
usepeerdns
password "mypassword"
user "email@hg43.btclick.com"
persist
defaultroute

Open in new window





0
 

Author Comment

by:saiyen_2002
ID: 35081692
Here is also the output of my logfile /var/log/vyatta/ppp_pppoe0.log

Wed Mar  9 10:38:31 GMT 2011: Starting PPP daemon for pppoe0
Serial connection established.
using channel 64
Using interface ppp0
Connect: ppp0 <--> /dev/pts/0
sent [LCP ConfReq id=0x1 <mru 1492> <magic 0x655a8641> <pcomp>]
rcvd [LCP ConfReq id=0x2a <mru 1492> <auth chap MD5> <magic 0x722fcacf>]
lcp_reqci: returning CONFACK.
sent [LCP ConfAck id=0x2a <mru 1492> <auth chap MD5> <magic 0x722fcacf>]
rcvd [LCP ConfRej id=0x1 <pcomp>]
sent [LCP ConfReq id=0x2 <mru 1492> <magic 0x655a8641>]
rcvd [LCP ConfAck id=0x2 <mru 1492> <magic 0x655a8641>]
sent [LCP EchoReq id=0x0 magic=0x655a8641]
rcvd [CHAP Challenge id=0x1 <5f9bc561a84ea0fa94124157ccba8def>, name = "bras-red5.l-ste"]
sent [CHAP Response id=0x1 <0cae32034072665eb1cf4578b4b973cd>, name = "c711241@hg43.btclick.com"]
rcvd [LCP EchoRep id=0x0 magic=0x722fcacf]
rcvd [LCP ConfReq id=0x2 <auth chap MD5> <magic 0x5f03c891>]
sent [LCP ConfReq id=0x3 <mru 1492> <magic 0xe60babd5> <pcomp>]
lcp_reqci: returning CONFACK.
sent [LCP ConfAck id=0x2 <auth chap MD5> <magic 0x5f03c891>]
rcvd [LCP ConfAck id=0x3 <mru 1492> <magic 0xe60babd5> <pcomp>]
sent [LCP EchoReq id=0x0 magic=0xe60babd5]
rcvd [CHAP Challenge id=0x2 <8647e7653c1b073eabf67a6d73efd960>, name = "R21CBIRLNS03"]
sent [CHAP Response id=0x2 <0842b0f5dc63c17b68a1be5b64ee8719>, name = "c711241@hg43.btclick.com"]
rcvd [CHAP Success id=0x2 ""]
CHAP authentication succeeded
CHAP authentication succeeded
sent [CCP ConfReq id=0x1 <deflate 15> <deflate(old#) 15> <bsd v1 15>]
sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
rcvd [IPCP ConfReq id=0x1 <addr 81.134.96.1>]
ipcp: returning Configure-ACK
sent [IPCP ConfAck id=0x1 <addr 81.134.96.1>]
rcvd [LCP ProtRej id=0x3 80 fd 01 01 00 11 1a 04 78 00 18 04 78 00 15 03 2f]
Protocol-Reject for 'Compression Control Protocol' (0x80fd) received
rcvd [IPCP ConfRej id=0x1 <compress VJ 0f 01>]
sent [IPCP ConfReq id=0x2 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
rcvd [IPCP ConfNak id=0x2 <addr 81.130.76.103> <ms-dns1 194.72.0.114> <ms-dns3 62.6.40.178>]
sent [IPCP ConfReq id=0x3 <addr 81.130.76.103> <ms-dns1 194.72.0.114> <ms-dns3 62.6.40.178>]
rcvd [IPCP ConfAck id=0x3 <addr 81.130.76.103> <ms-dns1 194.72.0.114> <ms-dns3 62.6.40.178>]
ipcp: up
Script /etc/ppp/ip-pre-up started (pid 3561)
Script /etc/ppp/ip-pre-up finished (pid 3561), status = 0x0
local  IP address 81.130.76.103
remote IP address 81.134.96.1
primary   DNS address 194.72.0.114
secondary DNS address 62.6.40.178
Script /etc/ppp/ip-up started (pid 3582)
Script /etc/ppp/ip-up finished (pid 3582), status = 0x0

Open in new window


0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
LVL 35

Expert Comment

by:Duncan Roe
ID: 35087821
Can you ping either DNS?
e.g. ping -c1 194.72.0.114 or ping -c1 62.6.40.178
0
 

Accepted Solution

by:
saiyen_2002 earned 0 total points
ID: 35088188
Ok, I have figured it out. It was a problem with my Neatgear modem. I had to change my multiplexing method from VC to LLC.

A bit weird, when I had the Netgear in modem+router mode it worked fine in VC mode.
0
 

Author Closing Comment

by:saiyen_2002
ID: 35126393
I figured it out at the end
0

Featured Post

Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article is a collection of issues that people face from time to time and possible solutions to those issues. I hope you enjoy reading it.
This article will show how Aten was able to supply easy management and control for Artear's video walls and wide range display configurations of their newsroom.
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

886 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question