Text 594, 108 rader
Skriven 2006-07-23 19:59:44 av Joe Hunt (1:379/45)
    Kommentar till text 583 av Randall Parker (1:379/45)
Ärende: Re: My Linux experience so far
======================================
From: Joe Hunt <jhunt@dslextreme.com>

On Sun, 23 Jul 2006 16:17:08 -0700, Randall Parker
<future_take-out-this-stuff_pundit@_same-name-as-on-left-side_dot-here_com>
wrote:

>Joe,
>
>At the moment the Linux box has a single ethernet card connected to a
>firewall (Netgear ProSafe 802.11g Wireless VPN Firewall model FVG318 -
>which I also just installed). My laptop is also connected to that firewall.
>
>Am I correct in assuming the firewall box lets all devices connected to
>it to pass traffic between each other? That the firewall only blocks
>traffic coming from the outside?
>

Yes, this is correct.

>Also, my Linux box gets an IP address from the firewall I think. I do
>not think I assigned one. But I see this at that web page you provided a
>link to:
>
>First, you must allow the Linux server full rights and access to the
>Windows workgroup and local domain.   That means that either in your
>Active Server environment you need to reserve an IP address for the
>Linux server, or you simply need to ensure a hard coded IP address is
>given to the Linux server.   The server must have a reserved IP address
>whether you deliver it via DHCP or statically assign it in the DNS.
>This also means that you need to ALLOW SMB DAEMON to operate. You can
>ensure your system security does this by editing your Firewall setup or
>using system-config-securitylevel .
>
>
>So can I assign an additional IP address to it for use only when doing
>Windows networking protocols?
>

You need only have a single ip address configured on the ethernet card on your
linux box.  If it is static, I believe that it is simpler to configure samba. 
The NETBIOS name <-> ip address association won't change.

You can leave your linux box configured to accept an ip address via DHCP, but
use your Netgear firewall to reserve an ip address for it, so that it never
changes.  By default, your Netgear uses 192.168.0/24 and so you should tell it
to reserve an ip address in this range (say, 192.168.0.10 for discussion
purposes).

With your browser, log into your firewall (http://www.routerlogin.net), from
main menu, advanced, LAN IP setup, click add at the bottom of the screen, enter
the ip address in the appropriate box, enter your linux ethernet card's MAC
address in the appropriate box, click apply.

(from a command prompt, /sbin/ifconfig eth0 will show your MAC address,
assuming ifconfig is located the same place as in Slackware, and assuming that
your ethernet card in the linux box is eth0)


>My constraint: The laptop has only one ethernet port. I want it to get
>to the internet on that port but also to do local file access to the
>Linux server on that port. Can I do this?
>

Yes, the firewall/switch recognizes packets destined for your lan as opposed to
those destined for the internet.

>Joe Hunt wrote:
>> On Sun, 23 Jul 2006 09:28:40 -0700, Randall Parker
>> <future_take-out-this-stuff_pundit@_same-name-as-on-left-side_dot-here_com>
>> wrote:
>>
>> <snip>
>>
>>> 7) I want to configure Samba and make it run on start-up. I think I have
>>> it on the machine. Do not know what next step to take. Go where to put
>>> it in a start-up script? Or is there a services/daemon manager?
>>
>> I don't use Fedora, but the following link might help.
>>
>> http://www.reallylinux.com/docs/sambaserver.shtml
>>
>> In particular, step 3 describes, using the gui, what you need to do to
>> have it start on system startup .  And, it says that to manually start
>> samba, you need to give this command
>>
>> /etc/rc.d/init.d/smb restart
>>
>> I use Slackware, and it's startup process is different from Redhat
>> derived distributions.  It has a directory /etc/rc.d and any script in
>> that directory which is executable will be run on startup.  So, for
>> example, in Slackware, samba is not started automatically, but there
>> is a startup script in that directory which is not executable.  Giving
>> the command
>>
>> chmod +x rc.samba
>>
>> will cause samba to start automatically upon system startup.  Perhaps
>> Fedora and other Red Hat distributions use a similar concept.
>>
>> Samba is configured entirely with a text file named smb.conf which in
>> Slackware is located in /etc/samba
>>
>> The above article describes configuring samba using gui tools in
>> Fedora.
>>

--- BBBS/NT v4.01 Flag-5
 * Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)