[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problem with dhcpd/ip_masq



At 11:02 20-10-97 -0600, Al Youngwerth wrote:

>No, you don't have to be running DNS but is this a demand dial link? If so
>you may have a problem with an Win95 TCP/IP bug that can cause Win95
>machines to query DNS when they can't find a resource they used to have.
>The fix for this sucks: setup all your DNS stuff in the Win95 control
>panel, save it, then go into the registry and disable DNS (regular DNS will
>still work).

Hmmm... now i'm a little confused. Nils Renebarth just told me that I have
to be running a dns server...! My isp have 2 of them...

Anyway ... there has to be a easyer way to do it!

I use diald to get the connection.

This is what appear in /var/log/daemon.log after bootup:

Oct 20 21:25:45 badpixel kerneld: started, pid=107, qid=0
Oct 20 21:25:46 badpixel dhcpd: Internet Software Consortium DHCPD $Name:
BETA_5_14 $
Oct 20 21:25:46 badpixel dhcpd: Copyright 1995, 1996 The Internet Software
Consortium.
Oct 20 21:25:46 badpixel dhcpd: All rights reserved.
Oct 20 21:25:46 badpixel dhcpd: Listening on Socket/eth0/192.168.0.0
Oct 20 21:25:46 badpixel dhcpd: Sending on   Socket/eth0/192.168.0.0
Oct 20 21:25:59 badpixel modprobe: can't locate module binfmt-0

Then I execute "diald up" and this appears in /var/log/messages

Oct 20 21:33:49 badpixel connect: Initializing Modem
Oct 20 21:33:50 badpixel connect: Dialing system
Oct 20 21:34:10 badpixel connect: Connected
Oct 20 21:34:10 badpixel connect: Loggin in
Oct 20 21:34:14 badpixel connect: Protocol started
Oct 20 21:34:14 badpixel diald[205]: Running pppd (pid = 220).
Oct 20 21:34:14 badpixel kernel: registered device ppp0 
Oct 20 21:34:14 badpixel pppd[220]: pppd 2.2.0 started by root, uid 0
Oct 20 21:34:14 badpixel pppd[220]: Using interface ppp0
Oct 20 21:34:14 badpixel pppd[220]: Connect: ppp0 <--> /dev/ttyS1
Oct 20 21:34:17 badpixel pppd[220]: local  IP address 194.239.144.47
Oct 20 21:34:17 badpixel pppd[220]: remote IP address 194.182.253.26
Oct 20 21:34:17 badpixel pppd[220]: Cannot determine ethernet address for
proxy ARP

This is the output from ifconfig:
badpixel# ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
          UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
          RX packets:59 errors:0 dropped:0 overruns:0
          TX packets:59 errors:0 dropped:0 overruns:0

eth0      Link encap:10Mbps Ethernet  HWaddr 00:40:33:41:A3:85
          inet addr:192.168.0.250  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0
          TX packets:0 errors:0 dropped:0 overruns:0
          Interrupt:11 Base address:0x300 

ppp0      Link encap:Point-Point Protocol  
          inet addr:194.239.144.47  P-t-P:194.182.253.26  Mask:255.255.255.0
          UP POINTOPOINT RUNNING  MTU:1500  Metric:1
          RX packets:57 errors:1 dropped:1 overruns:0
          TX packets:65 errors:0 dropped:0 overruns:0

And this is my routeing table:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
255.255.255.255 *               255.255.255.255 UH    0      0        0 eth0
asc1.gby.tele.d *               255.255.255.255 UH    0      0        0 ppp0
localnet        *               255.255.255.0   U     0      0        0 eth0
loopback        *               255.0.0.0       U     0      0        5 lo
default         *               0.0.0.0         U     0      0        1 ppp0

Any ideas whats wrong?

I would be so thankfull...




Regards,

michael-legart@jensen.com
icq uin: 2565176
-------------------------


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .


Reply to: