Linux-Networking Digest #904, Volume #10         Sun, 18 Apr 99 10:13:42 EDT

Contents:
  Re: Tulip - Linksys LNE100TX - Etherfast 10/100 LAN Card ("Action")
  Re: DHCP client questions (Stephen Carville)
  dhcp and 255.255.255.255 a new twist ("Larry Ash")
  Re: Problem compiling SSH-1.2.26 under Redhat Starbuck release 5.9.7... (Ingo 
Buescher)
  Re: DHCP (Stephen Carville)
  What is the load of this setup ?? ("alvin")
  Re: DHCPD and BIND Rumor? (Stephen Carville)
  Re: What's supposed to be in (now) TCP port 113? (mist)
  Re: What's supposed to be in (now) TCP port 113? (mist)
  usertty (Stephen Carville)
  NFS WITHIN AN IP MASQ FIREWALL (fwd) (Glenn Graham)

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

From: "Action" <[EMAIL PROTECTED]>
Subject: Re: Tulip - Linksys LNE100TX - Etherfast 10/100 LAN Card
Date: Sun, 18 Apr 1999 05:36:39 GMT

its not just a linux problem, I tried using the same card on both, a linux
machine and a win98 machine.  the card, simply put, sucks.  linksys made its
name by producing 16-bit cards for win 3.1 and has rested on its haunches
since.  My advice would be get rid of the card, and spring for the $30-40
(unless you go 3com) on a new 100baseT card.

-Action.


