You are not logged in.

#1 2011-04-07 15:30:09

na3r
Member
Registered: 2011-04-07
Posts: 12

[SOLVED] problem to connect to internet

hi guys
i'm newbi to arch . today i've installed arch properly :-) but i can't connect to internet .
i used this direction to setup pppoe
https://wiki.archlinux.org/index.php/PP … _with_pppd

when i ping google.com i get the host unknown error.

sorry for my bad english.

Last edited by na3r (2011-04-26 14:44:19)

Offline

#2 2011-04-07 16:27:46

Thor@Flanders
Member
Registered: 2010-08-27
Posts: 266

Re: [SOLVED] problem to connect to internet

Okay, some suggestions....

Ping yourself with 127.0.0.1, if you get resposes, your stack is okay, your network works
Get the IP address of a server/host somewhere and ping that...try to ping the DNS server of your provider...
See if your DNS server is set up properly...

Of course, and this may not be to your liking...an external modem works miracles...I use a Dlink, just setting up an IP address, and setting stuff inside the modem and bam, on to the Net...

Luck

Thor

Offline

#3 2011-04-07 20:44:58

na3r
Member
Registered: 2011-04-07
Posts: 12

Re: [SOLVED] problem to connect to internet

Ping yourself with 127.0.0.1, if you get resposes, your stack is okay, your network works
my network is working properly. reply from 127.0.0.1

Get the IP address of a server/host somewhere and ping that
ping google.com. response is destination host unreachable

try to ping the DNS server of your provider

this is my /etc/resolve.conf

nameserver  213.217.60.170
nameserver  213.217.60.172

ping 213.217.60.170 -> response is destination host unreachable

and ifconfig result

ppp1 link enscape:point-to-point protocol
inet addr:97.99.208.150    p-t-p:97.99.208.1 mask:255.255.255.255

ping 97.99.208.150 -> it wroks and reply response

i don't  know what is wrong !

Offline

#4 2011-04-07 21:22:58

hexanol
Member
From: Canaduh
Registered: 2009-08-04
Posts: 95

Re: [SOLVED] problem to connect to internet

na3r wrote:

ppp1 link enscape:point-to-point protocol
inet addr:97.99.208.150    p-t-p:97.99.208.1 mask:255.255.255.255

ping 97.99.208.150 -> it wroks and reply response

i don't  know what is wrong !

Well, that's normal that it pings since this IP address is your IP address, not the remote IP address.

That said, if you can ping 97.99.208.1, it would be a more useful information.

Else, your default route is probably not set to something meaningful (you can check it with ip route or route -n).

Offline

#5 2011-04-08 01:43:28

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,744

Re: [SOLVED] problem to connect to internet

Okay, Connect through ppp, try these commands, and post the output
ping 66.211.214.131  This will ping arxhlinux.org.  It will prove whether this is a DNS or a routing problem
ifconfig  You did this before, but the address information is probably stale by now
route -n  Hexanol is spot on about this one


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Online

#6 2011-04-08 05:54:38

na3r
Member
Registered: 2011-04-07
Posts: 12

Re: [SOLVED] problem to connect to internet

result of route -n

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
91.99.208.1     0.0.0.0         255.255.255.255 UH    0      0        0 ppp1
192.168.1.0     0.0.0.0         255.255.255.0   U     202    0        0 eth0
0.0.0.0         192.168.1.1     0.0.0.0         UG    202    0        0 eth0
ewaller wrote:

ping 66.211.214.131  This will ping arxhlinux.org.  It will prove whether this is a DNS or a routing problem

response is destination host unreachable

Offline

#7 2011-04-08 06:10:35

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,744

Re: [SOLVED] problem to connect to internet

The default gateway is 192.168.0.1.  Unfortunately, 192.*.*.* is a class C private network.  Almost every home router uses that address range.  The router performs NAT translation to map from the private network to the internet.  Your internet address is 91.99.208.1, but there is no gateway that tells your system to use that route for internet traffic.

I am not certain from whence the 192.168.1.0 route comes, but it should be changed.  It is probably in /etc/rc.conf.  There should be a way to identify the gateway when setting up ppp.  I do not use PPP, My ISB uses DHCP through a DSL link.

I'm not sure about the exact syntax, but you need to add a default gateway.  I think the command is  route add default gw 91.99.208.1   Take a close look at the man page for route.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Online

#8 2011-04-08 06:20:13

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,744

Re: [SOLVED] problem to connect to internet

Are you connected to a separate network through a wired Network Interface?
Also, look at the Routing section in the man for pppd.

Regardless, I am almost certain your problem lies in the routing table not knowing where to send default packets.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Online

#9 2011-04-08 07:13:44

na3r
Member
Registered: 2011-04-07
Posts: 12

Re: [SOLVED] problem to connect to internet

here is my rc.conf

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.UTF-8"
HARDWARECLOCK="localtime"
TIMEZONE="Asia/Tehran"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="myhost"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
# 
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#

#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(eth0)

# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
 
# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng network netfs crond)

ifconfig

eth0      Link encap:Ethernet  HWaddr 20:CF:30:C5:C0:57  
          inet addr:192.168.1.11  Bcast:255.255.255.255  Mask:255.255.255.0
          inet6 addr: fe80::22cf:30ff:fec5:c057/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:181 errors:0 dropped:0 overruns:0 frame:0
          TX packets:194 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:26112 (25.5 Kb)  TX bytes:10986 (10.7 Kb)
          Interrupt:37 

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:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:1692 (1.6 Kb)  TX bytes:1692 (1.6 Kb)

ppp0      Link encap:Point-to-Point Protocol  
          inet addr:91.99.208.111  P-t-P:91.99.208.1  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1492  Metric:1
          RX packets:7 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3 
          RX bytes:454 (454.0 b)  TX bytes:61 (61.0 b)

my adsl modem's ip is 192.168.1.1

Offline

#10 2011-04-09 00:01:03

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,744

Re: [SOLVED] problem to connect to internet

Sorry I did not get back to you sooner.  I've spent the day demonstrating to a major chip maker that they have an issue with the SPI interface on their latest chip.

I've been looking at your configuration and I am a bit confused.  You have a a DSL modem that is connecting to and is acquiring an address from the internet.  It is providing a private network (192.168.1.*)  It has an address, on that private network of 192.168.1.1.  It should provide a gateway of 192.168.1.0 providing NAT to the internet.

That the modem is serving a class C private network makes me believe that it is handling all of the PPP stuff. 

I think we are both being distracted by the pppd setup on the Arch box.  Unless I am missing something, it should not be required in the first place.

If I am missing something, then maybe a little more detail on your network would be helpful. 

If not
-- back out all the PPPD stuff
-- just use dhcpd to get an address from the modem (You already are). 
-- See if the modem provides a web interface by browsing to 192.168.1.1.
-- If so, use that interface to see if it is connecting to the net and getting an address.

Then lets fo from there.


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Online

#11 2011-04-26 14:45:17

na3r
Member
Registered: 2011-04-07
Posts: 12

Re: [SOLVED] problem to connect to internet

tnx , it's solved with

route add default gw gw-ip

Offline

Board footer

Powered by FluxBB