Linux-Networking Digest #437, Volume #12          Wed, 1 Sep 99 12:13:40 EDT

Contents:
  Re: samba-2.0.5a ("David J. M. Karlsen")
  Wierd udp packets on port 2348 ([EMAIL PROTECTED])
  Re: Mounting an NFS drive for Redhat 6.0 to Solaris 7 ("Kenneth Allan")
  NFS with RedHat 6.0 (Cedric Bonzon)
  Re: Finding my network card (Seth Rothberg)
  full duplex with linksys 10/100 NIC on RH6 (Partha Sri)
  Autodialing PPP Gateway? ("Brian J. Bernstein")
  Cool new Linux Dist - Runs from Flash-ROM - Free if you download (James Stevens)
  PPP sending but not receiving packets? (Ellis Pritchard)
  Re: DHCP troubles (Piotr Zolnierczuk)
  Wierd udp packets on port 2348 ([EMAIL PROTECTED])
  Re: Hostname for PPP connection? (Clifford Kite)
  Re: PPP hostnames vs IP (Clifford Kite)
  Re: chat error: can't get terminal parameters: not a typewriter (Clifford Kite)
  Re: RH 6.0, PPP, and my ISP (Clifford Kite)

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

From: "David J. M. Karlsen" <[EMAIL PROTECTED]>
Subject: Re: samba-2.0.5a
Date: Wed, 01 Sep 1999 14:35:05 +0200

"michael.fengler" wrote:

> # smbmount //optiplix/ftp /mnt -Umike
> Added interface ip=10.42.42.107 bcast=10.42.42.255 nmask=255.255.255.0
> Password:
> # cd /mnt
> # ls
> .    ..   mypc3

But the filedates are still wrong (several years infacet), even though
they are right at the NT side?

--
David J. M. Karlsen [[EMAIL PROTECTED]]      -*-     LAB: [EMAIL PROTECTED]     -*-     
http://cmr.no
fon: [+47] 55 57 43 29                  -*-     fax: [+47] 55 57 40 41




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

From: [EMAIL PROTECTED]
Subject: Wierd udp packets on port 2348
Date: Wed, 01 Sep 1999 14:22:59 GMT

I'm seeing a strange UDP packet hitting mu PPP
interface roughly every second and it's keeping my
line up when not otherwise in use.  It looks like
this:

[root@serv /root]# tcpdump udp -i ppp0 | grep 2348
tcpdump: listening on ppp0
21:40:09.965909 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:11.235882 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:12.165895 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:13.255895 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:14.365902 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:15.485881 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:16.565895 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:17.665869 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:18.765868 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:19.865886 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:20.965881 38.30.38.153.2348 >
38.30.38.153.2348: udp 29

547 packets received by filter
0 packets dropped by kernel


It's wierd because 38.30.38.153 is the address of
my PPP interface:

[root@serv /root]# ifconfig ppp0
ppp0      Link encap:Point-to-Point Protocol
          inet addr:38.30.38.153  P-t-P:38.1.1.1
Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST
MTU:1524  Metric:1
          RX packets:56720 errors:646 dropped:0
overruns:0 frame:646
          TX packets:60603 errors:0 dropped:0
overruns:0 carrier:0
          collisions:0 txqueuelen:10

I've got an updated RH5.2 setup running PPP via an
external ISDN line, feeding a few Win98/Linux
boxes.  My ipchains stuff looks like this:

[from
/etc/rc.d/rc.local]------------------------------------------
echo "1" > /proc/sys/net/ipv4/ip_forward
echo "1" > /proc/sys/net/ipv4/ip_dynaddr

# flush all rules
ipchains -F

# default policy: deny forwarding
ipchains -P forward DENY

# do not forward Windows garbage
/sbin/ipchains -A forward -s 0.0.0.0/0 137:139 -p
tcp -j DENY
/sbin/ipchains -A forward -s 0.0.0.0/0 137:139 -p
udp -j DENY
/sbin/ipchains -A forward -s 0.0.0.0/0 2348:2348
-p udp -j DENY

