Linux-Networking Digest #110, Volume #11 Tue, 11 May 99 01:13:32 EDT
Contents:
ipfwadm ([EMAIL PROTECTED])
Problems with pipes (Christopher Swanson)
Re: LinuxPing -> NTping net problems DEC PCI (Matt)
Re: MediaOne Cable Modem (Carl Karsten)
Re: inbound IP Forwarding to private IP? (Phil DeBecker)
Map Network Drives (Neo)
Mounting network drives? (Neo)
Re: SAMBA: How to get a complete list of computers Netbios name and IP addresses in
a NT network using a SAMBA CLIENT? (Lew Pitcher)
Re: kppp: connect before login & keep connection ([EMAIL PROTECTED])
Re: @HOME Cable Service and Linux ("TiM")
reading Ethernet card address (Victor Kwok)
Frog! @home (ruben)
Re: Reliable (!) nic for 2.2 kernel? (Johan Kullstam)
Re: uplink vs. cross-connect (Matt)
Re: connecting two networks w/o a router?? (Luca Filipozzi)
Re: RedHat-6.0 and port forwarding (Peter Van Doren)
Re: Crossover cable for pc to pc network? ("D. C. & M. V. Sessions")
----------------------------------------------------------------------------
From: [EMAIL PROTECTED]
Subject: ipfwadm
Date: Mon, 10 May 1999 22:56:02 GMT
I am trying to setup transparent proxying on a linux machine. I have all of
the forwarding code built into the kernel. For some reason, ipfwadm keeps
giving me an error. Here is what I am doing:
/sbin/ipfwadm -F -p accept
/sbin/ipfwadm -I -i accept -b -P tcp -S 192.168.1.0/24 -D 0.0.0.0/0 80 -r 3128
I get the error "ipfwadm: setsockopt failed: Invalid argument" when I try the
second line. I see if anything happen:
[root@mail rc.d]# ipfwadm -I -l
IP firewall input rules, default policy: accept
BTW, port 3128 is squid. I got much of my information from sys admin vol8#5,
"Linux Transparent Proxy". Seem simple enough. :) Any help?
---
Dustin Puryear
[EMAIL PROTECTED]
--== Sent via Deja.com http://www.deja.com/ ==--
---Share what you know. Learn what you don't.---
------------------------------
From: Christopher Swanson <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Subject: Problems with pipes
Date: Mon, 10 May 1999 17:16:32 -0700
Hello Everyone,
I am having a problem with what I think is blocking I/O. I have two
processes executing, let's call them server and console. The server
process has two pipes to read from. The problem I am having is: if I try
to read from a pipe that has had nothing written to it, then the process
will wait until the pipe is written to.
Is there a way to check a pipe to see if there is data ready to be read?
Chris
------------------------------
Date: Tue, 11 May 1999 01:13:38 +0100
From: Matt <[EMAIL PROTECTED]>
Subject: Re: LinuxPing -> NTping net problems DEC PCI
Crossposted-To:
comp.os.ms-windows.networking.tcp-ip,comp.os.ms-windows.networking.misc,comp.os.ms-windows.nt.misc
Changed the dummy route to..
route del 192.168.10.2 dev dummy0
and
route del 192.168.10.0 dev eth0
changed to
route add 192.168.10.2 dev eth0
Now I get the comments of..
ping sendto: network is unreachable
I have also changed the cable to a crossover cable too.
Still no luck.
Have you any more ideas, I think I maybe getting there soon,
I feel as though I am getting the idea of this network thing.
Many thanks
Matt
Sylvan Butler wrote:
>
> On Sun, 09 May 1999 09:47:34 +0100, Matt <[EMAIL PROTECTED]> wrote:
> >Pinging to Linux Box from NT ?
> >
> >Pinging 192.168.10.0 with 32 bytes of data:
>
> 192.168.10.0 would be an illegal IP address.
>
> >Pinging NT itsself (same IP addess)
> >Pinging 192.168.10.1 with 32 bytes of data:
>
> 192.168.10.1 is legal.
>
> >Pinging Linux Box ?
>
> Where from?
>
> >Pinging on Linux..
> >
> >% ping 192.168.10.0
> >
> >PING 192.168.10.0 (192.168.10.0): 56 data bytes
> >
> >
> >--- 192.168.10.0 ping statistics ---
> >7 packets transmitted, 0 packets received, 100% packet loss
>
> Yup. That illegal IP again.
>
> >% ping 192.168.10.1
> >
> >PING 192.168.10.1 (192.168.10.1): 56 data bytes
> >
> >--- 192.168.10.1 ping statistics ---
> >6 packets transmitted, 0 packets received, 100% packet loss
>
> OK, a route must be bad.
>
> >% ping 192.168.10.2 (itself)
> >
> >PING 192.168.10.2 (192.168.10.2): 56 data bytes
> >64 bytes from 192.168.10.2: icmp_seq=0 ttl=64 time=0.1 ms
>
> Looks good.
>
> >% netstat -rn
> >
> >Kernel IP routing table
> >Destination Gateway Genmask Flags MSS Window irtt Iface
> >192.168.10.2 0.0.0.0 255.255.255.255 UH 1500 0 0 dummy0
> >192.168.10.0 0.0.0.0 255.255.255.0 U 1500 0 0 eth0
> >127.0.0.0 0.0.0.0 255.0.0.0 U 3584 0 0 lo
> >
> >% route
> >
> >Kernel IP routing table
> >Destination Gateway Genmask Flags Metric Ref Use Iface
> >192.168.10.2 0.0.0.0 255.255.255.255 UH 0 0 0 dummy0
> >192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 2 eth0
> >127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 2 lo
>
> Do you notice that those are both the same?
>
> That route to 192.168.10.2 seems bogus...
>
> What is the 'dummy0' device? Are you perhaps running IPAlias? If so, Why?
>
> I'd probably delete that route to dummy...
> "route del 192.168.10.2"
> But it doesn't appear to be used, so it probably won't matter.
>
> >% ifconfig
> >dummy0 Link encap:10Mbps Ethernet HWaddr 00:00:00:00:00:00
> > inet addr:192.168.10.2 Bcast:192.168.10.255 Mask:255.255.255.0
> > UP BROADCAST RUNNING NOARP MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:0 overruns:0
> > TX packets:0 errors:0 dropped:0 overruns:0
> >
> >eth0 Link encap:10Mbps Ethernet HWaddr 00:40:C7:99:0D:F4
> > inet addr:192.168.10.2 Bcast:192.168.10.255 Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:477 dropped:0 overruns:0
> > TX packets:0 errors:20 dropped:0 overruns:0
> > Interrupt:11 Base address:0xe800
>
> Other than the questionable dummy, that info looks good.
>
> What is the NT netmast, default gw, etc.?
>
> sdb
> --
> | Sylvan Butler | Not speaking for Hewlett-Packard | sbutler-boi.hp.com |
> | Watch out for my e-mail address. Thank UCE. #### change ^ to @ #### |
> They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety. --Benjamin Franklin, 1759
> "Don't Tread On Me!"
------------------------------
From: Carl Karsten <[EMAIL PROTECTED]>
Subject: Re: MediaOne Cable Modem
Date: Mon, 10 May 1999 23:18:07 -0500
Take a look at this http://www.personnelware.com/carl/linux/cmr/
I have been using it for about a year.
^Carl
Doug O'Leary wrote:
> In article <7gu5ee$l2k$[EMAIL PROTECTED]>, [EMAIL PROTECTED] says...
>
> > Go to http://edge.fireplug.net/ and just follow his instructions. It works
> > for @Home cable and I don't see any reason it won't work for MediaOne
> >
>
> The problem is that it doesn't. MediaOne apparently does something
> squirrelly with their DHCP; I've been poking at this thing for months and
> haven't gotten anywhere. I finally gave up and am only using the cable
> modem through win95 - better that than nothing, I guess.
>
> Doug
> --
> ==============
> Douglas K. O'Leary
> Senior System Admin
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> ==============
------------------------------
Date: Thu, 06 May 1999 12:19:16 -0400
From: Phil DeBecker <[EMAIL PROTECTED]>
Subject: Re: inbound IP Forwarding to private IP?
J wrote:
<snip>
> How do I specify that requests coming to external_addr:80 should be
> forwarded to some_internal_addr:80, where some_internal_addr is not on the
> firewall machine?
The simplest thing to do is use ipautofw. Get the package from
http://ipmasq.cjb.net/ipautofw.tar.gz
and install it. You DO NOT need to patch the kernel with the patch included
in the package -- the 2.0.36 kernel includes support for ipautofw. You'll
need to verify that it's turned on in your kernel; if the file
/proc/net/ip_autofw exists then it is, otherwise you'll want to enable it
(under Networking Options) and recompile your kernel.
The syntax is as simple as:
ipautofw -A -r tcp 80 80 -h some_internal_addr
Hope this helps,
Phil
------------------------------
From: Neo <[EMAIL PROTECTED]>
Subject: Map Network Drives
Date: Sat, 08 May 1999 16:52:40 -0700
Im a newbie so please bear with me:
I just finally installed Red Hat linux and win98 on same HD and now Im
trying to get
setup with RH Linux. How do i mount a network drive over LAN?
thanks
Neo
------------------------------
From: Neo <[EMAIL PROTECTED]>
Subject: Mounting network drives?
Date: Sat, 08 May 1999 16:50:18 -0700
Im a newbie so please bear with me:
I just finally installed Red Hat linux and win98 on same HD and now Im trying to
get setup with RH Linux. How do i mount a network drive over LAN?
thanks
Neo
------------------------------
From: [EMAIL PROTECTED] (Lew Pitcher)
Crossposted-To: comp.os.linux,comp.os.linux.help,comp.os.linux.setup
Subject: Re: SAMBA: How to get a complete list of computers Netbios name and IP
addresses in a NT network using a SAMBA CLIENT?
Reply-To: [EMAIL PROTECTED]
Date: Thu, 06 May 1999 12:37:28 GMT
On Thu, 6 May 1999 07:20:13 +0800, "John Wong" <[EMAIL PROTECTED]> wrote:
>Dear Linux Advancers,
>
> I have a Linux box on an NT network and use smbclient. However, I have
>to know the IP of the service-providing computer in advance. That's
>troublesome..
> How to get a complete list of computers Netbios name and IP addresses in
>a NT network using a SAMBA CLIENT?
>
>Thank you
I don't know of a direct method, but here's an indirect one...
1) get the list of systems in the browse list from the DOMAIN's browse master
smbclient -L name_of_domain_browse_master
2) for each system in the list, get it's list of shared resources
smbclient -L name_of_system_in_domain
Lew Pitcher
System Consultant, Integration Solutions Architecture
Toronto Dominion Bank
([EMAIL PROTECTED])
(Opinions expressed are my own, not my employer's.)
------------------------------
From: [EMAIL PROTECTED]
Crossposted-To: comp.windows.x.kde,alt.os.linux.dial-up,comp.os.linux.setup
Subject: Re: kppp: connect before login & keep connection
Date: Tue, 11 May 1999 00:16:46 GMT
> kppp --help
> will tell you how to use it to auto connect to a specific account from
the
> command line.
>
Doesn't work:
> kppp --help
kppp: unknown option "kppp"
kppp -- valid command line options:
-h : describe command line options
-c account_name : connect to account account_name
-k : terminate an existing connection
-q : quit after end of connection
-r rule_file : check syntax of rule_file
--== Sent via Deja.com http://www.deja.com/ ==--
---Share what you know. Learn what you don't.---
------------------------------
From: "TiM" <[EMAIL PROTECTED]>
Subject: Re: @HOME Cable Service and Linux
Date: Tue, 11 May 1999 04:30:05 GMT
I believe it is a commercial server they are cracking down on.. not just a
normal server that is for... "fun".
Joseph D. Carvalho wrote in message ...
>Hello Scott,
>I was a subscriber to the @HOME service for about a year. I was
>living in SanDiego at the time. I'd been given a 'leased' IP and was
>told that the lease was valid for approx 30 days. My system was
>never offline for any length of time, so I don't know if it would've
>expired.
>
>What I do know is they will shut you down if you attempt to run a server
>across their lan/wan. The teeny-tiny print in your contract with them says
>so.
>They never filtered any of my traffic, but when they found I was running a
>pseudo commercial server, BANG! Service suspended and subsequent
>nastygram to cease in the mail.
>
>Good luck, I miss having the bandwidth. Now I live in the mountains of
>Colorado
>and have to make due with a 24.4k dialup, but the quiet and scenery more
>than
>make up for it.
>
>--joe
>DE KR6NA
>
>Scott Robson wrote in message <[EMAIL PROTECTED]>...
>>Hi
>>
>>Im curious if anyone has had any experience using linux with the @HOME
>>cable modem service (www.home.com).
>>
>>I know they do not support it, but is it possible to connect anyway and
>>do they fire wall? static or dynamic ip? Is the general performance of
>>the line good or bad?
>>
>>I'd plan to run a web server and maybe a mail server over it (for
>>completely personal use of course). Anyone have any experience with them?
>>
>>Thanx in Advance
>>
>>Scott
>
>
------------------------------
From: Victor Kwok <[EMAIL PROTECTED]>
Subject: reading Ethernet card address
Date: Tue, 11 May 1999 12:30:36 +0800
Hi,
I want to write a program to read the hardware address of my
Ethernet card. I know that I can read the address using ifconfig. Is
there anywhere I can find the source code of it? Or can anyone point
me to other method?
Thanks!
Victor
------------------------------
From: ruben <[EMAIL PROTECTED]>
Subject: Frog! @home
Date: Tue, 11 May 1999 00:52:56 GMT
Hi!
We regard frogs as "ugly". As a mater of fact they are
very interesting creatures!
By other hand, I have a frog in my house system.
I use @home ISP (cable)
I have two computers with two IP addresses.
I use a Linksys hub (5) and two iqual Linksys LNE cards
Coputer names aare
Like this:
1- cc123456-a
2- cc123456-b
The two computers can "see" each other.
But the cc123456-b can not connect to Internet,
If I use name cc123456-a in the second computer.
(after turning off the first),
I get connection!
If I use -b in the main computer, I CAN'T get on
@home Customer Service told me that my second computer
has a 'bad' setting.
I can't swallow that because I only have to change the
last letter, a or b, to get the problem in each computer.
Any hints?
Thaaaaaaaanks!
ruben
------------------------------
Crossposted-To: comp.os.linux.development.system
Subject: Re: Reliable (!) nic for 2.2 kernel?
From: Johan Kullstam <[EMAIL PROTECTED]>
Date: 10 May 1999 20:54:51 -0400
bryan <[EMAIL PROTECTED]> writes:
> In comp.os.linux.networking Johan Kullstam <[EMAIL PROTECTED]> wrote:
>
> : hmm all i have is this crappy hub. i have no cross-over cable.
>
> it would be a good test if you could locate one. sometimes its a
> 'timing thing' and bugs show up with direct connections that buffering
> or delaying devices (hubs/routers) might hide.
i'll ask the info tech folks at my place of employment for a loaner.
still, since my system works, why break it? ;-)
> : sophia(~)# time ping -s 1000 -f euler
> : PING euler.axel.nom (172.16.0.2): 1000 data bytes
> : ....
>
> if all you got were those dots, over 8 minutes, I'd say that was
> 'solid' ;-)
and i got those dots within the first few seconds of pinging.
> : everything still seems rock solid. i was even able to do stuff over
> : the telnet session i have going from sophia to euler.
>
> sounds like your system is stable. with that hub in the middle, at
> any rate. is that a TRUE hub (repeater) or is it a bridge/switch? if
> the latter, then it could buffer and make life easier on the nics.
it's a `d-link dfe-904 4 port 10/100Mbps dual-speed hubby [sic]'
there's a 10/100 switch which i have set to 100.
the manual claims it's a `multi-port repeater' or `repeating hub'. i
am not sure what that means exactly, but it's a small box with not a
lot of electronics in it. still, it could be delaying signals a fair
amount relative to what triggers your bug.
is 100Mbps supposed to work with a cross-over cable? when i got my
gear at a computer show, i was advised to get a hub for the fast
ethernet.
> --
> Bryan
--
J o h a n K u l l s t a m
[[EMAIL PROTECTED]]
Don't Fear the Penguin!
------------------------------
Date: Tue, 11 May 1999 01:22:53 +0100
From: Matt <[EMAIL PROTECTED]>
Subject: Re: uplink vs. cross-connect
Bill,
Should it be
Orange white + Green white (joined) = 1 + 3
Green + Orange (joined) = 2 to 6
3 green white
4 blue
5 blue white
7 brown white
8 brown
But then again I could be wrong as I am new to this game.
So far I have seen both the IEEE standard and the AT&T standard.
Please correct me if I am wrong this wiring/network thing is leading
into a lot of sleepless nights.. well early moring. Chances are I am
wrong though.
Bill Sica wrote:
>
> Yes!
>
> Coss connect, or cross over usualy refers to a cable between 2 ethernet
> cards, or hubs with the wires reversed, similar to a null modem. Uplink
> means a special port on a hub or switch that has the wires reversed. So
> basically they are the same thing.
>
> (little diagram, for CAT5 type B crosover cable 100BaseT)
>
> 1 (orange white) 2
> 2 (orange) 1
> 3 (Green white) 6
> 4 (Blue) 5
> 5 (Blue white) 4
> 6 (Green) 3
> 7 (Brown white) 8
> 8 (Brown) 7
>
> If I'm wrong with this sorry, I'm doing it off the top of my head, and I
> alwayse seem to revers them the wrong way.
>
> ----------
> In article <6NIZ2.5607$[EMAIL PROTECTED]>,
> [EMAIL PROTECTED] wrote:
>
> >I note in the help screens for the At Home network the term 'cross-connect'
> >usedto refer to a certain type of port on an ethernet hub. Is this
> >equivalent to an 'uplink' port?
> >
> >--
> >Bob Bernstein
> >at
> >Esmond, R.I., USA
> >
------------------------------
From: [EMAIL PROTECTED] (Luca Filipozzi)
Crossposted-To: comp.protocols.tcp-ip
Subject: Re: connecting two networks w/o a router??
Date: Thu, 6 May 1999 09:42:18 -0700
In article <7gs9ej$u76$[EMAIL PROTECTED]>, [EMAIL PROTECTED] says...
> So when should one use ip masq. instead of just ip forwarding?
When you want to hide a private network behind a single ip address.
> I have two lan
> segments (192.168.1 and 192.168.2) that I want to be connected through a ppp
> link. I assume I just use ip forwarding on the two machines that actually
> have the ppp link? This would allow each machine in segment 1 to speak with
> each machine on segment 2, and vice-versa. However, I would need to tell each
> machine to use the ppp machine on it's segment as a gateway, correct? (This
> is the part I am a bit confused about.)
Correct. You only need to ip forward here (route).
LAN 1 network: 192.168.1.0
LAN 1 netmask: 192.168.1.255
LAN 1 gateway: 192.168.1.1
|
linux eth0 192.168.1.1
linux ppp0
|
linux ppp0
linux eth0 192.168.2.1
|
LAN 2 network: 192.168.2.0
LAN 2 netmask: 192.168.2.255
LAN 2 gateway: 192.168.2.1
>
> If I then wanted to have both segments use one ppp link to the Internet, how
> would I go about that?
This is where you need to use masquerade. You want to hide the
192.168.1.0/24 and the 192.168.2.0/24 private networks behind a single
valid ip address (the ppp link).
--
Luca Filipozzi <[EMAIL PROTECTED]>
------------------------------
From: Peter Van Doren <^~[EMAIL PROTECTED]>
Subject: Re: RedHat-6.0 and port forwarding
Date: Mon, 10 May 1999 21:48:52 -0700
Here's my firewall.start script.. I finally got it working too.. Thanks John..
My problem was I was denying forwards from the outside world.. That overrides the
ipmasqadm tool.
This allows everyone out using masq, and only allows pcAnywhere in to client
192.168.0.2.
# Flush old rules
/usr/sbin/ipmasqadm portfw -f
/sbin/ipchains -F
# by default DENY EVERYTHING!
/sbin/ipchains -P forward DENY
# Allow everyone in to get out using IP MASQ.
/sbin/ipchains -A forward -s 192.168.0.1/255.255.255.0 -j MASQ
# Allow pcAnywhere in
/sbin/ipchains -I forward -p tcp -s 1.2.3.4/255.255.255.0 5631
/sbin/ipchains -I forward -p udp -s 1.2.3.4/255.255.255.0 5632
/usr/sbin/ipmasqadm portf -a -P tcp -L 1. 2.3.4 5631 -R 192.168.0.2 5631
/usr/sbin/ipmasqadm portf -a -P udp -L 1.2.3.4 5632 -R 192.168.0.2 5632
WARNING: This works for me, using RH6, kernel 2.2.7-ac2. However this is just a
very basic IP Masq ruleset, and is probably open to hacks and attacks.
Sorry, I don't know how to make it DHCP friendly..
Peter Van Doren
John Morey wrote:
> The command line on RedHat-6.0 should look something like this:
>
> /usr/sbin/ipmasqadm portfw -a -P tcp -L 1.2.3.4 5631 -R 192.168.0.2
> 5631
>
> Thanks for every ones help,
>
> John Morey
>
> John Morey wrote:
------------------------------
From: "D. C. & M. V. Sessions" <[EMAIL PROTECTED]>
Subject: Re: Crossover cable for pc to pc network?
Date: Mon, 10 May 1999 21:51:41 -0700
"Stuart R. Fuller" wrote:
>
> Jeffrey A. Bell ([EMAIL PROTECTED]) wrote:
> :
> : My question is: Do I have to use a hub to wire these machines together
> : or can I just wire the Ethernet cards directly together? I was reading
> : somewhere that if I wire them directly together I have to either make a
> : crossover cable or purchase one. Is this correct?
>
> Considering the low cost of a network hub, and the fact that crossover cables
> tend to be harder to find and/or more expensive, I'd recommended getting the
> hub and standard cables.
>
> After all, if you get a 3rd computer with network card, you're going to throw
> away the crossover cable, and end up buying the hub and standard cables
> anyway. Besides, hubs generally have pretty lights that you can watch while
> networking, and they (the lights) make great troubleshooting tools for when
> things go wrong.
Actually, at 100TX hubs are still pricy enough that you're better off
adding an extra card to one of the boxes and using it to route IP
traffic between the other two. ESPECIALLY if the box in the middle
is a server and the other two are clients, it can make a pretty big
difference in performance.
--
| Microsoft: "A reputation for releasing inferior software will make |
| it more difficult for a software vendor to induce customers to pay |
| for new products or new versions of existing products." |
+---------- D. C. & M. V. Sessions <[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
******************************