Mike Rayborn <[EMAIL PROTECTED]> wrote in message
news:7fbd7r$p1m$[EMAIL PROTECTED]...
> I have a Linksys LNE100TX Etherfast 10/100 LAN Card that I can't get to
work
> reliably with Linux 2.0.33.  I'm using tulip v0.91 4-14-99 with options
> debug=6 I get the following output for PING of another host (Windows 95)
on
> same network.
>
> Apr 17 20:54:54 pegasus kernel: eth0: tulip_open() irq 10.
> Apr 17 20:54:54 pegasus kernel: eth0: Done tulip_open(), CSR0 00008000,
CSR5
> 02260010 CSR6 814c2002.
> Apr 17 20:54:54 pegasus kernel: eth0: interrupt  csr5=0x02670014 new
> csr5=0x02660010.
> Apr 17 20:54:54 pegasus kernel: eth0: interrupt  csr5=0x02660010 new
> csr5=0x02660010.
> Apr 17 20:54:54 pegasus kernel: eth0: exiting interrupt, csr5=0x2660010.
> Apr 17 20:54:54 pegasus kernel: eth0: interrupt  csr5=0x02670014 new
> csr5=0x02660010.
> Apr 17 20:54:54 pegasus kernel: eth0: interrupt  csr5=0x02660010 new
> csr5=0x02660010.
> Apr 17 20:54:54 pegasus kernel: eth0: exiting interrupt, csr5=0x2660010.
> Apr 17 20:54:54 pegasus kernel: eth0: interrupt  csr5=0x02670014 new
> csr5=0x02660010.
> Apr 17 20:54:54 pegasus kernel: eth0: interrupt  csr5=0x02660010 new
> csr5=0x02660010.
> Apr 17 20:54:54 pegasus kernel: eth0: exiting interrupt, csr5=0x2660010.
> Apr 17 20:54:54 pegasus kernel: eth0: interrupt  csr5=0x02670014 new
> csr5=0x02660010.
> Apr 17 20:54:54 pegasus kernel: eth0: interrupt  csr5=0x02660010 new
> csr5=0x02660010.
> Apr 17 20:54:54 pegasus kernel: eth0: exiting interrupt, csr5=0x2660010.
> Apr 17 20:54:54 pegasus kernel: eth0: interrupt  csr5=0x02670014 new
> csr5=0x02660010.
> Apr 17 20:54:54 pegasus kernel: eth0: interrupt  csr5=0x02660010 new
> csr5=0x02660010.
> Apr 17 20:54:54 pegasus kernel: eth0: exiting interrupt, csr5=0x2660010.
> Apr 17 20:54:54 pegasus kernel: eth0: interrupt  csr5=0x02670014 new
> csr5=0x02660010.
> Apr 17 20:54:54 pegasus kernel: eth0: interrupt  csr5=0x02660010 new
> csr5=0x02660010.
> Apr 17 20:54:54 pegasus kernel: eth0: exiting interrupt, csr5=0x2660010.
> Apr 17 20:54:56 pegasus kernel: eth0: PNIC negotiated capability 00000080,
> CSR5 02660010.
> Apr 17 20:54:56 pegasus kernel: eth0: PNIC MII PHY status 782d, Link
partner
> report 0080, csr6 814c0000/814c2002.
> Apr 17 20:54:56 pegasus kernel: eth0: interrupt  csr5=0x02678016 new
> csr5=0x02660010.
> Apr 17 20:54:56 pegasus kernel: eth0: interrupt  csr5=0x02670014 new
> csr5=0x02660010.
> Apr 17 20:54:56 pegasus kernel: eth0: interrupt  csr5=0x02660010 new
> csr5=0x02660010.
> Apr 17 20:54:56 pegasus kernel: eth0: exiting interrupt, csr5=0x2660010.
> Apr 17 20:55:56 pegasus kernel: eth0: PNIC negotiated capability 00000080,
> CSR5 02660010.
> Apr 17 20:55:56 pegasus kernel: eth0: PNIC MII PHY status 782d, Link
partner
> report 0080, csr6 810e0000/810e2002.
> Apr 17 20:56:56 pegasus kernel: eth0: PNIC negotiated capability 00000080,
> CSR5 02660010.
> Apr 17 20:56:56 pegasus kernel: eth0: PNIC MII PHY status 782d, Link
partner
> report 0080, csr6 810e0000/810e2002.
> Apr 17 20:57:07 pegasus kernel: eth0: interrupt  csr5=0x02670014 new
> csr5=0x02660010.
> Apr 17 20:57:07 pegasus kernel: eth0: interrupt  csr5=0x02660010 new
> csr5=0x02660010.
> Apr 17 20:57:07 pegasus kernel: eth0: exiting interrupt, csr5=0x2660010.
> Apr 17 20:57:08 pegasus kernel: eth0: interrupt  csr5=0x02670050 new
> csr5=0x02660010.
> Apr 17 20:57:08 pegasus kernel:  In tulip_rx(), entry 0 010f0708.
> Apr 17 20:57:08 pegasus kernel:  In tulip_rx(), entry 0 010f0708.
> Apr 17 20:57:08 pegasus kernel: eth0: interrupt  csr5=0x02660010 new
> csr5=0x02660010.
> Apr 17 20:57:08 pegasus kernel: eth0: exiting interrupt, csr5=0x2660010.
> Apr 17 20:57:12 pegasus kernel: eth0: interrupt  csr5=0x02670014 new
> csr5=0x02660010.
> Apr 17 20:57:12 pegasus kernel: eth0: interrupt  csr5=0x02660010 new
> csr5=0x02660010.
> Apr 17 20:57:12 pegasus kernel: eth0: exiting interrupt, csr5=0x2660010.
> Apr 17 20:57:17 pegasus kernel: eth0: interrupt  csr5=0x02670014 new
> csr5=0x02660010.
> Apr 17 20:57:17 pegasus kernel: eth0: interrupt  csr5=0x02660010 new
> csr5=0x02660010.
> Apr 17 20:57:17 pegasus kernel: eth0: exiting interrupt, csr5=0x2660010.
> Apr 17 20:57:22 pegasus kernel: eth0: interrupt  csr5=0x02670014 new
> csr5=0x02660010.
> Apr 17 20:57:22 pegasus kernel: eth0: interrupt  csr5=0x02660010 new
> csr5=0x02660010.
> Apr 17 20:57:22 pegasus kernel: eth0: exiting interrupt, csr5=0x2660010.
> Apr 17 20:57:56 pegasus kernel: eth0: PNIC negotiated capability 00000080,
> CSR5 02660010.
> Apr 17 20:57:56 pegasus kernel: eth0: PNIC MII PHY status 782d, Link
partner
> report 0080, csr6 810e0000/810e2002.
> Apr 17 20:58:08 pegasus kernel: eth0: interrupt  csr5=0x02670050 new
> csr5=0x02660010.
> Apr 17 20:58:08 pegasus kernel:  In tulip_rx(), entry 1 01060708.
> Apr 17 20:58:08 pegasus kernel:  In tulip_rx(), entry 1 01060708.
> Apr 17 20:58:08 pegasus kernel: eth0: interrupt  csr5=0x02660010 new
> csr5=0x02660010.
> Apr 17 20:58:08 pegasus kernel: eth0: exiting interrupt, csr5=0x2660010.
> Apr 17 20:58:14 pegasus kernel: VFS: Disk change detected on device 02:28
> Apr 17 20:58:22 pegasus kernel: eth0: interrupt  csr5=0x02670015 new
> csr5=0x02660010.
> Apr 17 20:58:22 pegasus kernel: eth0: interrupt  csr5=0x02660010 new
> csr5=0x02660010.
> Apr 17 20:58:22 pegasus kernel: eth0: exiting interrupt, csr5=0x2660010.
> Apr 17 20:58:56 pegasus kernel: eth0: PNIC negotiated capability 00000080,
> CSR5 02660010.
> Apr 17 20:58:56 pegasus kernel: eth0: PNIC MII PHY status 782d, Link
partner
> report 0080, csr6 810e0000/810e2002.
>
> The above was created by issuing ping command. 100% lost packets.
> Any help would be appreciated.
>
> Mike Rayborn
>
>



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