ipchains -A forward -j MASQ -s 172.16.1.0/24 -d
0.0.0.0/0
ipmasqadm portfw -f

# Startup PPP networking
pppd /dev/ttyS0 :208.137.248.4
=======================================================================

The third DENY statement is to kill those packets
but it hasn't worked.

I've tried fuser and netstat to no avail.  I've
even looked up port 2348 and apart from a resource
tracking prog called RTS (not on my machine),
nothing is registered to use port 2348.  I'm
gettin' worried!


Has anyone seen this before or can help?  Thanks
in advance

~Tim


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

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

From: "Kenneth Allan" <[EMAIL PROTECTED]>
Subject: Re: Mounting an NFS drive for Redhat 6.0 to Solaris 7
Date: Mon, 30 Aug 1999 19:47:44 +1000

This work perfectly,
Thank you,
Cheers Ken.
Dmitri A. Sergatskov <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]...
> On Sun, 29 Aug 1999 20:32:24 +1000,
> Kenneth Allan <[EMAIL PROTECTED]> wrote:
> >Hi all
> >I am trying to export a partition from a Redhat 6.0 box to a Sparc 5 with
> >Solaris 7. However they dont seem to have compatible NFS systems. Redhat
> >reports in the message log
> >
> >Aug 29 20:22:05 THEHEAD mountd[429]: authenticated mount request from
> >Dragonfly:
> >847
> >Aug 29 20:22:05 THEHEAD kernel: svc: unknown version (3)
> >
> >I have checked /var/exports and all process are running ok.
> >
> >Can anyone help
> >
> >Thanks heaps
> >Ken
> >
> >
>
> In the file /etc/rc.d/init.d/nfs change the line:
> daemon rpc.mountd
>
> to
>
> daemon rpc.mountd -V 2 -N 3
>
> Restart nfs:
>
> /etc/rc.d/init.d/nfs stop ; /etc/rc.d/init.d/nfs start
>
> Now it should work.
>
> Regards,
>
> Dmitri.
>
>
>
>



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

From: Cedric Bonzon <[EMAIL PROTECTED]>
Subject: NFS with RedHat 6.0
Date: Wed, 01 Sep 1999 14:31:25 +0200
Reply-To: [EMAIL PROTECTED]

I have a problem with RedHat 6.0 NFS

I had to recompile the kernel to support Stallion multiport board.
Now, when i boot, the nfsd refuse to start, the /var/log/messages
contain:

Sep  1 11:36:23 loex nfs: Starting NFS services:  succeeded
Sep  1 11:36:24 loex nfs: rpc.statd startup succeeded
Sep  1 11:36:24 loex nfs: rpc.rquotad startup succeeded
Sep  1 11:36:24 loex nfs: rpc.mountd startup succeeded
Sep  1 11:36:25 loex rpc.nfsd: nfssvc: Function not implemented
Sep  1 11:36:25 loex nfs: rpc.nfsd startup failed

Can you help me ?




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

From: Seth Rothberg <[EMAIL PROTECTED]>
Subject: Re: Finding my network card
Date: Wed, 1 Sep 1999 09:13:54 -0400

Gracias. That's just what I needed to find out.

Seth

Kyle Hargraves <[EMAIL PROTECTED]> wrote:
>Seth Rothberg wrote:
>>=20
>> I've got a 3com Fast Etherlink XL PCI (3905C-TX) NIC in my box and I'm=
 trying to
>> get Red Hat 6.0 to find and use it. It works fine in Windows 98. But i=
n Linux,
>> when I run "ifconfig eth0 192.168.140.1" I get told that eth0 is an un=
known
>> interface.
>>=20
>> Questions: Is eth0 an unknown interface because I don't have the right=
 driver
