routing/name resolution problem

thorsten fly_a320 at gmx.de
Sun May 8 23:06:22 PDT 2005


Hello all,

I have a lfs-router with two ethernet cards, which connects via pppoe on 
eth0 to my adsl provider. eth1 has 192.168.0.1/24, my private subnet. On 
the subnet is 192.168.0.3, named linux. Now the following problem arises 
and I have no clue what is wrong:

With adsl disconnected all is fine: Name resolution works, I am able to 
ping linux (192.168.0.3):

  route
  Kernel IP routing table
  Destination     Gateway         Genmask        Flags Metric Ref Use Iface
  192.168.0.0     *               255.255.255.0   U     0      0   0 eth1

  ping linux
  PING linux.thorsten.de (192.168.0.3): 56 data bytes
  64 bytes from 192.168.0.3: icmp_seq=0 ttl=64 time=0.419 ms
  --- linux.thorsten.de ping statistics ---
  1 packets transmitted, 1 packets received, 0% packet loss
  round-trip min/avg/max/stddev = 0.419/0.419/0.419/0.000 ms

however after adsl connect: no more name resolution within the private 
subnet:

  adsl-start
  Connected!

  route
  Kernel IP routing table
  Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
  217.0.116.49    *               255.255.255.255 UH    0      0   0 ppp0
  192.168.0.0     *               255.255.255.0   U     0      0   0 eth1
  default         217.0.116.49    0.0.0.0         UG    0      0   0 ppp0

  ping www.google.de   ********** external name resolution and ping work
  PING www.l.google.com (66.249.85.104): 56 data bytes
  64 bytes from 66.249.85.104: icmp_seq=0 ttl=249 time=43.272 ms
  --- www.l.google.com ping statistics ---
  1 packets transmitted, 1 packets received, 0% packet loss
  round-trip min/avg/max/stddev = 43.272/43.272/43.272/0.000 ms

ping linux            ************* that is the point, which I don't get
ping: unknown host    ************* as far as I can see, the routing
***********************************
table looks good and typing ping 192.168.0.3 instead of ping linux works 
as it should.
Thank you for comments,

thorsten happel




More information about the lfs-support mailing list