From: Stephen Carville <[EMAIL PROTECTED]>
Subject: Re: DHCP client questions
Date: Sat, 17 Apr 1999 22:41:38 -0700

Mark Cooperstein wrote:
> 
> I am shamefully ignorant about DHCP and am having problems.  I have kernel
> 2.2.3.  Previously, I used static IP and /etc/hosts.  All worked just fine.
> Now, I have a Cisco ISDN router which is providing DHCP server services.  My
> Windows PC's can get a DHCP IP/lease.  They also get DNS servers from DHCP as
> well as gateway IP.  Linux, however, gets squat!  When I try bring up eth0, I
> get the following messages in /var/log/messages:
> 
> Apr 16 18:23:01 frodo dhcpcd[1118]: ioctl SIOCSIFBRDADDR (ifConfig):
> Cannot assign requested address
> 
> Now, I've been using netcfg under X to configure my network.  For the eth0
> device, I've specifed the protocol to be dhcp, and I've given the host name to
> be 'frodo'.  Under the 'routing' tab, I've enabled IPV4 and that's all.
> 
> So, what's going on?  Do I need additional kernel support, or perhaps some
> other piece of software?

Which version of dhcpcd are you using?  The 0.70 version does not work with
the 2.2.X kernels.

If you are using a correct version, do your logs tell you any other things
like is there DHCPOFFER messages being recieved?

-- 
Stephen Carville
[EMAIL PROTECTED]
====================================================
It's all right to have geniuses build systems for use by idiots, but 
the path from laboratory to marketplace needs to go through the 
proving ground of prudent engineering.
                                        Peter Coffee

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

From: "Larry Ash" <[EMAIL PROTECTED]>
Subject: dhcp and 255.255.255.255 a new twist
Date: Sat, 17 Apr 1999 10:08:01 -0600