>> for my card? I'm using the 3c590/3c900 series. If those are not the ri=
ght
>> drivers, is there any way in Red Hat to get Linux to find which card i=
t thinks
>> I have. I thought it did when I installed it, but I didn't pursue it
>> as I wasn't ready to set up networking then.
>>=20
>> Another question: If getting the eth0 interface working has nothing to=
 do with
>> finding the right driver for my card, or even if it does, how do I get=
  the
>> eth0 interface up and running?
>>=20
>> Thanks,
>> Seth
>
>If `ifconfig -a` doesn't list eth0 as a known device (even if it is down=
), then
>you don't have the correct driver in your kernel. Just recompile with su=
pport
>if that's the case.
>
>--=20
>Kyle Hargraves
>man(1) pages are good for the soul.


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

From: Partha Sri <[EMAIL PROTECTED]>
Subject: full duplex with linksys 10/100 NIC on RH6
Date: Wed, 01 Sep 1999 08:57:10 -0500
Reply-To: [EMAIL PROTECTED]

Hi all:

I am having trouble getting my linksys 10/100 NIC to work on my linux
box. (RH 6, 2.2.15) . This is my second NIC, the other one being a
eepro100. The ifconfig output on the linksys interface has 50% carrier
errors.. and I have checked the cables and they look fine.. my dmesg is
filled with a message which reads "Switching eth1 to 100MB full
duplex..".. the other eepro100 interface works just fine with the same
set of cables.. I use the tulip driver that comes with RH for the
linksys card.

has anyone seen this kind of a message before on a linksys card?

thanks in advance

Partha


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

From: "Brian J. Bernstein" <[EMAIL PROTECTED]>
Subject: Autodialing PPP Gateway?
Date: Wed, 1 Sep 1999 09:06:00 -0400

Hello,
I've tried searching a bit for a program like this through freshmeat, but I
haven't had much luck. Basically, I have a 486 that I want to make a
communications server. In other words, I have a home network and modem
connected to it, and I would like to have it that it dials up my ISP
(username and password stored) whenever some sockets need to go outside of
the home network. With a settable timeout, it would disconnect from
inactivity.

Anyone care to point me towards a program that handles this? Much
appreciated...

--
Brian J. Bernstein              (212) 449-3032 (voice)
[EMAIL PROTECTED]                 (888) 769-1332 (numeric pager)
[EMAIL PROTECTED] (alpha pager: up to 200 chars)
My opinions and statements are my own and are not of my employer.




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

From: [EMAIL PROTECTED] (James Stevens)
Subject: Cool new Linux Dist - Runs from Flash-ROM - Free if you download
Date: Wed, 01 Sep 1999 14:44:31 GMT

PizzaBox Server: File, Print & CD Server with remote access, Tape
Backup, UPS support and sophisticated Web Management running Linux &
Samba, on standard PC hardware, from a plug in Flash-ROM. Available to
end users / resellers as a turnkey server or to system builders in kit
form. Free, fully working, evaluation copy can be downloaded as only
three floppy images from our web site. http://www.jrcs.co.uk/

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

Date: Wed, 01 Sep 1999 15:49:06 +0100
From: Ellis Pritchard <[EMAIL PROTECTED]>
Subject: PPP sending but not receiving packets?

Hi,

A fantastic problem for you, I've managed to create a one-way PPP link!
:)

Ok, I'm using RedHat Linux 5.2, kernel 2.0.36 with the kernal patched
with the 'demand' dialing patch which came with ppp-2.3.5. I've also an
ZyXEL omni.net external ISDN modem (definitely working on Windoze).

I've configured PPP by hand in /etc/ppp:

[/etc/ppp/options]
name nuke
lock
idle 300
ipcp-accept-remote
ipcp-accept-local
holdoff 10
connect /etc/ppp/dircon-chat-script
modem
crtscts
debug
kdebug 7
defaultroute

