>>Why DHCP?
He repairs Macs. If he sets a static IP address and forgets to set it back,
it's a problem for the user.
>>As for the SuSE box, just configure the kernel for NAT
I was trying to figure out how, expecting to see something under network
services, but found nothing. Since I don't have two NICs on my SuSE box, I
doubted I could help him. But.... I just found it.
AJ, here's your answer. And it is easy.
In YAST, under "Security and Users", Firewall. Set the internal interface
to your HP NIC, and the external interface to your Wireless. On the next
page, don't select any services, and click 'next'. You can click 'next' on
page 3, as well. On the last page, you can clear the logs if you want (your
option). Contine and you should have it.
Ken Elliott
=====================
-----Original Message-----
From: slug@nks.net [mailto:slug@nks.net] On Behalf Of Russell Hires
Sent: Sunday, July 25, 2004 8:27 PM
To: slug@nks.net
Subject: Re: [SLUG] networking
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Why DHCP? He could just go around and put all the Macs on static addresses.
As for the SuSE box, just configure the kernel for NAT...connect one end of
the box to the net, the other to the hub that the Macs are connected
to...voila.
Russell
On Sunday 25 July 2004 18:40, Ken Elliott wrote:
> Ok all you Linux Experts....
>
> AJ needs his Linux box to be a DHCP server and router for a bunch of Macs.
> He has a DSL wireless router in the front room connected to his wife's PC.
> His backroom Linux box is connected via wireless and sees the internet
> just fine. He works on Macs and needs to be able to connect them to
> the Internet for software upgrades. He has a hub that is plugged into
> the Linux wired Network card, as are the Macs. The Linux box wireless
> NIC is configured via DHCP on the router(192.168.1.x). The second
> (wired) NIC in the Linux box is fixed at 192.168.2.10.
>
> He needs you highly intelligent fellows to come to his aid and tell
> him how to configure DHCP and routing on this SuSE 9.1 box, so his
> Macs can see the Internet.
>
> I did my part on the phone, by helping him simplify what he has, but
> when he fires up DHCP in YAST, he gets errors, and I've never setup
> DHCP on Linux. <imagine a "whoosh" sound over my head>
>
> Please help him before he places that XP CD in the drive...
>
> Ken Elliott
>
> =====================
> -----Original Message-----
> From: slug@nks.net [mailto:slug@nks.net] On Behalf Of A2L1
> Sent: Saturday, July 24, 2004 6:02 PM
> To: slug@nks.net
> Subject: Re: [SLUG] networking
>
> I am not the best at clarification , let me try to clearly explain.
> Although the dual dhcp thing might be the problem.
> OK here it goes. The linux box has its internet conection by PCI
> wireless card so the internet to the back room is only by wireless. So
> that I dont have to buy multiple wireless cards I figured to make use
> of what I have. I have the linux box up
> 24/7 and it has a built in nic so I figured to use that as a "server"
> to the D-link router(which is also just laying around. The D-Link is
> set as a dhcp server. I have multiple macs and a few other tower units
> (windows and linux). If the D-Link is hooked up I can then just plug
> and unplug as I need the other units to be online.
> Now if there is a problem with the linux box being a dhcp server to
> the router which in turn is a dhcp server then I guess the linux box
> would have to still be a server to the router but using a static?
> Networking is not even close to something I comprehend fully and I get
> just more confused as I read more, mostly the terminolgy is difficult
> to put in context. In plain and simple terminolgy here is what I would
like to do !.
> get the linux box to act as a server to provide internet to the
> router/firewall 2. Have the router/firewall act as a server so that I
> may plug in different units that I am testing or working on.
> 3.I would like to use the existing hardware that I have. i have plenty
> of nic's and a ton of cable, two different router/firewalls/.
> The problem with wireless with the mac is the macs use 40 bit wep and
> wont hook up to the 64 bit wep on the wireless so in order to get
> internet access for the macs I have to either have a cable(rj45)
> connection or have to use mac
> airport(expensive) which I do not want to buy.
> With everything that can be done with linux there has to be a way to
> use the linux box with its wireless internet access to provide
> internet access to the other units in the room, I just dont have a clue on
how.
> For now I will try to have the D-Link issue static IPs and see if I
> can connect, but I would prefer a dhcp because it would be easier when
> I hook up other boxes.
> Thanks for the input, I'm off to try.
> A J
>
> On Saturday 24 July 2004 16:19, Ken Elliott wrote:
> > >>I installed and initiated both dhcp and dns servers
> > >>
> > >>The D-Link shows a Wlan signal and when I connect a caple to it
> > >>and to the
> >
> > mac it also shows a connection.
> >
> > Do you have DHCP turned OFF on the D-Link router? You can't have
> > two DHCP servers on the same network segment.
> > So, if you have the Mac and Linux box both plugged into the router
> > you must either use the router's DHCP server, _OR_ the Linux DHCP
> > server, but never both. Now, if you have two network cards in the
> > Linux box, one going to the router, one going to the Mac, that's
different.
> >
> > Why are you going to the trouble of using a DNS server for just 2
> > computers? It that's all there are, you could simply create a hosts
> > file on each machine, containing the hostname and IP address of the
> > other, and either use fixed IP addresses, or configure your router
> > to assign a known IP address based on the NIC hardware address.
> >
> > I don't think I understand everything you're trying to do, so more
> > information will help.
> >
> > Smarter more Linux-savvy guys will chip in soon.
> >
> >
> > Ken Elliott
> >
> > =====================
> > -----Original Message-----
> > From: slug@nks.net [mailto:slug@nks.net] On Behalf Of A2L1
> > Sent: Saturday, July 24, 2004 3:18 PM
> > To: slug@nks.net
> > Subject: [SLUG] networking
> >
> > Hello,
> > Things were progressing nicely, got the antenna up and signal
> > strenght is up on the wireless and that is all working well.
> > The problem I am having is getting SuSE 9.1 pro to act as a dhcp
> > server. I installed and initiated both dhcp and dns servers and
> > they are up and running according to yast. I connected a cable to
> > the onboard nic ( which is designated as eth0 by the bo and the
> > other end to a D-Link router/firewall. The D-Link shows a Wlan
> > signal and when I connect a caple to it and to the mac it also shows
> > a connection. The mac shows an Ip and subnet but cant connect to the
> > net. i cannot ping the linux box from the mac. I can access the
> > D-Link from the mac and access all the settings(they all seem
right---dhcp).
> > I am assuming that the SuSE box is not sending a dhcp to the D-Link
> > and I dont know what to do next. Has anyone set a SuSe
> > 9.1 pro box as a dhcp server and would it be possible to get a copy
> > of the /etc/sysconfig/dhcpd. I assume that is what needs modifying?
> > Any help is appreciated.
> > Thanks,
> > A J
> >
> >
> >
> >
> >
> >
> > --
> > Feel safe and confident,there were no M$ products used in the
> >creation of this email, only virus-free and rock solid LINUX!
> > Registered LINUX user #191255
> > -----------------------------------------------------------
> >------------ This list is provided as an unmoderated internet
> >service by Networked Knowledge Systems (NKS).
> > Views and opinions expressed in messages posted are those of the
> >author and do not necessarily reflect the official policy or
> >position of NKS or any of its employees.
> >
> > -----------------------------------------------------------
> >------------ This list is provided as an unmoderated internet
> >service by Networked Knowledge Systems (NKS).
> > Views and opinions expressed in messages posted are those of the
> >author and do not necessarily reflect the official policy or
> >position of NKS or any of its employees.
>
> --
> Feel safe and confident,there were no M$ products used in the creation
> of this email, only virus-free and rock solid LINUX!
> Registered LINUX user #191255
> ----------------------------------------------------------------------
> - This list is provided as an unmoderated internet service by
> Networked Knowledge Systems (NKS). Views and opinions expressed in
> messages posted are those of the author and do not necessarily reflect
> the official policy or position of NKS or any of its employees.
>
> ----------------------------------------------------------------------
> - This list is provided as an unmoderated internet service by
> Networked Knowledge Systems (NKS). Views and opinions expressed in
> messages posted are those of the author and do not necessarily reflect
> the official policy or position of NKS or any of its employees.
- --
Linux -- the OS for the Renaissance Man -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBBE/GAqKGrvVshJQRAl5nAJ9tk7eS5DmObYQtSd9rflljsix0KQCfQIgv
/vXIQNa4DMEXpn27Q+B2s0o=
=XExC
-----END PGP SIGNATURE-----
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages posted
are those of the author and do not necessarily reflect the official policy
or position of NKS or any of its employees.
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 13:28:07 EDT