Linux-Networking Digest #267, Volume #11 Mon, 24 May 99 17:13:42 EDT
Contents:
Re: IP Masquerading Connecting but not working (Jonathan Marks)
Re: *BSD or Linux Based Computer Telephony development Products ("Lee Sharp")
Re: Practice firewall ("Doug Pitek")
Re: Small private network woes - Still not working (Ray)
Re: Frog! @home (Ted Potter)
Re: Samba and printing. (Jake Kim)
Re: Multiple nic's ([EMAIL PROTECTED])
Stop netbios port 137, 138, 139 to bring up diald (Wayne Chan)
Re: Newbie - please help (Dennis Wetzig)
----------------------------------------------------------------------------
From: Jonathan Marks <[EMAIL PROTECTED]>
Subject: Re: IP Masquerading Connecting but not working
Date: Mon, 24 May 1999 17:02:35 GMT
Hi,
Firstly, word on the street (or should I say wire) is that the 2.2.8 kernel is
somewhat problematic. - see www.kernel.org. I here 2.2.5 is the least
problematic, 2.2.9 has
just been released, claims to not be problematic, but it has only out there for
a few days.
I guess we are not the only two people who will struggle to get this to work. I
am writing a manual on how to implement a masquerading firewall. I'll share
some of this 'to be published' info with you.
The network options with which to compile the kernel that I used to get ipmasq
to work:
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_NETLINK=y
CONFIG_RTNETLINK=y
CONFIG_NETLINK_DEV=y
CONFIG_FIREWALL=y
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
# CONFIG_IP_MULTIPLE_TABLES is not set
# CONFIG_IP_ROUTE_MULTIPATH is not set
# CONFIG_IP_ROUTE_TOS is not set
CONFIG_IP_ROUTE_VERBOSE=y
# CONFIG_IP_ROUTE_LARGE_TABLES is not set
# CONFIG_IP_PNP is not set
CONFIG_IP_FIREWALL=y
CONFIG_IP_FIREWALL_NETLINK=y
CONFIG_NETLINK_DEV=y
CONFIG_IP_TRANSPARENT_PROXY=y
CONFIG_IP_MASQUERADE=y
CONFIG_IP_MASQUERADE_ICMP=y
CONFIG_IP_MASQUERADE_MOD=y
# CONFIG_IP_MASQUERADE_IPAUTOFW is not set
CONFIG_IP_MASQUERADE_IPPORTFW=y
# CONFIG_IP_MASQUERADE_MFW is not set
CONFIG_IP_ROUTER=y
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
CONFIG_IP_ALIAS=y
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
CONFIG_INET_RARP=y
CONFIG_SKB_LARGE=y
# CONFIG_IPV6 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
Note: I've turned off IPAUTOFW, and turned on IPPORTFW. IPPORTFW is the most
appropriate port forwarding option, all the others are legacy. Remember to
select kernel modules and make the modules too.
Have you seen the IP-masq Howto - the latest V1.71 which is still in draft and
can be found at 'www.ecst.csuchico.edu/~dranch/LINUX/index-linux.html', as well
as his TrinityOS tomb. 'www.ecst.csuchico.edu/~dranch/LINUX/TrinityOS.wri.
Check that the networking is running correctly. ifconfig should display
something
like the following. (eth0 - internet, eth1 private network).
eth0 Link encap:Ethernet HWaddr 00:00:E8:D3:D7:65
inet addr:24.113.94.87 Bcast:24.113.95.255 Mask:255.255.254.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3361523 errors:0 dropped:0 overruns:0 frame:3
TX packets:82074 errors:0 dropped:0 overruns:0 carrier:0
collisions:692 txqueuelen:100
Interrupt:12 Base address:0x240
eth1 Link encap:Ethernet HWaddr 00:00:E8:D3:D9:C0
inet addr:192.168.0.254 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:301646 errors:0 dropped:0 overruns:0 frame:0
TX packets:316820 errors:0 dropped:0 overruns:0 carrier:0
collisions:30 txqueuelen:100
Interrupt:11 Base address:0x300
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:82 errors:0 dropped:0 overruns:0 frame:0
TX packets:82 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
netstat -rn should display something similar to: Note the the last gateway
entry.
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.0.254 0.0.0.0 255.255.255.255 UH 0 8192 0 eth1
24.113.94.87 0.0.0.0 255.255.255.255 UH 0 8192 0 eth0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
24.113.94.0 0.0.0.0 255.255.254.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 8192 0 lo
0.0.0.0 24.113.94.1 0.0.0.0 UG 0 8192 0 eth0
Great, now try pinging an address on the internet (metalab.unc.edu) and a
private ip address from the ipmasq box.
Now from a box on the private network, ping the private interface -
192.168.0.254
in my case, and the internet interface 24.113.94.87, in my case.
Now from a box on the private network, attempt to ping an address on the
internet (metalab.unc.edu). The DNS should work - ie. returns the ip address,
but the ping attempts all timeout.
Having got this far, I followed the ip-masq howto advise of making a call to
rc.firewall from rc.local. My rc.firewall looks like:
/etc/rc.d/rc.firewall
#!/bin/sh
#
#/etc/rc.d/rc.firewall
#
#Created by Jonathan Marks, 5/21/99
# Do not need to do a depmod, as this is done in rc.sysinit
#/sbin/depmod -a
# Lets install the required ip_masq modules
#/sbin/modprobe ip_masq_cuseeme
/sbin/modprobe ip_masq_ftp
/sbin/modprobe ip_masq_irc
#/sbin/modprobe ip_masq_quake
/sbin/modprobe ip_masq_raudio
#/sbin/modprobe ip_masq_user
#/sbin/modprobe ip_masq_vdolive
# Flush old firewall rules - just in case
/sbin/ipchains -F
# Masquerading firewall timeouts: tcp conns 2hrs, tcp after fin pkt 10s, udp
120s
/sbin/ipchains -M -S 7200 10 120
# Set up ipchains for simple masqerading firewall
/sbin/ipchains -P forward DENY
/sbin/ipchains -A forward -s 192.168.0.0/24 -j MASQ
# Port forwarding - first flush out any forwards - just in case
/usr/sbin/ipmasqadm portfw -f
# Add port forwarding for http, smtp and ftp to henry
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 80 -R 192.168.0.3 80
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 25 -R 192.168.0.3 25
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 21 -R 192.168.0.3 21
# ICQ tcp return port setup
# First to Hershel
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2000 -R 192.168.0.6 2000
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2001 -R 192.168.0.6 2001
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2002 -R 192.168.0.6 2002
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2003 -R 192.168.0.6 2003
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2004 -R 192.168.0.6 2004
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2005 -R 192.168.0.6 2005
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2006 -R 192.168.0.6 2006
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2007 -R 192.168.0.6 2007
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2008 -R 192.168.0.6 2008
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2009 -R 192.168.0.6 2009
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2010 -R 192.168.0.6 2010
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2011 -R 192.168.0.6 2011
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2012 -R 192.168.0.6 2012
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2013 -R 192.168.0.6 2013
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2014 -R 192.168.0.6 2014
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2015 -R 192.168.0.6 2015
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2016 -R 192.168.0.6 2016
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2017 -R 192.168.0.6 2017
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2018 -R 192.168.0.6 2018
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2019 -R 192.168.0.6 2019
# Secondly to Hercules
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2020 -R 192.168.0.1 2020
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2021 -R 192.168.0.1 2021
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2022 -R 192.168.0.1 2022
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2023 -R 192.168.0.1 2023
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2024 -R 192.168.0.1 2024
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2025 -R 192.168.0.1 2025
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2026 -R 192.168.0.1 2026
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2027 -R 192.168.0.1 2027
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2028 -R 192.168.0.1 2028
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2029 -R 192.168.0.1 2029
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2030 -R 192.168.0.1 2030
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2031 -R 192.168.0.1 2031
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2032 -R 192.168.0.1 2032
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2033 -R 192.168.0.1 2033
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2034 -R 192.168.0.1 2034
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2035 -R 192.168.0.1 2035
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2036 -R 192.168.0.1 2036
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2037 -R 192.168.0.1 2037
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2038 -R 192.168.0.1 2038
/usr/sbin/ipmasqadm portfw -a -P tcp -L 24.113.94.87 2039 -R 192.168.0.1 2039
Notes on rc.firewall
1. Flush out ipchains and portfw. This is useful if this file is run
manually, after bootup (say during debugging / testing).
2. The syntax of portfw is different to that in the ip_masq howto. Check out
the ipmasqadm man page and run 'ipmasqadm portfw -h'
Now lets confirm that the settings are all ok.
do a 'lsmod', this is what I see:
============================================
Module Size Used by
ip_masq_raudio 2884 0
ip_masq_irc 1336 0 (unused)
ip_masq_ftp 2128 0
nfsd 150212 8 (autoclean)
lockd 30736 1 (autoclean) [nfsd]
sunrpc 50688 1 (autoclean) [nfsd lockd]
msdos 8176 1 (autoclean)
fat 26228 1 (autoclean) [msdos]
============================================
The ip_masq_... modules are installed
do a 'ipchains -L'
============================================
Chain input (policy ACCEPT):
Chain forward (policy DENY):
target prot opt source destination ports
MASQ all ------ 192.168.0.0/24 anywhere n/a
Chain output (policy ACCEPT):
============================================
This will be strengthened later.
lastly do a 'ipmasqadm portfw -l'
============================================
prot localaddr rediraddr lport rport pcnt pref
TCP cr324145-a hercules 2039 2039 10 10
TCP cr324145-a hercules 2038 2038 10 10
TCP cr324145-a hercules 2037 2037 10 10
TCP cr324145-a hercules 2036 2036 10 10
TCP cr324145-a hercules 2035 2035 10 10
TCP cr324145-a hercules 2034 2034 10 10
TCP cr324145-a hercules 2033 2033 10 10
TCP cr324145-a hercules 2032 2032 10 10
TCP cr324145-a hercules 2031 2031 10 10
TCP cr324145-a hercules 2030 2030 10 10
TCP cr324145-a hercules 2029 2029 10 10
TCP cr324145-a hercules 2028 2028 10 10
TCP cr324145-a hercules 2027 2027 10 10
TCP cr324145-a hercules 2026 2026 10 10
TCP cr324145-a hercules 2025 2025 10 10
TCP cr324145-a hercules 2024 2024 10 10
TCP cr324145-a hercules 2023 2023 10 10
TCP cr324145-a hercules 2022 2022 10 10
TCP cr324145-a hercules 2021 2021 10 10
TCP cr324145-a hercules 2020 2020 10 10
TCP cr324145-a hershel 2019 2019 10 10
TCP cr324145-a hershel 2018 2018 10 10
TCP cr324145-a hershel 2017 2017 10 10
TCP cr324145-a hershel 2016 2016 10 10
TCP cr324145-a hershel 2015 2015 10 10
TCP cr324145-a hershel 2014 2014 10 10
TCP cr324145-a hershel 2013 2013 10 10
TCP cr324145-a hershel 2012 2012 10 10
TCP cr324145-a hershel 2011 2011 10 10
TCP cr324145-a hershel 2010 2010 10 10
TCP cr324145-a hershel 2009 2009 10 10
TCP cr324145-a hershel 2008 2008 10 10
TCP cr324145-a hershel 2007 2007 10 10
TCP cr324145-a hershel 2006 2006 10 10
TCP cr324145-a hershel 2005 2005 10 10
TCP cr324145-a hershel 2004 2004 10 10
TCP cr324145-a hershel cfinger cfinger 10 10
TCP cr324145-a hershel 2002 2002 10 10
TCP cr324145-a hershel 2001 2001 10 10
TCP cr324145-a hershel 2000 2000 10 10
TCP cr324145-a henry ftp ftp 10 10
TCP cr324145-a henry smtp smtp 10 10
TCP cr324145-a henry www www 10 10
==============================================
Now from a host (that is configured correctly) on the private network, ping
a external site, say metalab.unc.edu (choose a not so busy site or busy time).
If that works, attempt to ftp an external site from a host on the private
network. - same with http. Refer to the ipmasq Howto to trouble shoot if
there are problems.
Nigel Sim wrote:
> At this stage the information I have is a little vague but there may be
> enough here for someone to offer some suggestions.
> I had a working IP masquerading server running Debian 2.1 (Kernel 2.0.36). I
> upgraded the kernel to 2.2.8 (by hand compiling it etc, as opposed to using
> the package manager, for which 2.2.8 wasn't available). Things still worked.
> I then, in order to install the ICQ masquerading module, installed (using
> dselect) ipautofw (Automatic Packet Forwarding i believe) and on top of that
> I installed Squid with the idea to set up a caching http proxy. It was after
> the next restart that my IP masquerading, although it on the surface
> appeared to work, really didn't.
> From the computers on the local network you can start to connect to a web
> site but it will not get beyond "Site found, waiting for reply". Simularly
> when checking email it can connect, authorise and then say downloading
> message 1 of 10, but it doesn't get beyond that (ie, no progress into the
> download). ICQ also works a little. It connects, you can see who is on, but
> when you try to get someones info it complains you are not on the internet.
> The rules in IPChains havn't changed since it was working.
> Any Suggestions?
>
> Thanks
> Nigel
------------------------------
From: "Lee Sharp" <[EMAIL PROTECTED]>
Subject: Re: *BSD or Linux Based Computer Telephony development Products
Date: Mon, 24 May 1999 20:01:58 GMT
Hans Lambermont <[EMAIL PROTECTED]> wrote in article
<[EMAIL PROTECTED]>...
> In article
<[EMAIL PROTECTED]>,
> Gong Wei <[EMAIL PROTECTED]> writes:
> > Is there any commercial products for computer telephony development on
> > *BSD and/or Linux exists today?
> http://www.quicknet.net have cards+(linux) drivers, and they are working
> with the http://www.openh323.org group afaik.
Also check http://www.linuxtelephony.org/ for some other pointers. A
nice portal...
Lee
--
SCSI is *NOT* magic. There are *fundamental technical reasons* why it is
necessary to sacrifice a young goat to your SCSI chain now and then. *
Black holes are where God divided by zero. - I am speaking as an
individual, not as a representative of any company, organization or other
entity. I am solely responsible for my words.
------------------------------
From: "Doug Pitek" <[EMAIL PROTECTED]>
Subject: Re: Practice firewall
Date: Mon, 24 May 1999 15:33:39 -0400
a modem?!?
Mark Swope <[EMAIL PROTECTED]> wrote in message
news:YAh23.1824$[EMAIL PROTECTED]...
> My company is considering setting up an old box
> as a Linux Firewall. However, my boss requested
> that we set it up to "test" it before we go on line.
>
> Can anyone think of a good way to set up a firewall,
> w/o a "live" connection to the Internet so that we
> can test operations and administration?
>
> Currently we don't have a dedicated connection
> to the internet, just a dynamic ISDN connection
> to our ISP...
>
> Thanks for suggestions,
> Mark Swope
>
>
------------------------------
From: [EMAIL PROTECTED] (Ray)
Subject: Re: Small private network woes - Still not working
Date: Mon, 24 May 1999 17:36:45 GMT
Your routing looks fine to me. Are you sure you don't have a cabling
problem? Can you see the transmit lights on the hub blink when you ping (by
ip address)? Could you try connecting the two cards directly using a
cross-over cable?
--
Ray
On Sun, 23 May 1999 11:12:32 -0500, James R. Barnett, Jr. <[EMAIL PROTECTED]> wrote:
>Hi,
> I appreciate all the help I have gotten but I still can't seem to find
>the problem. I am desparate and frustrated. If anyone could lookover the output
>of these commands and could post some suggestions, I would be very grateful.
>
>here is the output of route -n by arson (192.168.1.1):
>
>Kernel IP routing table
>Destination Gateway Genmask Flags Metric Ref Use Iface
>208.128.7.17 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 3 eth0
>127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
>0.0.0.0 208.128.7.17 0.0.0.0 UG 0 0 8 ppp0
>
>here is 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:47 errors:0 dropped:0 overruns:0 frame:0
> TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
>
>eth0 Link encap:Ethernet HWaddr 00:10:5A:0B:50:2F
> 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:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:56 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
> Interrupt:10 Base address:0x300
>
>ppp0 Link encap:Point-to-Point Protocol
> inet addr:208.128.7.90 P-t-P:208.128.7.17 Mask:255.255.255.0
> UP POINTOPOINT RUNNING MTU:1500 Metric:1
> RX packets:342 errors:1 dropped:1 overruns:0 frame:0
> TX packets:318 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
> Memory:12ec038-12ecc04
>
>here is the output of route -n by tireiron (192.168.1.2):
>
>Kernel IP routing table
>Destination Gateway Genmask Flags Metric Ref Use Iface
>192.168.1.1 0.0.0.0 255.255.255.255 UH 0 0 144 eth0
>192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 5 eth0
>127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 15 lo
>0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 26 eth0
>
>Here is the ifconfig for tireiron:
>
>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:104337 errors:0 dropped:0 overruns:0 frame:0
> TX packets:104337 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
>
>eth0 Link encap:Ethernet HWaddr 00:10:5A:0C:9E:1C
> inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:258 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0
> Interrupt:10 Base address:0x300
>
>Please, please, PLEASE help if you can. I have been working on this
>considerably every day for a week and feel like I am getting nowhere.
>
>Thanks in advance,
>
>James
------------------------------
From: [EMAIL PROTECTED] (Ted Potter)
Subject: Re: Frog! @home
Date: Mon, 24 May 1999 12:41:06 GMT
Reply-To: [EMAIL PROTECTED]
Perhaps the bad setting they refer to is the ip address they
gave you. I would check to be sure it is valid.
On Tue, 11 May 1999 00:52:56 GMT, ruben <[EMAIL PROTECTED]> wrote:
>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
------------------------------
From: Jake Kim <[EMAIL PROTECTED]>
Crossposted-To: comp.os.linux.setup,comp.os.linux.admin,comp.os.linux.misc
Subject: Re: Samba and printing.
Date: 24 May 1999 20:31:23 GMT
In comp.os.linux.networking Nitin Mule <[EMAIL PROTECTED]> wrote:
: If you want to load all the printers, add this to your [global] section.
: Specify appropriate values for your system.
: printing = bsd
: load printers = yes
: printcap name = /etc/printcap
Finally mine works. Key was "printing = bsd". Thanks.
Jake
[EMAIL PROTECTED]
------------------------------
From: [EMAIL PROTECTED]
Subject: Re: Multiple nic's
Date: Mon, 24 May 1999 20:39:01 GMT
Haven't done it, can't help directly, but maybe the "Mini-HowTo on
using multiple Ethernet adapters with Linux" will apply. It's at:
http://cesdis.gsfc.nasa.gov/linux/misc/multicard.html
"Tommy �s�n" <[EMAIL PROTECTED]> wrote:
>I have a machine with one RTL8029 based Nic and three RTL8019 Nic's.
>If i try to set up the RTL8019 based cards in netconf using different
>adresses it seems to work.
>But the next time i run netconf all the cards have the same io/irq
>adfresses!!
>
>Has anyone seen this before and is willing to help.
>
>/Tommy
>
>
------------------------------
From: Wayne Chan <[EMAIL PROTECTED]>
Subject: Stop netbios port 137, 138, 139 to bring up diald
Date: Tue, 25 May 1999 00:49:08 +0800
Hi all,
When I do a network neighborhood browsing in my Windows machine and try
to go into some shared folders on another Windows machines. My linux box
with diald will start dialling out to my ISP. How can I deny those
netbios packet from port 137, 138 & 139 in the diald.defs?
Regards,
Wayne
------------------------------
From: Dennis Wetzig <[EMAIL PROTECTED]>
Subject: Re: Newbie - please help
Date: 24 May 1999 19:51:30 GMT
Hi,
> I am using SuSE Linux 6.0 on both mashines. The network cards are recognized
> by the kernel (I think so). I am using the tulip driver with the "options=0"
> parameter. My problem is that I cant even ping the other mashine. I already
> read the net-howto but that didn't solve my problem either. Please help!!!!
did you use ifconfig? That the kernel recognizes the card does not
yet mean that it can actually use it.
You need to run ifconfig to assign an address to that card, set a
subnet mask, set a broadcast address, an MTU, etc.
Also you need to set a routing table entry to tell the system that it
can access that particular network through that netdevice.
You can run route and ifconfig without parameters to check the current
settings.
There is the "Linux Networking Guide" (or something like that) out
there from the LDP...I think it might help you.
If you already did ifconfig and route, well then it's hard to say what
went wrong ;)
Hope that helps,
Dennis
------------------------------
** 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
******************************