[/etc/ppp/dircon-chat-script]
#!/bin/sh
exec /usr/sbin/chat -s -e -v \
        TIMEOUT         3 \
        ABORT           BUSY \
        ABORT           'NO ANSWER' \
        ABORT           'NO CARRIER' \
        ''              'ATB93S20=1S82=74S102=74' \
        'OK'            ATDI08450798200 \
        CONNECT         ''

and an appropriate pap-secrets file, which I won't disclose for obvious
reasons :*)

My ISP gives me an ISDN account with PAP authentication and dynamic IP.

So when I go:

pppd /dev/modem 115200

This spews out in /var/log/messages:

Sep  1 15:35:40 arnie pppd[6718]: pppd 2.3.5 started by root, uid 0
Sep  1 15:35:41 arnie chat[6719]: timeout set to 3 seconds
Sep  1 15:35:41 arnie chat[6719]: abort on (BUSY)
Sep  1 15:35:41 arnie chat[6719]: abort on (NO ANSWER)
Sep  1 15:35:41 arnie chat[6719]: abort on (NO CARRIER)
Sep  1 15:35:41 arnie chat[6719]: send (ATB93S20=1S82=74S102=74^M)
Sep  1 15:35:41 arnie chat[6719]: expect (OK)
Sep  1 15:35:41 arnie chat[6719]: ATB93S20=1S82=74S102=74^M^M
Sep  1 15:35:41 arnie chat[6719]: OK
Sep  1 15:35:41 arnie chat[6719]:  -- got it
Sep  1 15:35:41 arnie chat[6719]: send (ATDI08450798200^M)
Sep  1 15:35:42 arnie chat[6719]: expect (CONNECT)
Sep  1 15:35:42 arnie chat[6719]: ^M
Sep  1 15:35:44 arnie chat[6719]: ATDI08450798200^M^M
Sep  1 15:35:44 arnie chat[6719]: CONNECT
Sep  1 15:35:44 arnie chat[6719]:  -- got it
Sep  1 15:35:44 arnie chat[6719]: send (^M)
Sep  1 15:35:44 arnie pppd[6718]: Serial connection established.
Sep  1 15:35:45 arnie kernel: ppp_tty_ioctl: set flags to 70000
Sep  1 15:35:45 arnie kernel: ppp_tty_ioctl: set flags to 70000
Sep  1 15:35:45 arnie kernel: ppp_tty_ioctl: set xasyncmap
Sep  1 15:35:45 arnie kernel: ppp_tty_ioctl: set xmit asyncmap ffffffff
Sep  1 15:35:45 arnie kernel: ppp_tty_ioctl: set flags to 70000
Sep  1 15:35:45 arnie kernel: ppp_tty_ioctl: set mru to 5dc
Sep  1 15:35:45 arnie kernel: ppp_tty_ioctl: set rcv asyncmap ffffffff
Sep  1 15:35:45 arnie kernel: ppp_tty_ioctl: set flags to 70000
Sep  1 15:35:45 arnie pppd[6718]: Using interface ppp0
Sep  1 15:35:45 arnie pppd[6718]: Connect: ppp0 <--> /dev/modem
Sep  1 15:35:48 arnie kernel: ppp_tty_ioctl: set xmit asyncmap 0
Sep  1 15:35:48 arnie kernel: ppp_tty_ioctl: set flags to f070000
Sep  1 15:35:48 arnie kernel: ppp_tty_ioctl: set mru to 5dc
Sep  1 15:35:48 arnie kernel: ppp_tty_ioctl: set rcv asyncmap ffffffff
Sep  1 15:35:48 arnie kernel: ppp_tty_ioctl: set flags to f070010
Sep  1 15:35:48 arnie pppd[6718]: Remote message:
Sep  1 15:35:48 arnie kernel: ppp_tty_ioctl: set flags to f070050
Sep  1 15:35:48 arnie pppd[6718]: local  IP address 194.112.53.153
Sep  1 15:35:48 arnie pppd[6718]: remote IP address 194.112.50.134
Sep  1 15:35:48 arnie kernel: ppp_tty_ioctl: set flags to f070010
Sep  1 15:35:48 arnie kernel: ppp_tty_ioctl: set maxcid to 16
Sep  1 15:35:48 arnie kernel: ppp_tty_ioctl: set flags to f070014
Sep  1 15:35:48 arnie kernel: ppp: channel ppp0 going up for IP packets!



