ADSL connection via RHL 90

I just installed RHL90, as workstation, and connected to our internal LAN.
Now, I tried to connect to the net via our ADSL. But failed, via Mozilla
browser, sendmail, or any other. The ADSL's IP number as default gateway was
already put into the routing table.
I can ping to the external IP number of my ISP ( i.e. 202.134.0.155 ), but
not to any external IP number ( e.g. 18.7.22.69 ). When I ping-ed to
external FQDN, it always said something like "...unknown host...".
Have I done something wrong during the installation? Where should I check
first?
Could somebody please help me?

My data is as follows :

Result of ifconfig :
eth0 Link encap:Ethernet HWaddr 00:0C:6E:6B:4E:C2
inet addr:10.234.16.101 Bcast:10.234.16.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4818 errors:0 dropped:0 overruns:0 frame:0
TX packets:502 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:583229 (569.5 Kb) TX bytes:42296 (41.3 Kb)
Interrupt:12 Base address:0xd000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:62168 errors:0 dropped:0 overruns:0 frame:0
TX packets:62168 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4244648 (4.0 Mb) TX bytes:4244648 (4.0 Mb)

( note : 10.234.16.101 is my workstation's IP number. )

Result of route -v as follows :

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
10.234.16.0 * 255.255.255.0 U 0 0 0 eth0
169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 10.234.16.99 0.0.0.0 UG 0 0 0 eth0

route -C

Kernel IP routing cache
Source Destination Gateway Flags Metric Ref Use
Iface
fxrhl90 acbiserver.acbi acbiserver.acbi 0 0 17 eth0
fxrhl90 10.0.0.6 10.234.16.99 0 0 1 eth0
10.234.16.117 10.234.16.255 10.234.16.255 ibl 0 0 5 lo
fxrhl90 255.255.255.255 255.255.255.255 bl 0 0 9 eth0
10.234.16.100 10.234.16.255 10.234.16.255 ibl 0 0 2 lo
fxrhl90 10.234.16.104 10.234.16.104 0 0 2 eth0
10.234.16.135 10.234.16.255 10.234.16.255 ibl 0 0 14 lo
10.234.16.104 fxrhl90 fxrhl90 il 0 0 17 lo
10.234.16.105 10.234.16.255 10.234.16.255 ibl 0 0 1 lo
10.234.16.112 10.234.16.255 10.234.16.255 ibl 0 0 1 lo
10.234.16.104 10.234.16.255 10.234.16.255 ibl 0 0 0 lo
acbiserver.acbi fxrhl90 fxrhl90 il 0 0 25 lo
fxrhl90 fxrhl90 fxrhl90 l 0 0 98 lo
fxrhl90 10.234.16.104 10.234.16.104 0 0 2 eth0
fxrhl90 10.234.16.255 10.234.16.255 bl 0 0 2 eth0
fxrhl90 fxrhl90 fxrhl90 l 0 0 35 lo
fxrhl90 10.0.0.6 10.234.16.99 0 0 0 eth0
10.234.16.99 fxrhl90 fxrhl90 il 0 0 0 lo
acbiserver.acbi 10.234.16.255 10.234.16.255 ibl 0 0 0 lo
fxrhl90 acbiserver.acbi acbiserver.acbi 0 0 27 eth0

( note : fxrhl90 is the name of my workstation )

netstat -r :

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt
Iface
10.234.16.0 * 255.255.255.0 U 0 0 0
eth0
169.254.0.0 * 255.255.0.0 U 0 0 0
eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 10.234.16.99 0.0.0.0 UG 0 0 0
eth0

( note : I didn't input this 169.254.0.0 number; where does it come from ? )

Data from /etc/sysconfig/networking/devices/eth0.route as follows :

GATEWAY1=10.234.16.99
NETMASK1=255.255.0.0
ADDRESS1=202.134.2.5
GATEWAY0=10.234.16.99
NETMASK0=255.255.0.0
ADDRESS0=202.134.0.155

Data from /etc/sysconfig/networking/devices/ifcfg-eth0 :

DEVICE=eth0
BOOTPROTO=none
BROADCAST=10.234.16.255
IPADDR=10.234.16.101
NETMASK=255.255.255.0
NETWORK=10.234.16.0
ONBOOT=yes
HWADDR=00:0c:6e:6b:4e:c2
USERCTL=no
PEERDNS=no
GATEWAY=10.234.16.99
TYPE=Ethernet

Yours,


Frans T.

P.S.
Sorry for the use of bandwidth


------------------------------------------------------------ ----------------

This information is confidential and legally privileged. If you are not the
intended recipient, (i) please do not read or disclose to others,
(ii) please notify the sender by reply mail, and (iii) please delete this
communication from your system. Any review, retransmission, dissemination
or other use of, or taking of any action in reliance upon, this information
by persons or entities other than the intended recipient is prohibited.
Thank you for your cooperation.
------------------------------------------------------------ ----------------



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: ADSL connection via RHL 90

GA Dept PT ACBI wrote:

> Data from /etc/sysconfig/networking/devices/ifcfg-eth0 :
>
> DEVICE=eth0
> BOOTPROTO=none
> BROADCAST=10.234.16.255
> IPADDR=10.234.16.101
> NETMASK=255.255.255.0
> NETWORK=10.234.16.0
> ONBOOT=yes
> HWADDR=00:0c:6e:6b:4e:c2
> USERCTL=no
> PEERDNS=no
> GATEWAY=10.234.16.99
> TYPE=Ethernet
>

Does your ISP have its own DNS servers? If so, you might need to use dhcpcd (some
ISPs require you to use their own DNS servers to reduce network load.)

> Yours,
>
>
> Frans T.
>
> P.S.
> Sorry for the use of bandwidth
>
>
> ------------------------------------------------------------ ----------------
>
> This information is confidential and legally privileged. If you are not the
> intended recipient, (i) please do not read or disclose to others,
> (ii) please notify the sender by reply mail, and (iii) please delete this
> communication from your system. Any review, retransmission, dissemination
> or other use of, or taking of any action in reliance upon, this information
> by persons or entities other than the intended recipient is prohibited.
> Thank you for your cooperation.
> ------------------------------------------------------------ ----------------
>

Might want to kill this message for mail sent to publicly-accesable mailing lists.

Jim
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: ADSL connection via RHL 90

GA Dept PT ACBI wrote:
> I just installed RHL90, as workstation, and connected to our internal LAN.
> Now, I tried to connect to the net via our ADSL. But failed, via Mozilla
> browser, sendmail, or any other. The ADSL's IP number as default gateway was
> already put into the routing table.
> I can ping to the external IP number of my ISP ( i.e. 202.134.0.155 ), but
> not to any external IP number ( e.g. 18.7.22.69 ). When I ping-ed to
> external FQDN, it always said something like "...unknown host...".
> Have I done something wrong during the installation? Where should I check
> first?
> Could somebody please help me?
>
> My data is as follows :
>
> Result of ifconfig :
> eth0 Link encap:Ethernet HWaddr 00:0C:6E:6B:4E:C2
> inet addr:10.234.16.101 Bcast:10.234.16.255 Mask:255.255.255.0

> ( note : 10.234.16.101 is my workstation's IP number. )
>
> Result of route -v as follows :
>
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 10.234.16.0 * 255.255.255.0 U 0 0 0 eth0
> 169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
> 127.0.0.0 * 255.0.0.0 U 0 0 0 lo
> default 10.234.16.99 0.0.0.0 UG 0 0 0 eth0
>

> netstat -r :
>
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS Window irtt
> Iface
> 10.234.16.0 * 255.255.255.0 U 0 0 0
> eth0
> 169.254.0.0 * 255.255.0.0 U 0 0 0
> eth0
> 127.0.0.0 * 255.0.0.0 U 0 0 0 lo
> default 10.234.16.99 0.0.0.0 UG 0 0 0
> eth0
>
> ( note : I didn't input this 169.254.0.0 number; where does it come from ? )
>
> Data from /etc/sysconfig/networking/devices/eth0.route as follows :
>
> GATEWAY1=10.234.16.99
> NETMASK1=255.255.0.0
> ADDRESS1=202.134.2.5
> GATEWAY0=10.234.16.99
> NETMASK0=255.255.0.0
> ADDRESS0=202.134.0.155
>

> Yours,
>
>
> Frans T.
>
> P.S.
> Sorry for the use of bandwidth

Hi, Frans:

10.234.16.101 fxrhl90 workstation's LAN interface
10.234.16.99 ? gateway's LAN interface
202.134.0.155 nsjkt1.telkom.net.id gateway's WAN interface ?
202.134.2.5 ns2.telkom.net.id a DNS server

I assume that the host's (gateway, that has the DSL modem attached?)
interfaces are
10.234.16.99 on the LAN and
202.134.0.155 on its ppp# interface and
that it is routing 10.234.16.0<>0.0.0.0
using a netmask of 255.x.x.0 or similar.

Can you ping the gateway's external interface by IP address?
"I can ping to the external IP number of my ISP ( i.e. 202.134.0.155 )"
I assume that 202.134.0.155 is the IP address of the gateway's
external interface and the answer is yes.

Can you ping 202.134.2.5 or 203.130.196.6 ?
(ns1.telkom.net.id or ns2.telkom.net.id)

For ping'ing by FQDN you will need 202.134.2.5 (or similar)
in /etc/resolv.conf (or RedHat equivilant).

Do you have access to 10.234.16.99?

What assumptions of mine are incorrect?

HTH, Chuck

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: ADSL connection via RHL 90

Comments interspersed.

At 03:14 PM 2/15/2005 +0700, GA Dept PT ACBI wrote:

>I just installed RHL90, as workstation, and connected to our internal LAN.
>Now, I tried to connect to the net via our ADSL. But failed, via Mozilla
>browser, sendmail, or any other. The ADSL's IP number as default gateway was
>already put into the routing table.

I don't quite understand this last sentence. The gateway number should be
the LAN address of your router ... probably 10.234.16.99, based on what you
report below ... not (for example) the public address by which that router
(probably) connects to the Internet via ADSL (or, even worse, the router's
gateway address).

Hosts (including routers) have IP addresses; ADSL circuits do not.

>I can ping to the external IP number of my ISP ( i.e. 202.134.0.155 ), but
>not to any external IP number ( e.g. 18.7.22.69 ). When I ping-ed to
>external FQDN, it always said something like "...unknown host...".

Preliminary comment: When asking for technical help, never tell us what the
response is "something like". Take the time to write it down and tell us
what it actually is, and the exact command it is response to.

Now ... you say first that you cannot ping to "any external IP number", but
then refer to "external FQDN". Have you tested pinging an address ("( e.g.
18.7.22.69 )") or not? If not, please do ... in that case, James'
suggestion that you have a DNS problem is probably on target. But if you
cannot ping actual addresses, you probably have a routing problem of some
sort, not a DNS problem.

Finally, what do you mean by "the external IP number of my ISP ( i.e.
202.134.0.155 )"? Is that the external IP address of the router your
systems sees as "10.234.16.99", the adress of that system's gateway (from
its routing table), or something else?

>Have I done something wrong during the installation? Where should I check
>first?
>Could somebody please help me?
>
>My data is as follows :
>
>Result of ifconfig :
>eth0 Link encap:Ethernet HWaddr 00:0C:6E:6B:4E:C2
> inet addr:10.234.16.101 Bcast:10.234.16.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:4818 errors:0 dropped:0 overruns:0 frame:0
> TX packets:502 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:583229 (569.5 Kb) TX bytes:42296 (41.3 Kb)
> Interrupt:12 Base address:0xd000
>lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:62168 errors:0 dropped:0 overruns:0 frame:0
> TX packets:62168 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:4244648 (4.0 Mb) TX bytes:4244648 (4.0 Mb)
>
>( note : 10.234.16.101 is my workstation's IP number. )

This looks fine.

>Result of route -v as follows :
>
>Kernel IP routing table
>Destination Gateway Genmask Flags Metric Ref Use
>Iface
>10.234.16.0 * 255.255.255.0 U 0 0 0 eth0
>169.254.0.0 * 255.255.0.0 U 0 0 0 eth0
>127.0.0.0 * 255.0.0.0 U 0 0 0 lo
>default 10.234.16.99 0.0.0.0 UG 0 0 0 eth0

Is "10.234.16.99" the right address for your gateway (default route) or
not? Assuming it is, this part looks OK too.

> route -C
>
>Kernel IP routing cache
>Source Destination Gateway Flags Metric Ref Use
>Iface
>fxrhl90 acbiserver.acbi acbiserver.acbi 0 0 17 eth0
>fxrhl90 10.0.0.6 10.234.16.99 0 0 1 eth0
>10.234.16.117 10.234.16.255 10.234.16.255 ibl 0 0 5 lo
>fxrhl90 255.255.255.255 255.255.255.255 bl 0 0 9 eth0
>10.234.16.100 10.234.16.255 10.234.16.255 ibl 0 0 2 lo
>fxrhl90 10.234.16.104 10.234.16.104 0 0 2 eth0
>10.234.16.135 10.234.16.255 10.234.16.255 ibl 0 0 14 lo
>10.234.16.104 fxrhl90 fxrhl90 il 0 0 17 lo
>10.234.16.105 10.234.16.255 10.234.16.255 ibl 0 0 1 lo
>10.234.16.112 10.234.16.255 10.234.16.255 ibl 0 0 1 lo
>10.234.16.104 10.234.16.255 10.234.16.255 ibl 0 0 0 lo
>acbiserver.acbi fxrhl90 fxrhl90 il 0 0 25 lo
>fxrhl90 fxrhl90 fxrhl90 l 0 0 98 lo
>fxrhl90 10.234.16.104 10.234.16.104 0 0 2 eth0
>fxrhl90 10.234.16.255 10.234.16.255 bl 0 0 2 eth0
>fxrhl90 fxrhl90 fxrhl90 l 0 0 35 lo
>fxrhl90 10.0.0.6 10.234.16.99 0 0 0 eth0
>10.234.16.99 fxrhl90 fxrhl90 il 0 0 0 lo
>acbiserver.acbi 10.234.16.255 10.234.16.255 ibl 0 0 0 lo
>fxrhl90 acbiserver.acbi acbiserver.acbi 0 0 27 eth0
>
>( note : fxrhl90 is the name of my workstation )

This looks OK too.

> netstat -r :
>
>Kernel IP routing table
>Destination Gateway Genmask Flags MSS Window irtt
>Iface
>10.234.16.0 * 255.255.255.0 U 0 0 0
>eth0
>169.254.0.0 * 255.255.0.0 U 0 0 0
>eth0
>127.0.0.0 * 255.0.0.0 U 0 0 0 lo
>default 10.234.16.99 0.0.0.0 UG 0 0 0
>eth0
>
>( note : I didn't input this 169.254.0.0 number; where does it come from ? )

Probably something RH does by default. There's an RFC standard for
self-assignment of IP addresses (by DHCP clients that do not get a
response) that reserves this network. Systems are sopposed to ... or at
least allowed to ... pick a random address in this range for themselves.
It's intended to handle hubless connections between 2 isolated hosts, such
as a field connection between 2 laptops or a laptop connected to a
workstation. I never actually see Linux systems uses this option, but all
Windows systems do.


>Data from /etc/sysconfig/networking/devices/eth0.route as follows :
>
>GATEWAY1=10.234.16.99
>NETMASK1=255.255.0.0
>ADDRESS1=202.134.2.5
>GATEWAY0=10.234.16.99
>NETMASK0=255.255.0.0
>ADDRESS0=202.134.0.155

What do the addresses in "ADDRESS1" and "ADDRESS0" refer to?

>Data from /etc/sysconfig/networking/devices/ifcfg-eth0 :
>
>DEVICE=eth0
>BOOTPROTO=none
>BROADCAST=10.234.16.255
>IPADDR=10.234.16.101
>NETMASK=255.255.255.0
>NETWORK=10.234.16.0
>ONBOOT=yes
>HWADDR=00:0c:6e:6b:4e:c2
>USERCTL=no
>PEERDNS=no
>GATEWAY=10.234.16.99
>TYPE=Ethernet

I don't offhand know where RH places config values for DNS servers. Since
you are doing a manual config (not using DHCP), you need to provide them
manually. The standard place is in /etc/resolv.conf ... I don't know if RH
does this directly or uses a config file to create this one during
boot/init. (In addition, I don't know what "PEERDNS=no" means in the above
file ... perhaps someone who is more experienced than I with the RH config
procedure can jump in here.)


>Yours,
>
>
>Frans T.
>
>P.S.
>Sorry for the use of bandwidth

Nothing to be sorry for. Technical questions require proper descriptions
and, except for the concern in my initial comment, your is close to a model
of how prople should pose them.

>
>
>----------------------------------------------------------- -----------------
>
>This information is confidential and legally privileged. If you are not the
>intended recipient, (i) please do not read or disclose to others,
>(ii) please notify the sender by reply mail, and (iii) please delete this
>communication from your system. Any review, retransmission, dissemination
>or other use of, or taking of any action in reliance upon, this information
>by persons or entities other than the intended recipient is prohibited.
>Thank you for your cooperation.
>----------------------------------------------------------- -----------------

No, it's not any of this, not when you post to a public mailing list. As a
matter of form (my boilerplate can lick your boilerplate), I reject the
notion that I am obligated to any specific actions by the posting of such
boilerplate nonsense at the end of messages sent to public mailing lists.


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

RE: ADSL connection via RHL 90

Many thanks for your comments,

# fx >
# fx > Does your ISP have its own DNS servers? If so, you might need to use
# fx > dhcpcd (some
# fx > ISPs require you to use their own DNS servers to reduce network
# fx > load.)

Yes, 202.134.0.155 and 202.134.2.5 are DNS servers of our ISP. I already
inputted those into the /etc/resolv.conf :

resolv.conf :
search telkom.net
nameserver 10.234.16.10
nameserver 202.134.0.155
nameserver 202.134.2.5

( note : 10.234.16.10 is DNS server in my internal/LAN )

# fx > dhcpcd (some

If I still have to set dhcpcd, then, how should I do that ?

Yours,


Frans T.

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

RE: ADSL connection via RHL 90

# fx > Hi, Frans:
# fx >
# fx > 10.234.16.101 fxrhl90 workstation's LAN interface
# fx > 10.234.16.99 ? gateway's LAN interface
# fx > 202.134.0.155 nsjkt1.telkom.net.id gateway's WAN interface
# fx > ?
# fx > 202.134.2.5 ns2.telkom.net.id a DNS server

Yes, you are right.
10.234.16.99 is IP number of ADSL router ( = default gateway ) in our LAN
202.134.0.155 and 202.134.2.5 are DNS servers of our ISP

# fx > I assume that the host's (gateway, that has the DSL modem
# fx > attached?)
# fx > interfaces are
# fx > 10.234.16.99 on the LAN and
# fx > 202.134.0.155 on its ppp# interface and
# fx > that it is routing 10.234.16.0<>0.0.0.0
# fx > using a netmask of 255.x.x.0 or similar.

Yes . . .

# fx > Can you ping the gateway's external interface by IP address?
# fx > "I can ping to the external IP number of my ISP ( i.e. 202.134.0.155
# fx > )"
# fx > I assume that 202.134.0.155 is the IP address of the gateway's
# fx > external interface and the answer is yes.

You already answered a yes.

# fx > Can you ping 202.134.2.5 or 203.130.196.6 ?
# fx > (ns1.telkom.net.id or ns2.telkom.net.id)

Yes, to the number of the ISP ( 202.134.2.5 ).
No, to other numbers ( 203.130.196.6, and other numbers ).
Also, a big no to other names.

# fx > For ping'ing by FQDN you will need 202.134.2.5 (or similar)
# fx > in /etc/resolv.conf (or RedHat equivilant).

It's already there ! :
resolv.conf :
search telkom.net
nameserver 10.234.16.10
nameserver 202.134.0.155
nameserver 202.134.2.5

( note : 10.234.16.10 is my internal DNS server )

# fx > Do you have access to 10.234.16.99?

Of course, see above. I can also connect to it.

Thank you, anyway. But, I still can't see the world via my RHL90
( Btw, my router is Draytek Vigor 2500, is it somehow incompatible with
Linux ? )

Regards,


Frans T.

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

RE: ADSL connection via RHL 90

# fx > I don't quite understand this last sentence. The gateway number
# fx > should be
# fx > the LAN address of your router ... probably 10.234.16.99, based on

Yes, you are right.

# fx > what you
# fx > report below ... not (for example) the public address by which that
# fx > router
# fx > (probably) connects to the Internet via ADSL (or, even worse, the
# fx > router's
# fx > gateway address).

# fx > Preliminary comment: When asking for technical help, never tell us
# fx > what the
# fx > response is "something like". Take the time to write it down and tell
# fx > us
# fx > what it actually is, and the exact command it is response to.


# fx > Now ... you say first that you cannot ping to "any external IP
# fx > number", but
# fx > then refer to "external FQDN". Have you tested pinging an address ("(
# fx > e.g.
# fx > 18.7.22.69 )") or not? If not, please do ... in that case, James'

Already tried to ping to other IP numbers, but failed. I could only ping to
IP numbers of DNS servers of our ISP ( and even then, not to their names ).


# fx > Probably something RH does by default. There's an RFC standard for

Many thanks for your info.

# fx > >Data from /etc/sysconfig/networking/devices/eth0.route as follows :
# fx > >
# fx > >GATEWAY1=10.234.16.99
# fx > >NETMASK1=255.255.0.0
# fx > >ADDRESS1=202.134.2.5
# fx > >GATEWAY0=10.234.16.99
# fx > >NETMASK0=255.255.0.0
# fx > >ADDRESS0=202.134.0.155
# fx >
# fx > What do the addresses in "ADDRESS1" and "ADDRESS0" refer to?

IP numbers of my ISP.

Very many thanks,


Frans T.


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

RE: ADSL connection via RHL 90

At 11:09 AM 2/16/2005 +0700, frans toruan wrote:
>[...]
># fx > Preliminary comment: When asking for technical help, never tell us
># fx > what the
># fx > response is "something like". Take the time to write it down and tell
># fx > us
># fx > what it actually is, and the exact command it is response to.

Please take to heart the comment I made above. Below, you say a ping
"failed", but you do not provide the sort of details I was trying to ask
you to provide.

Please tell us the *exact* command you entered and the *exact* message ping
provided when it failed. pings fail in at least 4 distinct ways I can think
of, *not* counting DNS issues, and the message you get from ping will help
me, or someone here, figure out what is going on in your case.

You might also try a traceroute and see how far it gets. If you want help
interpreting that, don't even think about providing anything short of the
complete output of the process.

># fx > Now ... you say first that you cannot ping to "any external IP
># fx > number", but
># fx > then refer to "external FQDN". Have you tested pinging an address ("(
># fx > e.g.
># fx > 18.7.22.69 )") or not? If not, please do ... in that case, James'
>
>Already tried to ping to other IP numbers, but failed. I could only ping to
>IP numbers of DNS servers of our ISP ( and even then, not to their names ).
[...]


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

Re: ADSL connection via RHL 90

Comments embedded.
frans toruan wrote:
> # fx > Hi, Frans:
> # fx >
> # fx > 10.234.16.101 fxrhl90 workstation's LAN interface
> # fx > 10.234.16.99 ? gateway's LAN interface
> # fx > 202.134.0.155 nsjkt1.telkom.net.id gateway's WAN interface
> # fx > ?
> # fx > 202.134.2.5 ns2.telkom.net.id a DNS server
>
> Yes, you are right.

? No, I am not right. 202.134.0.155 is an external DNS server and
not the router's WAN interface IP address.

> 10.234.16.99 is IP number of ADSL router ( = default gateway ) in our LAN
> 202.134.0.155 and 202.134.2.5 are DNS servers of our ISP
>
> # fx > I assume that the host's (gateway, that has the DSL modem
> # fx > attached?)
> # fx > interfaces are
> # fx > 10.234.16.99 on the LAN and
> # fx > 202.134.0.155 on its ppp# interface and
> # fx > that it is routing 10.234.16.0<>0.0.0.0
> # fx > using a netmask of 255.x.x.0 or similar.
>
> Yes . . .

? No, 202.134.0.155 is an external DNS server and not the IP address
of the router's interface.

> # fx > Can you ping the gateway's external interface by IP address?
> # fx > "I can ping to the external IP number of my ISP ( i.e. 202.134.0.155
> # fx > )"
> # fx > I assume that 202.134.0.155 is the IP address of the gateway's
> # fx > external interface and the answer is yes.
>
> You already answered a yes.

? No, I do not know what is the IP address of the router's external
interface.

> # fx > Can you ping 202.134.2.5 or 203.130.196.6 ?
> # fx > (ns1.telkom.net.id or ns2.telkom.net.id)
>
> Yes, to the number of the ISP ( 202.134.2.5 ).
> No, to other numbers ( 203.130.196.6, and other numbers ).
> Also, a big no to other names.

I think that since you can ping your external DNS servers,
your router is routing packets LAN<>WAN.

> # fx > For ping'ing by FQDN you will need 202.134.2.5 (or similar)
> # fx > in /etc/resolv.conf (or RedHat equivilant).
>
> It's already there ! :
> resolv.conf :
> search telkom.net
> nameserver 10.234.16.10
> nameserver 202.134.0.155
> nameserver 202.134.2.5

Try:
ping -c 1 202.134.0.12
ping -c 1 66.94.234.13

Try using only one of these DNSs at a time, then:
ping -c 1 telkom.net.id
ping -c 1 yahoo.com

traceroute 202.134.0.12
traceroute 66.94.234.13
traceroute telkom.net.id
traceroute yahoo.com

> ( note : 10.234.16.10 is my internal DNS server )

Whereas the Draytek router can DNS, using an internal DNS
server inside the LAN wmay slow down (1st time) DNS
queries and increase LAN traffic.

> # fx > Do you have access to 10.234.16.99?

Oh, I see below that it is a hardware box.

> Of course, see above. I can also connect to it.

http://10/234.16.99 ?

> Thank you, anyway. But, I still can't see the world via my RHL90
> ( Btw, my router is Draytek Vigor 2500, is it somehow incompatible with
> Linux ? )

( Why do you ask this, does it work with other operating systems and
not this RedHat workstation ? )

http://www.draytek.co.uk/products/vigor2500.html

(btw, No. It doesn't know or care what o/s is in use.)

Is DNS enabled on the Draytek router?

Is its web setup interface accessed via http://10.234.16.99:80
or similar?

HTH, Chuck

> Regards,
>
>
> Frans T.



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

RE: ADSL connection via RHL 90

# fx > Please tell us the *exact* command you entered and the *exact*
# fx > message ping

Sorry, truly.

These are exact results of ping via RHL :


ping 202.134.0.155 -c 1 :
PING 202.134.0.155(202.134.0.155) 56(84) bytes of data.
64 bytes from 202.134.0.155: icmp_seq=1 ttl=61 time=375 ms

--- 202.134.0.155 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 375.192/375.192/375.192/0.000 ms
( note : 202.134.0.155 is IP number of ISP's DNS server )

ping nsjkt1.telkom.net.id -c 1 :
ping: unknown host nsjkt1.telkom.net.id


ping 202.134.2.5 -c 1 :
PING 202.134.2.5(202.134.2.5) 56(84) bytes of data.
64 bytes from 202.134.2.5: icmp_seq=1 ttl=248 time=407 ms

--- 202.134.2.5 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 407.694/407.694/407.694/0.000 ms
( note : 202.134.2.5 is IP number of ISP's DNS server )


ping ns1.telkom.net.id -c 1 :
ping: unknown host ns1.telkom.net.id


ping 203.130.196.6 -c 1 :
PING 203.130.196.6(203.130.196.6) 56(84) bytes of data.

--- 203.130.196.6 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
( note : 202.134.196.6 is IP number of ISP's DNS server )

ping ns2.telkom.net.id -c 1 :
ping: unknown host ns2.telkom.net.id


ping 18.7.22.69 -c 1 :
PING 18.7.22.69(18.7.22.69) 56(84) bytes of data.

--- 18.7.22.69 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms


ping mit.edu -c 1 :
ping: unknown host mit.edu


Regards,


Frans T.


-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

RE: ADSL connection via RHL 90

OK. In the list below, the ones that involve FQDNs are all returning errors
tha indicate a DNS problem. If I am right in recalling that you can ping
the ISP's DNS server themselves by their addresses, I would suggest you see
if removing the on-LAN DNS server from the list in /etc/resolv.conf fixes
this problem. In theory, a host is supposed to check all the DNS servers in
the list, but I've found the practice to be a bit less reliable. You
**might** simply be seeing a result where the on-LAN DNS server cannot
resolve off-LAN addresses.

If that turns out to be the case, post again and I, or others, can suggest
options for dealing with this. (The easiest is to reconfigure the on-LAN
DNS server so it can do off-LAN name resolution as well as on-LAN, for
example by using the ISP's DNS servers as forwarders.)

Below, I comment on the pings by address.

At 04:35 PM 2/16/2005 +0700, frans toruan wrote:


># fx > Please tell us the *exact* command you entered and the *exact*
># fx > message ping
>
>Sorry, truly.
>
>These are exact results of ping via RHL :
>
> ping 202.134.0.155 -c 1 :
>PING 202.134.0.155(202.134.0.155) 56(84) bytes of data.
>64 bytes from 202.134.0.155: icmp_seq=1 ttl=61 time=375 ms
>
>--- 202.134.0.155 ping statistics ---
>1 packets transmitted, 1 received, 0% packet loss, time 0ms
>rtt min/avg/max/mdev = 375.192/375.192/375.192/0.000 ms
>( note : 202.134.0.155 is IP number of ISP's DNS server )

OK. Good. This, BTW, is what you call in your first message "the external
IP number of my ISP". I'm glad to know what you meant by that term.

If confirms that your system is able to use your LAN gateway
(10.234.16.99), as your routing table suggests it should.

> ping nsjkt1.telkom.net.id -c 1 :
>ping: unknown host nsjkt1.telkom.net.id
>
> ping 202.134.2.5 -c 1 :
>PING 202.134.2.5(202.134.2.5) 56(84) bytes of data.
>64 bytes from 202.134.2.5: icmp_seq=1 ttl=248 time=407 ms
>
>--- 202.134.2.5 ping statistics ---
>1 packets transmitted, 1 received, 0% packet loss, time 0ms
>rtt min/avg/max/mdev = 407.694/407.694/407.694/0.000 ms
>( note : 202.134.2.5 is IP number of ISP's DNS server )

Same thing here.



> ping ns1.telkom.net.id -c 1 :
>ping: unknown host ns1.telkom.net.id
>
>
> ping 203.130.196.6 -c 1 :
>PING 203.130.196.6(203.130.196.6) 56(84) bytes of data.
>
>--- 203.130.196.6 ping statistics ---
>1 packets transmitted, 0 received, 100% packet loss, time 0ms
>( note : 202.134.196.6 is IP number of ISP's DNS server )

Same thing again.


> ping ns2.telkom.net.id -c 1 :
>ping: unknown host ns2.telkom.net.id
>
>
> ping 18.7.22.69 -c 1 :
>PING 18.7.22.69(18.7.22.69) 56(84) bytes of data.
>
>--- 18.7.22.69 ping statistics ---
>1 packets transmitted, 0 received, 100% packet loss, time 0ms

Hmmm ... OK. No explicit error message from ping, just a failure to get a
response. (And, just to avoid uncertainty, I confirmed that I can ping this
address from here, so it's not a problem at the far end.)

So ... your host *thinks* it has a route to this address.

Can you verify that other hosts on your LAN are able to ping this address?
OR the router itself?

You might try ping'ing with more than 1 packet (say -c 5) to make sure you
are not seeing some incidental loss.

Definitely try a traceroute to this address and see where you lose
connectivity.

Your LAN uses NAT to reach the Internet. (That follows from the subnet-10
addresses it uses.) I always assume that the router is set up correctly to
NAT the address of the test host, but is there any possible issue there?
I'd guess not, since you can reach the ISP's DNS servers, but this problem
is just odd enough to make me wonder.

Can you verify that your host can ping the router's gateway address (not
its own external address; the default route in its routing table), whatever
that address is (you said you had access to the router, so I assume you can
check its routing table)?




> ping mit.edu -c 1 :
>ping: unknown host mit.edu

-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs