Linux-Networking Digest #315, Volume #10 Fri, 26 Feb 99 22:13:52 EST
Contents:
Re: PPP problem : Serial line is looped back ?? (Bernd Harries)
simple routing within same network ([EMAIL PROTECTED])
Re: Use Samba on a Novell network? ("Tobin Melton")
Re: x window (jedi)
2 NICs, 1 works the other gives an error (Rutger Coers)
Re: 2 Ethernet Cards/DHCP/2.0.x Kernel=Disaster, Help? ("Philip L. Butler")
----------------------------------------------------------------------------
From: Bernd Harries <[EMAIL PROTECTED]>
Crossposted-To: comp.protocols.ppp
Subject: Re: PPP problem : Serial line is looped back ??
Date: Fri, 26 Feb 1999 16:12:38 +0100
[EMAIL PROTECTED] wrote:
> I'm using Linux Kernel 2.2.0 and PPPD 2.3.5f.
Good.
You want to dial into your school, right? And you have Linux.
But obviously not Debian Linux? Pitty, really.
Anyway, I would say don't use dip. Forget dip. Read the pppd and
the chat manpages intensively.
Use 'pppd call school'
Have a file /etc/ppp/peers/school like the /etc/ppp/options,
but with only THE pppd-options specific for your school.
Especially connect "/usr/sbin/chat -v -f
/etc/chatscripts/chatscript_school"
and the user kurtk
Have a pap-secrets file ready or if you have to login before pppd talks,
modify the chatscript similar to dip. (man chat)
Below are the files for my Provider in germany.
Change the specifig things to your needs:
phone-number, speed, port, (username, password)
Post the xconsole output or the /var/log/ppp.log tail if still problems.
Keep me updated.
==============================================
The chatscript
==============================================
ABORT "NO DIALTONE"
ABORT "NO CARRIER"
ABORT ERROR
ABORT VOICE
"" ATZ1
OK ATb8
ABORT BUSY
OK ATD042153763
CONNECT ""
==============================================
The peer-specific options
==============================================
# /etc/ppp/options
#
# $Id: options,v 1.4 1996/05/01 18:57:04 alvar Exp $
#
# Originally created by Jim Knoble <[EMAIL PROTECTED]>
# Modified for Debian by alvar Bray <[EMAIL PROTECTED]>
# Modified for PPP Server setup by Christoph Lameter
<[EMAIL PROTECTED]>
#
# Use the command egrep -v '#|^ *$' /etc/ppp/options to quickly see
what
# options are active in this file.
# Specify which DNS Servers the incoming Win95 or WinNT Connection
should use
# Two Servers can be remotely configured
# dns-addr 192.168.1.1
# dns-addr 192.168.1.2
# Specify which WINS Servers the incoming connection Win95 or WinNT
should use
# wins-addr 192.168.1.50
# wins-addr 192.168.1.51
# Specify the modem device the pppd should attempt to start a ppp
# connection too. You need to comment this out for a PPP Server setup.
/dev/ttyS3
# Specify the baud rate for the modem device.
# You should probably comment this out if you are using mgetty as your
# way of handling dialins. mgetty prepares everything so that ppppd does
# not need this parameter.
# 230400
###115200
# Use the executable or shell command specified to set up the serial
line.
# Here the default is to use the chat program to login to a remote
machine
# and start ppp. The -v flag will cause chat to log to
/var/adm/messages.
# Sensitive words in the /etc/ppp/chatscript file should be prefixed by
\q
# to stop chat writing these to the log file.
# This setting MUST be disabled for a PPP Server setup. If you want the
pppd
# to do both incoming and outgoing connection then the parameter has to
be
# specified on the commandline!
connect "/usr/sbin/chat -v -f /etc/chatscripts/chatscript_ipvos"
# Run the executable or shell command specified after pppd has
# terminated the link. This script could, for example, issue commands
# to the modem to cause it to hang up if hardware modem control signals
# were not available.
#disconnect "chat -- \d+++\d\c OK ath0 OK"
# async character map -- 32-bit hex; each bit is a character
# that needs to be escaped for pppd to receive it. 0x00000001
# represents '\x01', and 0x80000000 represents '\x1f'.
###asyncmap 0
# Require the peer to authenticate itself before allowing network
# packets to be sent or received.
# For a PPP Server with script based logins not using PAP or CHAP
# you need to disable this setting.
##auth
# Use hardware flow control (i.e. RTS/CTS) to control the flow of data
# on the serial port.
###crtscts
# Use software flow control (i.e. XON/XOFF) to control the flow of data
# on the serial port.
#xonxoff
# Don't use the modem control lines.
#local
# Specifies that pppd should use a UUCP-style lock on the serial device
# to ensure exclusive access to the device.
###lock
# Use the modem control lines. On Ultrix, this option implies hardware
# flow control, as for the crtscts option. (This option is not fully
# implemented.)
###modem
# Set the MRU [Maximum Receive Unit] value to <n> for negotiation. pppd
# will ask the peer to send packets of no more than <n> bytes. The
# minimum MRU value is 128. The default MRU value is 1500. A value of
# 296 is recommended for slow links (40 bytes for TCP/IP header + 256
# bytes of data).
# mru 1500
# Set the interface netmask to <n>, a 32 bit netmask in "decimal dot"
# notation (e.g. 255.255.255.0).
netmask 255.255.255.0
# Disables the default behaviour when no local IP address is specified,
# which is to determine (if possible) the local IP address from the
# hostname. With this option, the peer will have to supply the local IP
# address during IPCP negotiation (unless it specified explicitly on the
# command line or in an options file).
noipdefault
# Enables the "passive" option in the LCP. With this option, pppd will
# attempt to initiate a connection; if no reply is received from the
# peer, pppd will then just wait passively for a valid LCP packet from
# the peer (instead of exiting, as it does without this option).
passive
idle 30
holdoff 300
# With this option, pppd will not transmit LCP packets to initiate a
# connection until a valid LCP packet is received from the peer (as for
# the "passive" option with old versions of pppd).
#silent
# Don't request or allow negotiation of any options for LCP and IPCP
# (use default values).
#-all
# Disable Address/Control compression negotiation (use default, i.e.
# address/control field disabled).
#-ac
# Disable asyncmap negotiation (use the default asyncmap, i.e. escape
# all control characters).
#-am
# Don't fork to become a background process (otherwise pppd will do so
# if a serial device is specified).
#-detach
# Disable IP address negotiation (with this option, the remote IP
# address must be specified with an option on the command line or in an
# options file).
#-ip
# Disable magic number negotiation. With this option, pppd cannot
# detect a looped-back line.
#-mn
# Disable MRU [Maximum Receive Unit] negotiation (use default, i.e.
# 1500).
#-mru
# Disable protocol field compression negotiation (use default, i.e.
# protocol field compression disabled).
#-pc
# Require the peer to authenticate itself using PAP.
#+pap
# Don't agree to authenticate using PAP.
#-pap
# Require the peer to authenticate itself using CHAP [Cryptographic
# Handshake Authentication Protocol] authentication.
#+chap
# Don't agree to authenticate using CHAP.
#-chap
# Disable negotiation of Van Jacobson style IP header compression (use
# default, i.e. no compression).
#-vj
# Increase debugging level (same as -d). If this option is given, pppd
# will log the contents of all control packets sent or received in a
# readable form. The packets are logged through syslog with facility
# daemon and level debug. This information can be directed to a file by
# setting up /etc/syslog.conf appropriately (see syslog.conf(5)). (If
# pppd is compiled with extra debugging enabled, it will log messages
# using facility local2 instead of daemon).
###debug
# Append the domain name <d> to the local host name for authentication
# purposes. For example, if gethostname() returns the name porsche,
# but the fully qualified domain name is porsche.Quotron.COM, you would
# use the domain option to set the domain name to Quotron.COM.
#domain <d>
# Enable debugging code in the kernel-level PPP driver. The argument n
# is a number which is the sum of the following values: 1 to enable
# general debug messages, 2 to request that the contents of received
# packets be printed, and 4 to request that the contents of transmitted
# packets be printed.
#kdebug n
# Set the MTU [Maximum Transmit Unit] value to <n>. Unless the peer
# requests a smaller value via MRU negotiation, pppd will request that
# the kernel networking code send data packets of no more than n bytes
# through the PPP network interface.
#mtu <n>
# Set the name of the local system for authentication purposes to <n>.
#name <n>
# Set the user name to use for authenticating this machine with the peer
# using PAP to <u>.
user bharries
# Enforce the use of the hostname as the name of the local system for
# authentication purposes (overrides the name option).
#usehostname
# Set the assumed name of the remote system for authentication purposes
# to <n>.
#remotename <n>
# Add an entry to this system's ARP [Address Resolution Protocol]
# table with the IP address of the peer and the Ethernet address of this
# system.
##proxyarp
# Use the system password database for authenticating the peer using
# PAP.
##login
# If this option is given, pppd will send an LCP echo-request frame to
# the peer every n seconds. Under Linux, the echo-request is sent when
# no packets have been received from the peer for n seconds. Normally
# the peer should respond to the echo-request by sending an echo-reply.
# This option can be used with the lcp-echo-failure option to detect
# that the peer is no longer connected.
##lcp-echo-interval 30
# If this option is given, pppd will presume the peer to be dead if n
# LCP echo-requests are sent without receiving a valid LCP echo-reply.
# If this happens, pppd will terminate the connection. Use of this
# option requires a non-zero value for the lcp-echo-interval parameter.
# This option can be used to enable pppd to terminate after the physical
# connection has been broken (e.g., the modem has hung up) in
# situations where no hardware modem control lines are available.
##lcp-echo-failure 4
# Set the LCP restart interval (retransmission timeout) to <n> seconds
# (default 3).
#lcp-restart <n>
# Set the maximum number of LCP terminate-request transmissions to <n>
# (default 3).
#lcp-max-terminate <n>
# Set the maximum number of LCP configure-request transmissions to <n>
# (default 10).
#lcp-max-configure <n>
# Set the maximum number of LCP configure-NAKs returned before starting
# to send configure-Rejects instead to <n> (default 10).
#lcp-max-failure <n>
# Set the IPCP restart interval (retransmission timeout) to <n>
# seconds (default 3).
#ipcp-restart <n>
# Set the maximum number of IPCP terminate-request transmissions to <n>
# (default 3).
#ipcp-max-terminate <n>
# Set the maximum number of IPCP configure-request transmissions to <n>
# (default 10).
#ipcp-max-configure <n>
# Set the maximum number of IPCP configure-NAKs returned before starting
# to send configure-Rejects instead to <n> (default 10).
#ipcp-max-failure <n>
# Hint for /etc/ppp/ip-up.d/anmelder that it shall advertise the
# new temporary IP address to my friends
ipparam is_vossnet
# Set the PAP restart interval (retransmission timeout) to <n> seconds
# (default 3).
#pap-restart <n>
# Set the maximum number of PAP authenticate-request transmissions to
# <n> (default 10).
#pap-max-authreq <n>
# Set the CHAP restart interval (retransmission timeout for
# challenges) to <n> seconds (default 3).
#chap-restart <n>
# Set the maximum number of CHAP challenge transmissions to <n>
# (default 10).
#chap-max-challenge
# If this option is given, pppd will rechallenge the peer every <n>
# seconds.
#chap-interval <n>
# With this option, pppd will accept the peer's idea of our local IP
# address, even if the local IP address was specified in an option.
ipcp-accept-local
# With this option, pppd will accept the peer's idea of its (remote) IP
# address, even if the remote IP address was specified in an option.
ipcp-accept-remote
# Hint for negotiation: Give remote server
#
##:enterprise.vossnet.de
# Add a default route to the system routing tables, using the peer as
# the gateway, when IPCP negotiation is successfully completed. This
# entry is removed when the PPP connection is broken.
# It is probably advisable to use defaultroute for outbound connections
# only. In mixed mode defaultroute should be specified on the
commandline.
defaultroute
# Specifies that certain characters should be escaped on transmission
# (regardless of whether the peer requests them to be escaped with its
# async control character map). The characters to be escaped are
# specified as a list of hex numbers separated by commas. Note that
# almost any character can be specified for the escape option, unlike
# the asyncmap option which only allows control characters to be
# specified. The characters which may not be escaped are those with hex
# values 0x20 - 0x3f or 0x5e.
#escape 11,13,ff
--
Bernd Harries
[EMAIL PROTECTED] http://www.freeyellow.com/members/bharries
[EMAIL PROTECTED] Tel. +49 421 809 7351 priv. | MSB First!
[EMAIL PROTECTED] +49 421 457 3966 offi. | Linux-m68k
[EMAIL PROTECTED] | Medusa T40
<>_<> _______ _____
.---|'"`|---. | |_| |_|_|_|_|_|_|_ (_____) .-----.
______`o"O-OO-OO-O"o'`-o---o-'`-oo-----oo-'`-o---o-'`-o---o-'___
------------------------------
From: [EMAIL PROTECTED]
Subject: simple routing within same network
Date: Thu, 25 Feb 1999 15:33:44 GMT
Hi all,
probably this is fairly simple, anyway can somebody give me
a hint on this:
I�m trying to set up basic routing between two network cards.
IP-Forwarding is turned on in the kernel, all firewalling is
turned off.
My network looks like this:
194.97.200.169 194.97.200.162/3/4...
| |
[internet]-------[router]-------[linux-box]-------[internal-network]
| |
| 194.97.200.168
194.97.200.161
My Internal network consists of 194.97.200.162, 163, 164, 165, 166,
167, 170, 171, 172, 173, 174 and 175.
With this setup I can ping the router as well as the internal
network using eth1 for the router and eth0 for internal.
Now what doesnt work is the routing. from internal I can�t ping the
router and vice versa.
Another thing I can�t do: I can�t ping the eth1 IP-Address, neither from
the linux box itself nor from anywhere else.
But: I can ping the router _through_ it. (so it basically works)
Shouldn�t it be possible to ping all the local interfaces even without
any routing entries?
BTW: Here�s the routing table:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
194.97.200.168 0.0.0.0 255.255.255.255 UH 0 0 0 dummy0
194.97.200.161 0.0.0.0 255.255.255.255 UH 0 0 0 eth1
194.97.200.0 0.0.0.0 255.255.255.0 U 0 0 1 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 2 lo
0.0.0.0 194.97.200.161 0.0.0.0 UG 0 0 0 eth1
My /etc/route.conf looks like this:
194.97.200.161 0.0.0.0 255.255.255.255 eth1
194.97.200.0 0.0.0.0 255.255.255.0 eth0
default 194.97.200.161 0.0.0.0 eth1
When I change the network part (.200.) of one of the interfaces
to 201 or something, everything works fine. Linux just doesn�t
seem to know that it should route between to cards that are
obviously on the same subnet.
Anything special I have to set the subnet-mask to for this
to work?
Any help would be greatly appreciated!
Cheers,
Kai
[EMAIL PROTECTED]
============= Posted via Deja News, The Discussion Network ============
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
------------------------------
From: "Tobin Melton" <[EMAIL PROTECTED]>
Subject: Re: Use Samba on a Novell network?
Date: Thu, 25 Feb 1999 10:45:35 -0600
grab the GTKSAMA tool from somewhere...i had problems till i got this and it
helps out in an awesone way...basically an X frontend for the SAMA config
file
Jeff Lasman wrote in message <[EMAIL PROTECTED]>...
>DIT wrote:
>
>> Is Samba the answer here even though we are on a Novell network or is
>> there another solution? I have tried setting Samba up but haven't had
>> much success. I can see that Samba is running and I can see it in
>> Network Neighborhood on my NT Workstation. But when I click on it,
>> nothing happens. And the 'Map network drive' selection is greyed out.
>>
>> Am I going in the right direction or is there a "Novell solution"?
>
>Great book: "Samba: Integrating UNIX and Windows", Blair, SSC, 1998.
>ISBN: 1-57831-006-7. Good explanations. Lots of handholding.
>
>Jeff
>
>--
>Jeff Lasman <[EMAIL PROTECTED]>
>"Publisher of the FREE InterestingTimes computer-industry newsletter.
>To subscribe, write <[EMAIL PROTECTED]>."
------------------------------
From: [EMAIL PROTECTED] (jedi)
Subject: Re: x window
Date: Fri, 26 Feb 1999 17:00:00 -0800
On Fri, 26 Feb 1999 01:53:10 +0100, hotmilk <[EMAIL PROTECTED]> wrote:
>
>
>
Goto www.scitechsoft.com.
>
>
> Does anybody knows howto install intel I740 graphic card under X
>with RH5.2 ?
> Which graphic card is similar to the I740 ?
>
> Thank you
>
> Les petits francais,r�pondez moi,svp...
>
>
>
>
>
>
>
>
>
>
>
>
--
Herding Humans ~ Herding Cats
Neither will do a thing unless they really want to, or |||
is coerced to the point where it will scratch your eyes out / | \
as soon as your grip slips.
In search of sane PPP docs? Try http://penguin.lvcm.com
------------------------------
From: Rutger Coers <[EMAIL PROTECTED]>
Subject: 2 NICs, 1 works the other gives an error
Date: Thu, 25 Feb 1999 17:53:46 +0100
these PCI NICs are using the ne2k-pci driver, they both initialize well
on
start-up......
BUT when i (after a while) type dmesg on the console then at the end of
the
text there is written :
eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x2, t=3000
eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x2, t=6000
eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=6000
eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=3183
eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=5817
this goes on & on & ......
what is wrong? Can anybody help me?
btw ive got RedHat 5.1
thnx in advance,
Mangli
------------------------------
From: "Philip L. Butler" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Re: 2 Ethernet Cards/DHCP/2.0.x Kernel=Disaster, Help?
Date: Thu, 25 Feb 1999 15:55:30 GMT
Has anyone seen the 0.7 version of dhcpcd anywhere on the net ?? The
1.3x version doesn't seem to work on kernel 2.0.33 (and other messages on
this group verify that).
Thanks,
Phil Butler
[EMAIL PROTECTED]
Clinton Pierce wrote:
> On Sat, 13 Feb 1999 01:32:47 +0100, Malware
> <[EMAIL PROTECTED]> wrote:
>
> >Clinton Pierce wrote:
> >> DHCP 0.7 will not run with two Ethernet cards.[1] It disables the
> >[...]
> >> 1.3 will not run with a kernel revision lower than 2.1.70, but does
> >
> >Beetween 0.7 and 1.3 there is some space for numbers - Did you try to
> >use a version between?
>
> Actually, I couldn't find one. The "Changes" file in the distribution
> says there are two versions of dhcpcd: "before v.1.3" and since then.
> --
> "If you rush a Miracle Man, you get rotten miracles"
> --Miracle Max, The Princess Bride
> DNRC: "Grand Inquisitor of Out At 5 Doctrine" 06/96
------------------------------
** 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
******************************