LOOKS GOOD DON'T IT! :)

Here's the ever popular routing table:

[root@arnie ppp]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
194.112.50.134  0.0.0.0         255.255.255.255 UH    0      0        0
ppp0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0      178
eth0
192.168.3.0     192.168.1.5     255.255.255.0   UG    0      0       17
eth0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0       43
lo
0.0.0.0         194.112.50.134  0.0.0.0         UG    0      0        0
ppp0


Default routes look ok...


And why not an ifconfig?


[root@arnie ppp]# 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:1374 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1374 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0

eth0      Link encap:Ethernet  HWaddr 00:A0:C9:43:67:6E
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:32635 errors:0 dropped:0 overruns:0 frame:65
          TX packets:18161 errors:0 dropped:0 overruns:0 carrier:0
          collisions:47
          Interrupt:11 Base address:0x6000

ppp0      Link encap:Point-to-Point Protocol
          inet addr:194.112.53.153  P-t-P:194.112.50.134
Mask:255.255.255.0
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1524  Metric:1
          RX packets:8 errors:1 dropped:0 overruns:0 frame:0
          TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          Memory:9d8034-9d8c00


Note that there is already an error on the RX packets on ppp0.

So the next thing I try is to ping www.netscape.com:

[root@arnie ppp]# ping www.netscape.com
PING www-ld1.netscape.com (207.200.75.200): 56 data bytes

--- www-ld1.netscape.com ping statistics ---
6 packets transmitted, 0 packets received, 100% packet loss

No dice, during this period the RX and TX lights on the modem blink in
expected fashion (TX pause RX, ...), so I pressed break.


Now another ifconfig:

[root@arnie ppp]# ifconfig -i ppp0
ppp0      Link encap:Point-to-Point Protocol
          inet addr:194.112.53.153  P-t-P:194.112.50.134
Mask:255.255.255.0
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1524  Metric:1
          RX packets:8 errors:7 dropped:0 overruns:0 frame:5
          TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          Memory:9e8034-9e8c30

GOSH! 6 packets transmitted by ping, and 6 more RX errors...


Now, from another server connected to the internet, I can try to ping
the troublesome server:

webforce 8# ping 194.112.53.153
PING 194.112.53.153 (194.112.53.153): 56 data bytes


----194.112.53.153 PING Statistics----
5 packets transmitted, 0 packets received, 100% packet loss

Another 5 packets out, this time the RX light on the modem blinks, but
no TX follows.

[root@arnie ppp]# ifconfig -i ppp0
ppp0      Link encap:Point-to-Point Protocol
          inet addr:194.112.53.153  P-t-P:194.112.50.134
Mask:255.255.255.0
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1524  Metric:1
          RX packets:8 errors:12 dropped:0 overruns:0 frame:10
          TX packets:15 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0
          Memory:9e8034-9e8c30

GOSH! Another 5 pings and another 5 RX errors!


SO, it would seem that TXing works, but not RXing.

Anyone got any clues as to why this should be, or what I can try next?

Cheers!

Ellis.



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

From: Piotr Zolnierczuk <[EMAIL PROTECTED]>
Subject: Re: DHCP troubles
Date: Wed, 01 Sep 1999 10:52:31 -0400

Tom Eastep wrote:

>
> b) DHCPCD is pretty much deprecated with the 2.2.* kernels -- you should
> be using dhcpclient or pump.
>

can you give me an url where can I find them?

                                                            Regards
                                                                        Piotr