I have configured dhcpd on a RH 5.2 box with three network interfaces.
(Don't ask, that part is a long story.)
DHCP correctly sees the inbound interface and assigns an address
apropriate for the inbound subnet.

It then needs to respond to the client sending to broadcast  address of
255.255.255.255.

The problem, the routing code wants to send this address out one
interface. (Actually loopback always gets a packet also) It needs to go out,
as a minimum, the inbound interface, or lacking that, all three. If I enter
three route commands the machine selects one of the three (usually the one
that the default route is one) and sends it there.

The question, is there a way to make a linux machine flood a broadcast to
all interfaces.

Thanks in advance




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

From: Ingo Buescher <[EMAIL PROTECTED]>
Crossposted-To: comp.security.ssh,linux.redhat.misc,comp.os.linux.misc
Subject: Re: Problem compiling SSH-1.2.26 under Redhat Starbuck release 5.9.7...
Date: 17 Apr 1999 20:05:41 GMT

tester <[EMAIL PROTECTED]> wrote:
> I get an error in login.c...  Anyone know how to fix this?
> -DTIS_MAP_FILE=\"/etc/sshd_tis.map\" -g -O2 -I/usr/X11R6/include login.c
> login.c: In function `record_login':
> login.c:437: structure has no member named `ut_syslen'
> login.c:441: structure has no member named `e_termination'
> login.c:442: structure has no member named `e_exit'
> login.c:454: `WTMPX_FILE' undeclared (first use in this function)
> login.c:454: (Each undeclared identifier is reported only once
> login.c:454: for each function it appears in.)
> make: *** [login.o] Error 1

I had exactly the same problem. To solve this remove the
HAVE_UTMPX_H entry in config.h after configuring.


IB
===============================================================
Ingo Buescher <[EMAIL PROTECTED]>
              <[EMAIL PROTECTED]>

Fingerprint: D9C3 0899 78BF 15DF 0C99  B6B2 EFFC 8DF1 BAB7 703F
G-Code: [Sph:s FHu Oeu WTn Sxm ~1200/~30 Sz+ CS-12 PT-12/13 M++
         Tc+ R--- H0 | A--- W-- EF++ S-- C G* CR | RLBM/RLMA a
         cl++ e+ h+ i+ j-- o-]

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

From: Stephen Carville <[EMAIL PROTECTED]>
Subject: Re: DHCP
Date: Sat, 17 Apr 1999 22:47:58 -0700

William Smith wrote:
> 
> I have a tokenring (IBM Turbo 16/4) I've been trying for 2 week to get
> it on an NT network, using DHCP server to assign IP's, U'm told that all
> I have to do is make sure the card is connect to the network at boot
> time and it is, and it works fine when I boot into Win95 we us Microsoft
> Window Login to get into the domain is there some here that I missed in
> the Howto is it even possible to connect to a DHCP server using Linux,
> or can someone please point me to a website that has info on doing this.

Whcih version of dhcpcd are you using?  There is a bug in the 0.70 version
most people are using now that causes the DHCPREQUEST message to be
encapsulated as a BOOTP rather than a DCHP packet.  If your DHCP server is
on a different subnet than you are the router is probably configured as a
forwarding agent and will allmost certainly drop the DHCPREQUEST (since it
is BOOTP) and your server never sees the request.

-- 
Stephen Carville
[EMAIL PROTECTED]
====================================================
It's all right to have geniuses build systems for use by idiots, but 
the path from laboratory to marketplace needs to go through the 
proving ground of prudent engineering.
                                        Peter Coffee

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

From: "alvin" <[EMAIL PROTECTED]>
Subject: What is the load of this setup ??
Date: Mon, 12 Apr 1999 19:37:58 +0800

Hi,

I have a question which i can't seem to find answer.
i've setup an amd k6-2 333MHZ cpu with 64MB ram and 6.4GB IDE harddisk
(UDMA)
the network is running 100MBps, and runing as a file server using samba.
how many max users can this setup take ??

What if i setup web server, internal email server (smtp and pop) and gateway
to the internet on the same box, how many user can it handle now ??
btw, my internet acces is thru a 56kbps dial-up modem.


Thanks in advance for answers.

:)



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

From: Stephen Carville <[EMAIL PROTECTED]>
Subject: Re: DHCPD and BIND Rumor?
Date: Sat, 17 Apr 1999 22:51:06 -0700

Anthony Ewell wrote:
> 
> Hi,
> 
> I heard a rumor that DHCPD and BIND will now talk to each other.
> Can anyone confirm or deny this?  If true, is there a HOWTO on
> linking the two together?

There are many people -- like me -- that are tying them together using perl
scripst but AFAIK it is not yet built into dhcpd.  Version three is
supposed to do this.

-- 
Stephen Carville
[EMAIL PROTECTED]
====================================================
It's all right to have geniuses build systems for use by idiots, but 
the path from laboratory to marketplace needs to go through the 
proving ground of prudent engineering.
                                        Peter Coffee

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

From: mist <[EMAIL PROTECTED]>
Subject: Re: What's supposed to be in (now) TCP port 113?
Date: Sun, 18 Apr 1999 11:31:27 +0100
Reply-To: mist <new$[EMAIL PROTECTED]>

jmsalvo <[EMAIL PROTECTED]> scribed to us that -
>
>
>> > That's most likely because Sendmail attempts an IDENT on whoever telnets
>> > to your SMTP port.
>>
>
>Furthermore, why would anyone forward mail through my SMTP port when I only
>have a single-machine, dial-up connection????.... unless they are spammers or
>trying to hack-in?
>

In my case, because that is how I receive mail from my ISP.  In your
case, maybe the same, maybe because someone is trying to send you mail
direct, maybe its your own mail going *outbound* and maybe, maybe it is
a spammer trying to relay mail.   Without seeing some of the logs I
couldn't really say.  Mail some if you like. /var/log/maillog normally.

-- 
Mist.
http://www.misthaven.demon.co.uk/

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

From: mist <[EMAIL PROTECTED]>
Subject: Re: What's supposed to be in (now) TCP port 113?
Date: Sun, 18 Apr 1999 11:35:56 +0100
Reply-To: mist <new$[EMAIL PROTECTED]>

jmsalvo <[EMAIL PROTECTED]> scribed to us that -

<snip>

>
>So whoever was telnetting to my SMTP port, my IDENT asks that host and that
>host is getting the response back?

Yes.

> Geeez, I've been reading O'Reilly'
>"Building Internet Firewalls" and it never did mentioned about that (nor of
>IRC servers doing ths same thing) .... must read the RFCs.
>

I'm not sure the RFCs are particularly important in this case. 

>> That's a security measure for your benefit, but
>> obviously IDENT could be used in the reverse direction to find out
>> information about your network.  (I don't know the specifics of that.)
>
>Hmmm ..... So there's no way to identify between an incoming IDENT request (I
>am the server) from an external host versus an outgoing IDENT request (I am
>the client) where I am making a connection .... like different ports? I
>better read the RFCs.
>

Well.  IIRC, an incoming request [getting info from you] will originate
from "any old port" and come into your IDENT port, whilst an outgoing
request [wanting info from elsewhere] would start from your [any old]
port and go to the other machine's IDENT port.  So I suppose you could
firewall off any access to your own IDENT port.  How this might affect
other things I don't know.  You could also comment out the "auth" entry
in /etc/inetd.conf and restart inetd if it bothers you.  Then noone can
request stuff from your machine. (Sendmail will still work.)


<snip>
-- 
Mist.
http://www.misthaven.demon.co.uk/

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

From: Stephen Carville <[EMAIL PROTECTED]>
Subject: usertty
Date: Sat, 17 Apr 1999 22:58:16 -0700

Has anyone been able to get /etc/usertty to work?  I have enterd the
following rules but it doesn't seem to restrict logins at all:

CLASSES
localtty        tty1 tty2 tty3 tty4 tty5 tty6 tty7 tty8
localnet        @192.168.1.0/255.255.255.0
localhost       @localhost

GROUPS

USERS
user    localtty localnet localhost 

These rules should restrict "user" from logging in from an off net site but
they don't 

Any ideas?

-- 
Stephen Carville
[EMAIL PROTECTED]
====================================================
It's all right to have geniuses build systems for use by idiots, but 
the path from laboratory to marketplace needs to go through the 
proving ground of prudent engineering.
                                        Peter Coffee

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

From: Glenn Graham <[EMAIL PROTECTED]>
Subject: NFS WITHIN AN IP MASQ FIREWALL (fwd)
Date: Sat, 17 Apr 1999 22:46:28 -0700



============================================================
inTEXT Communications
Vancouver BC

========== Forwarded message ==========
Date: Sat, 13 Mar 1999 22:04:25 -0800
From: Glenn Graham <[EMAIL PROTECTED]>
Newsgroups: alt.linux.slakware
Subject: NFS WITHIN AN IP MASQ FIREWALL


This may be an orriginal question and any help would be very much
appreciated.

Here's my situation.  I'll draw a mapped diagram at the bottom to further
explain.

I have several machines connected within a LAN, and connected to the
outside internet using a linux box running IP-masq ( NAT )

The machines inside my lan, all run linux as well.

I am attempting to mount via NFS, to a machine on the outside internet.

The NFS server on the outside has, in it's /etc/exports file,
the ip number of the machine on my end, which is hosting for ip-masq
as rw,no_root_squash

I am able to successfully establish an NFS mount from my ip-masq box, to
the box which I wish to mount to.

Now... When I attempt to do a mount from within my ip-masq LAN, to the
same machine on the outter internet, it attempts a connection to
the outter machine, but the connection is refused by the outter machine,
due to the fact that ip-masq is assigning it an Illegal Port number.
I note this by the /var/log/messages file from the NFS Server which reads
NFS from  xxx.xxx.xxx.xxx on ILLEGAL port number.


Here's a diagram ( I do better at most other things, but not well at
diagrams )
                                                   Inner Lan Machines
                           ipmasq box              X <--trying to estab.
OUTTER NFS SERVER          _____                   |    nfs to outter
|---|_____________________|     |__________________|    from these boxes
|---|                     |_____|                  |
                                                   X <---

If there was some way, I could convince NFS to assign say
perhaps ( and I'm guessing port # 2048 ) then I would be able
to connect from within the ip masq LAN to the outside.

Has anyone come across any solution to this.. or better yet, has anyone
been crazy enough to attempt this yet ??

Any replies to this please direct to my email account:
[EMAIL PROTECTED]

Thank you all in advance.

Yours.. Glenn Graham... Vancouver BC


============================================================
inTEXT Communications
Internet Security              Unix Networking Specialist
http://www.intextonline.com    [EMAIL PROTECTED]



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


** 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