Linux-Networking Digest #306, Volume #12 Fri, 20 Aug 99 20:13:54 EDT
Contents:
Re: problems with 2 networks (Peter Buelow)
Re: failing network connection (Luc De Cock)
Re: Telnet thru' a firewall, any backdoor ??? (Peter Buelow)
Re: Ping Timeout? (Bill Pitz)
routing 2 networks (Tiberio, David)
FDDI Cards (Brent Paddon)
Re: Telnet thru' a firewall, any backdoor ??? ("End User")
Linux Friendly UK ISP's? ("Andrew Taylor")
Re: Cracks for Linux? (Oleg Letsinsky)
Re: problems with 2 networks (hollywoodjoe)
Re: NE2000 ISA help ("John Bekas, Jr.")
Re: Samba's last stand! (Ronald Cole)
Re: ip-masquerading ("eelco of viola")
Re: Netgear FA310 and Micronics W6Li (John Meissen)
CNet's PRO120 and Linux? (Woojin Lee)
Re: Why not C++ (Kaz Kylheku)
----------------------------------------------------------------------------
From: Peter Buelow <[EMAIL PROTECTED]>
Subject: Re: problems with 2 networks
Date: Fri, 20 Aug 1999 15:08:25 -0500
Tiberio, David wrote:
>
> does this look correct? the TX and RX don't look right to
> me!
>
> I have 2 dsl lines and 2 nic cards for this machine, one
> nic card on each dsl line
>
> Kernel IP routing table
> Destination Gateway Genmask Flags MSS
> Window irtt Iface
> 216.46.85.16 * 255.255.255.240 U 1500
> 0 0 eth0
> 216.32.200.0 * 255.255.255.0 U 1500
> 0 0 eth1
> loopback * 255.0.0.0 U 3584
> 0 0 lo
> default 216.32.200.1 0.0.0.0 UG 1500
> 0 0 eth1
> default 216.46.85.17 0.0.0.0 UG 1500
> 0 0 eth0
>
> 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:65381538 errors:0 dropped:0 overruns:0
> frame:0
> TX packets:65381538 errors:0 dropped:0 overruns:0
> carrier:0
> Collisions:0
>
> eth0 Link encap:Ethernet HWaddr 00:A0:CC:51:BE:DE
> inet addr:216.46.85.20 Bcast:216.46.85.31
> Mask:255.255.255.240
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:2111377 errors:0 dropped:0 overruns:0
> frame:0
> TX packets:74813 errors:0 dropped:0 overruns:0
> carrier:0
> Collisions:114
> Interrupt:11 Base address:0xdc00
>
> eth1 Link encap:Ethernet HWaddr 00:40:05:42:CF:49
> inet addr:216.32.200.14 Bcast:216.32.200.255
> Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1711303 errors:0 dropped:0 overruns:0
> frame:0
> TX packets:4178344 errors:0 dropped:0 overruns:0
> carrier:0
> Collisions:88320
> Interrupt:10 Base address:0xd880
>
> * Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
> The fastest and easiest way to search and participate in Usenet - Free!
Do you have an actual problem? Collisions might be a little high, but
DSL is new, and you may have had outside network problems one morning
(or something like that), so who knows? But the TX/RX doesn't look so
bad. Looks like they have been running for a while and you are
downloading a ton on eth0. Seems a little split, but if you aren't
having any problems, why worry? Don't second guess the kernel for the
most part. If you are having problems, then post the problems here and
people will have at them.
--
Peter Buelow - Software Engineer
Motorola - Common Platform Group - (847)632-6390
--
"Finger to spiritual emptiness underlying everything." -- How a C manual
referred to a "pointer to void."
------------------------------
From: Luc De Cock <[EMAIL PROTECTED]>
Crossposted-To: be.comp.os.linux,linux.redhat
Subject: Re: failing network connection
Date: Fri, 20 Aug 1999 19:39:08 +0200
Bjorn Comhaire wrote:
> Hi,
>
> I have a pentium running redhat 5.2 and win95, with a 3com 3c509 network
> card.
>
> For some reason currently not known to me (off course) the box won't connect
> to my LAN. I've reinstalled the 5.2 but the same thing occured again. Here
> are some facts:
>
> UTP connection
> i/o=0x300 ==> no conflicts
> irq=10 ==> no conflicts
> ping myself: OK
> ping another computer on the network: eth0 timeout !!
> The office hub does NOT show a connection with the box !!
>
> When I restart win95, everything works fine again.
>
> I guess the card is working fine but for some reason won't interact with the
> outside world when configured in linux.
>
> Any tips or other help would be very much appreciated.
> Bj�rn
The 3COM 3C509 card is normally configured to detect the media automaticly.
This
will confuse the 3c509 driver from Becker that it will choose the wrong media.
Try putting the card on a fix media type, eg UTP or BNC but NOT autodetect.
Luc.
------------------------------
From: Peter Buelow <[EMAIL PROTECTED]>
Crossposted-To:
comp.sys.sun.admin,comp.unix.admin,comp.os.linux.setup,comp.unix.misc,comp.unix.questions,comp.os.ms-windows.nt.admin.networking,comp.os.ms-windows.apps.winsock
Subject: Re: Telnet thru' a firewall, any backdoor ???
Date: Fri, 20 Aug 1999 15:34:41 -0500
[EMAIL PROTECTED] wrote:
>
> Dear TCP/IP Gurus,
>
> I have several machines on a subnet "behind" a corporate firewall
> which disables any telnet access to the outside world.
>
> The firewall allows HTTP and POP3 but denies FTP and Telnet.
>
> Is there any __backdoor__ which allows our machines telnet'ing
> to the outside world ?
>
> Please drop a copy of your hint to my email
> [EMAIL PROTECTED]
>
> Thanks in advance!
> KiT
Try the other two suggestions, but most corp firewalls filter on
content, not port numbers. My corp firewall even goes so far as to block
any traffic that does not contain a valid HTTP/1.0 or 1.1 header on any
port going through the http proxy. Wrote my own browser a while back in
college and it doesn't work here because I didn't follow the rules to
some degree (cheated you could say) cause it didn't matter back then. I
don't believe the other solutions will work for this reason though. To
get through the proxy, you have to connect to the proxy and telnet
doesn't allow multiple address to connect to. For instance, you would
have to telnet to http.proxy.com:8080 and then from there, telnet to the
address. Since the proxy only understands HTTP requests, it won't know
to continue on. If all else fails, you will have to be tunneling
creative (I'm currently working on a little tunneling ICQ proxy to get
around our firewall problem) with a software solution. It all depends on
how anal and aware your administrators are. Less anal and aware, more
chance there is a hole and vice-versa.
--
Peter Buelow - Software Engineer
Motorola - Common Platform Group - (847)632-6390
--
"Finger to spiritual emptiness underlying everything." -- How a C manual
referred to a "pointer to void."
------------------------------
From: Bill Pitz <[EMAIL PROTECTED]>
Subject: Re: Ping Timeout?
Date: Fri, 20 Aug 1999 21:29:25 GMT
Bradley Dunn <[EMAIL PROTECTED]> gave us the interesting posting of:
> -c count
> Stop after sending (and receiving) count ECHO_RESPONSE packets.
> This is straight from man, as you can see -c stops after X count number of
> packets are received, not after a give amount of time, so if a server was
> doing ping -c 1 mydownserver.com should sit and wait forever.
Duh, I have read the man page. Apparently you didn't understand my post.
The question was is there a way to CHANGE THIS PARAMETER.
------------------------------
From: Tiberio, David <[EMAIL PROTECTED]>
Subject: routing 2 networks
Date: Fri, 20 Aug 1999 10:47:57 -0700
I need help in routing my 2 networks.
I have 8 servers and 2 SDSL lines. I want half of my
machines to be accessible through both DSL lines, some
of them only on one line, and some only available
internally.
I have DLINK DSH5 and DSH 8 hub/switches. Most of my
machines have 2 nic cards installed, running linux 2.2 or
in some cases 2.0
I am using slackware.
what should my rc.inet1 file contain?
here is what I have. I realize that it is probably
completely wrong. in some cases it seems to work, in others
one nic will work and the other is down and then they flip
so the other suddenly works and the working one goes down.
/sbin/ifconfig lo 127.0.0.1
/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
IPADDR="216.46.85.20"
NETMASK="255.255.255.240"
NETWORK="216.46.85.16"
BROADCAST="216.46.85.31"
GATEWAY="216.46.85.17"
/sbin/ifconfig eth0 216.46.85.20 broadcast 216.46.85.31
netmask 255.255.255.240
/sbin/ifconfig eth1 216.32.200.14 broadcast 216.32.200.255
netmask 255.255.255.0
/sbin/route add -net ${NETWORK} netmask ${NETMASK} eth0
/sbin/route add -net 216.32.200.0 netmask 255.255.255.0 eth1
if [ ! "$GATEWAY" = "" ]; then
/sbin/route add default gw ${GATEWAY} netmask 0.0.0.0
metric 1 eth0
/sbin/route add default gw 216.32.200.1 netmask 0.0.0.0
metric 1 eth1
fi
also, ho would I add a machine to this that is only
reachable locally (192.168.x.x)?
* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!
------------------------------
From: Brent Paddon <[EMAIL PROTECTED]>
Subject: FDDI Cards
Date: 21 Aug 1999 07:24:54 +1000
Hi,
I'm interested in putting an FDDI card into a Linux based
router - has anyone here had any experience with FDDI
and linux they're willing to share?
Thanks
Brent
--
----
Brent Paddon Managing Director
[EMAIL PROTECTED] http://www.bit.net.au/
Brisbane Internet Technology Pty Ltd Ph : +61 7 3252-1600
------------------------------
From: "End User" <[EMAIL PROTECTED]>
Crossposted-To:
comp.sys.sun.admin,comp.unix.admin,comp.os.linux.setup,comp.unix.misc,comp.unix.questions,comp.os.ms-windows.nt.admin.networking,comp.os.ms-windows.apps.winsock
Subject: Re: Telnet thru' a firewall, any backdoor ???
Date: Fri, 20 Aug 1999 16:56:53 -0500
If you were the firewall admin, you would know the answer to this question.
Since you dont know, I can only suppose you are not supposed to.
I cannot help you snafu the security of your organization. You will have to
buy your admins some beers or women (maybe both) to get them to make the
changes for you.
<[EMAIL PROTECTED]> wrote in message
news:7pjsu5$[EMAIL PROTECTED]...
> Dear TCP/IP Gurus,
>
> I have several machines on a subnet "behind" a corporate firewall
> which disables any telnet access to the outside world.
>
> The firewall allows HTTP and POP3 but denies FTP and Telnet.
>
> Is there any __backdoor__ which allows our machines telnet'ing
> to the outside world ?
>
> Please drop a copy of your hint to my email
> [EMAIL PROTECTED]
>
> Thanks in advance!
> KiT
>
------------------------------
From: "Andrew Taylor" <[EMAIL PROTECTED]>
Subject: Linux Friendly UK ISP's?
Date: Fri, 20 Aug 1999 23:08:42 +0100
Hi,
I'm currently using a standard demon dial up account, for �11.75 I get
unlimited dial up access, 20MB webspace, a subdomain name, fixed IP address
and SMTP delivery? Are they're any other ISP's which also provide these
facilites and are easy to get going under linux?
Andy
------------------------------
From: Oleg Letsinsky <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.misc
Subject: Re: Cracks for Linux?
Date: 21 Aug 1999 01:58:16 +0400
[EMAIL PROTECTED] (Kaz Kylheku) writes:
> I tried the 4Front technologies driver for my sound card. It locked up my
> kernel hard so I never looked back at the crap again. That is just lousy
> programming.
>
> I wish that a hole in the ground would open up and swallow up these guys. Not
> only do their drivers suck, but they are also getting in the way of free sound
> development by getting into bed with manufacturers who then don't want to
> release specs.
I'd second that. The fact that there is a company which signs NDA and
releases closed-source drivers for soundcards disturbs me. Look at
Aureal's WWW site, 'Drivers' page. There are drivers for Windows 9x
(of cause :-/), Windows NT, Win 3.1 (what?!), OS/2(err... I'm not
sure, what these letters mean? :-))... There are no fscking drivers
for Linux, only link to www.opensound.com. 'OpenSound', my ass!
Why is it 'open'? Is it a joke?
$20 for soundcard, which itself costs < $20, and *no sources*? Sorry -
no source - no love. But the problem is that Aureal doesn't seem to
care about releasing specs on their hardware, since 'drivers' for
Linux already 'exist'.
--
This .sig is shareware ($10). Register now to get the full 10MB version!
------------------------------
From: hollywoodjoe <[EMAIL PROTECTED]>
Subject: Re: problems with 2 networks
Date: Fri, 20 Aug 1999 15:59:02 -0700
In article <[EMAIL PROTECTED]>, Peter Buelow
<[EMAIL PROTECTED]> wrote:
> Do you have an actual problem?
yes, I am having odd problems.
some of my machines cannot be accessed from outside my
network, and some can. and sometimes it flip-flops. for
example, machine A has 2 nics with an ip each on each
network, and is reachable on one network and not the
other, then suddenly the reverse is true
also getting tons of packet loss (30%) and my line is
only 25% used
also, packet loss flips between machines. one machine
will have 10% packet loss for a few hours, then suddenly
another machine does for a few hours, and then back to the
first machine. I have graphs that show it right to the
minute. I am pinging from work.
I have problems where I cannot ping a machine but I
can telnet to it, and then maybe a few minutes later I
can't telnet but I can ping
and I get disconnected constantly
* Sent from RemarQ http://www.remarq.com The Internet's Discussion Network *
The fastest and easiest way to search and participate in Usenet - Free!
------------------------------
From: "John Bekas, Jr." <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.hardware,redhat.hardware.arch.intel
Subject: Re: NE2000 ISA help
Date: Fri, 20 Aug 1999 13:32:32 -0500
All the success stories thus far have related to loading the driver as a
module. Any successes with the driver compiled into the kernel?
John
------------------------------
From: Ronald Cole <[EMAIL PROTECTED]>
Subject: Re: Samba's last stand!
Date: 20 Aug 1999 11:27:38 -0700
"Hiawatha Bray" <[EMAIL PROTECTED]> writes:
> Thanks for a lucid and informative message.
>
> But here's where things get messy...I try to log into the share using
> my Linux password and it's rejected. Then I go to the Linux box and
> try to run smbpasswd, to give the user an SMB password. It doesn't
> work. It asks for my old SMB password, and of course there isn't any.
> So when I try to set up a new password it says it can't change my
> password. This is bizarre. How do you set the SMB password for the
> user? Thanks.
Nuke smbpasswd and run 'smbpasswd -a' as root. Also look at the log
files to see if you can determine what Samba says the problem is
(/var/log/samba/*.log).
--
Forte International, P.O. Box 1412, Ridgecrest, CA 93556-1412
Ronald Cole <[EMAIL PROTECTED]> Phone: (760) 499-9142
President, CEO Fax: (760) 499-9152
My PGP fingerprint: 15 6E C7 91 5F AF 17 C4 24 93 CB 6B EB 38 B5 E5
------------------------------
From: "eelco of viola" <[EMAIL PROTECTED]>
Subject: Re: ip-masquerading
Date: Fri, 20 Aug 1999 20:38:25 +0200
catsquotl <[EMAIL PROTECTED]> schreef in berichtnieuws
[EMAIL PROTECTED]
that is me .
I finaly got it working . I had to enable ip_forwarding in
/proc/sys/net/ipv4/ip_forward
Try finding thatone as a newbee.
annyway thank you all for trying to help...
George thanks for clearing up the network vs machine thing
greets eelco
------------------------------
From: [EMAIL PROTECTED] (John Meissen)
Crossposted-To: comp.os.linux.hardware
Subject: Re: Netgear FA310 and Micronics W6Li
Date: 20 Aug 1999 23:50:12 GMT
In article <[EMAIL PROTECTED]>, Bill Pitz <[EMAIL PROTECTED]> wrote:
>In comp.os.linux.networking John Meissen <[EMAIL PROTECTED]> wrote:
>> Now, I could say OK, I have a workaround, but I need =2= NICS
>> in this machine.
>
>> So, is this some new restriction with this NIC, or is there
>> some bizarre restriction in the BIOS for this motherboard?
>
>The first thing you need to do is go download the latest tulip.c source
>from Donald Becker's web site and compile that into your kernel.
I plan on trying that, but I don't expect much success. As I said,
it works fine in slot 0. The point is, the message is coming from
a BIOS level activity, long before the system is booted. I've
never heard of this with the Netgear card before, and I managed
to talk to a support person at Micronics->Orchid->Diamond who
could find no references to anything even remotely similar.
I tried to find something, anything, in the CMOS settings that
might be related, but without success.
<sigh> My two cards with the Digital chips certainly don't
care. I guess I'm going to have to start dismantling systems
and swapping parts.
>I sure wish that we could still get the good solid DEC chips :)
>
You and me, both!
john-
------------------------------
From: Woojin Lee <[EMAIL PROTECTED]>
Subject: CNet's PRO120 and Linux?
Date: Fri, 20 Aug 1999 15:03:09 -0400
Hi.
I'd like to find out if CNet's Pro120 10/100BT NIC would work with
Linux.
I'm using Mandrake 6.0.
Thanks in advance.
Woojin
------------------------------
From: [EMAIL PROTECTED] (Kaz Kylheku)
Crossposted-To: comp.os.linux.development.apps,comp.os.linux.development.system
Subject: Re: Why not C++
Date: Fri, 20 Aug 1999 18:56:03 GMT
On 20 Aug 1999 09:25:08 -0400, Johan Kullstam <[EMAIL PROTECTED]> wrote:
>and it would be nice to be able put in a goto of some sort to do
>something useful.
>
> writeh(array, size, fd, goto disk_full);
>
>and failed writes could jump to some recovery code.
The above might not be C syntax, but a macro can give it to you.
I've maintained code in which REQUIRE() macros were used heavily to do this
kind of thing. These macros would jump to a given statement label if a certain
condition were found to be false, and log a message. These were only used
because the code had to work in C++ environments that do not support exception
handling.
C gives you setjmp and longjmp that can be used to implement exception handling
that is quite functional. I have written a tiny package which can give C
programs structured exception handling. You can have nested try blocks, and
exceptions that are divided into groups so you can catch by group as well as
specific ID. The calling of cleanup handlers is supported in the unwinding
process. Unhandled exceptions go to a default handler which can be overriden
by a pointer to a user-supplied function.
>it might be nice to have functions check for stuff automatically and
>by default unless told otherwise. then it wouldn't be such a royal
>pain. computers are great at filling the details. they don't get
>tired of repitition. let the computer do the religious checking!
This is achieved to some extent exception handling. In C++, operator new now
is required to throw an exception if allocation fails, unless the nothrow form
is used. If you do not handle the exception, the program is aborted. You can
implement a function called terminate() which catches unhandled exceptions
which can do things other than terminate; for example, re-execute a new
program image. Of course, you do not have a simple compile time switch which
will turn off all your try blocks and let all exceptions be unhandled.
If you want to write a program that does little error checking, just have the
low level functions throw exceptions that are not caught. Without too many
problems, you can implement your own I/O layer which wraps up some
non-exception based I/O functions and translates errors into exception throws.
Such programs would traditionally be peppered with nasty exit calls. In
reality, only certain classes of programs can be written this way, such as
small trivial programs or batch processors such as compilers, which can abort
at the first resource problem or I/O error. In many types of applications,
termination is an unacceptable way of dealing with transient environmental
errors. And even if a shutdown must take place due to a catastrophic failure,
it may be required that resources must be released and everything must be left
in a sane state. E.g. a database would probably want to close all of its tables
properly, or a program with resources that are not automatically deallocated by
the OS would probably want to free them.
------------------------------
** 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
******************************