--
 ________________________________________________________________
 Piotr Adam Zolnierczuk
 Dept. of Physics and Astronomy   http://www.pa.uky.edu/~zolnie
 University of Kentucky           phone:  (606) 257-5565
 Lexington, KY 40506, USA         fax:    (606) 323-2846
 ________________________________________________________________
                   written on recycled electrons




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

From: [EMAIL PROTECTED]
Subject: Wierd udp packets on port 2348
Date: Wed, 01 Sep 1999 14:23:00 GMT

I'm seeing a strange UDP packet hitting mu PPP
interface roughly every second and it's keeping my
line up when not otherwise in use.  It looks like
this:

[root@serv /root]# tcpdump udp -i ppp0 | grep 2348
tcpdump: listening on ppp0
21:40:09.965909 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:11.235882 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:12.165895 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:13.255895 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:14.365902 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:15.485881 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:16.565895 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:17.665869 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:18.765868 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:19.865886 38.30.38.153.2348 >
38.30.38.153.2348: udp 29
21:40:20.965881 38.30.38.153.2348 >
38.30.38.153.2348: udp 29

547 packets received by filter
0 packets dropped by kernel


It's wierd because 38.30.38.153 is the address of
my PPP interface:

[root@serv /root]# ifconfig ppp0
ppp0      Link encap:Point-to-Point Protocol
          inet addr:38.30.38.153  P-t-P:38.1.1.1
Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST
MTU:1524  Metric:1
          RX packets:56720 errors:646 dropped:0
overruns:0 frame:646
          TX packets:60603 errors:0 dropped:0
overruns:0 carrier:0
          collisions:0 txqueuelen:10

I've got an updated RH5.2 setup running PPP via an
external ISDN line, feeding a few Win98/Linux
boxes.  My ipchains stuff looks like this:

[from
/etc/rc.d/rc.local]------------------------------------------
echo "1" > /proc/sys/net/ipv4/ip_forward
echo "1" > /proc/sys/net/ipv4/ip_dynaddr

# flush all rules
ipchains -F

# default policy: deny forwarding
ipchains -P forward DENY

# do not forward Windows garbage
/sbin/ipchains -A forward -s 0.0.0.0/0 137:139 -p
tcp -j DENY
/sbin/ipchains -A forward -s 0.0.0.0/0 137:139 -p
udp -j DENY
/sbin/ipchains -A forward -s 0.0.0.0/0 2348:2348
-p udp -j DENY

ipchains -A forward -j MASQ -s 172.16.1.0/24 -d
0.0.0.0/0
ipmasqadm portfw -f

# Startup PPP networking
pppd /dev/ttyS0 :208.137.248.4
=======================================================================

The third DENY statement is to kill those packets
but it hasn't worked.

I've tried fuser and netstat to no avail.  I've
even looked up port 2348 and apart from a resource
tracking prog called RTS (not on my machine),
nothing is registered to use port 2348.  I'm
gettin' worried!


Has anyone seen this before or can help?  Thanks
in advance

~Tim


Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.

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

From: kite@NoSpam.%inetport.com (Clifford Kite)
Subject: Re: Hostname for PPP connection?
Date: 1 Sep 1999 09:48:39 -0500

Edward S Meadows ([EMAIL PROTECTED]) wrote:

: I connect my home machine to the world via a PPP connection
: at the University of Delaware, where I work.  The domain
: there is udel.edu, so I gave my local machine the hostname
: tiago.udel.edu.  I find that I can't use mail from home
: because my ISP rejects tiago.udel.edu as a valid hostname.

: What should my hostname be in this case?  The apparent
: hostname that my ppp connection has on the remote machine is
: ppp-as10-14.nss.udel.edu.  Is that relevant?

Host names must be added to the DNS data base by a network administrator
before they can be used to access your host.  Just defining your hostname
won't do it.  The ppp-as10-14.nss.udel.edu is the DNS name of the IP
address used for that particular connection.

--
Clifford Kite <kite@inet%port.com>                    Not a guru. (tm)
/* For every credibility gap, there is a gullibility fill.
                -- R. Clopton */

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

From: kite@NoSpam.%inetport.com (Clifford Kite)
Subject: Re: PPP hostnames vs IP
Date: 1 Sep 1999 09:56:03 -0500

Rick ([EMAIL PROTECTED]) wrote:

:    I'm pretty new to Linux and am still getting my box up and running.  I 
: have finally solved the problem of dialing my ISP successfully and now am 
: just tangling with the issue of accessing the web.  I can ping localhost 
: and 205.188.247.66 (www.netscape.com) fine, but when I try pinging 
: www.netscape.com itself, it can't find the host.  I can open up the IP in 
: Netscape as well, but IP addresses only, not hostnames.

Sounds like a resolver problem.  Have you configured /etc/resolv.conf with
nameservers?  man 5 resolver.


--
Clifford Kite <kite@inet%port.com>                    Not a guru. (tm)
/* The signal-to-noise ratio is too low in many [news] groups to make
 * them good candidates for archiving.
 *    --- Mike Moraes, Answers to FAQs about Usenet */

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

From: kite@NoSpam.%inetport.com (Clifford Kite)
Subject: Re: chat error: can't get terminal parameters: not a typewriter
Date: 1 Sep 1999 09:59:54 -0500

Khurram Farhan Hassan ([EMAIL PROTECTED]) wrote:

: If I send this command (AT&F%E0&W0) to the modem using minicom, there
: is no error.

You need single quotes:  'AT&F%E0&W0'  to prevent the shell from
intercepting the ampersand.

--
Clifford Kite <kite@inet%port.com>                    Not a guru. (tm)
/* 97.3% of all statistics are made up. */

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

From: kite@NoSpam.%inetport.com (Clifford Kite)
Subject: Re: RH 6.0, PPP, and my ISP
Date: 1 Sep 1999 09:53:53 -0500

Josh Thompson ([EMAIL PROTECTED]) wrote:

: I am trying to connect to my ISP (Intrex in Raleigh, NC).  They don't
: officially support linux, but have several users connecting with it.  I
: have tried everything I can think of.  I have set up the connection with
: RedHat's netcfg, using scripts, connecting with minicom and then
: starting pppd after exiting, and a few other methods.  I am using PAP. 
: I have a Digicom Connection 144+ modem.  I can connect to a terminal
: dialup somewhere else and use slirp without any problems.  I have
: attached a script that I have tried, the output generated when starting
: pppd from the command line after connecting with chat, and what is
: generated in my log files.  What gives?!!

: ---------------script----------------
: #!/bin/bash -v
: #       ppp-on
: #       Set up a PPP link
: #       /etc/ppp/pap-secrets file must exist and contain
: #       USERNAME        *       PASSWORD

: LOCKDIR=/var/lock/modem
: DEVICE=modem
: umask 022
: PHONE=<my ISP's number>
: NAME=<my PAP name>

I'd suggest trying  export NAME=<my PAP name>  instead.  This is necessary
when exec'ing pppd although I'm not sure it's what's wrong here where
pppd is simply backgrounded and not exec'ed.  But pppd doesn't know it's
supposed to do PAP so it's a likely candidate anyway.


--
Clifford Kite <kite@inet%port.com>                    Not a guru. (tm)
/* I gave up on politics when no matter who I voted for, I regretted it.
 *    -- Pepper...and Salt, WSJ */

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


** FOR YOUR REFERENCE **

The service address, to which questions about the list itself and requests
to be added to or deleted from it should be directed, is:

    Internet: [EMAIL PROTECTED]

You can send mail to the entire list (and comp.os.linux.networking) via:

    Internet: [EMAIL PROTECTED]

Linux may be obtained via one of these FTP sites:
    ftp.funet.fi                                pub/Linux
    tsx-11.mit.edu                              pub/linux
    sunsite.unc.edu                             pub/Linux

End of Linux-Networking Digest
******************************

Reply via email to