Re: Voange WRT54GP2 router to Fedora Core 5 - eth0 won't get IP address and won't start
- From: Ohmster <notareal@emailaddress.>
- Date: Fri, 29 Dec 2006 23:31:11 -0600
Alan Adams <alan.adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
news:08174f9c4e.Alan.Adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx:
In message <Xns98A6E1E4FEE5AMyBigKitty@xxxxxxxxxxxxxx>
Ohmster <notareal@emailaddress.> wrote:
<snip>
What I want to do now is have all 3 of my computers plugged into the
Linksys and allow them to setup themselves with automatic settings
for the Windows machines and configure my Fedora box to connect with
DHCP to get an IP address and DNS server addresses. Then I can setup
the router to forward the server ports or if I can find it, put the
Linux box in the DMZ, although I cannot really find that setup in the
browser admin screen.
Page 41 of the user guide - Applications and Gaming - DMZ
seems to have what you need.
Oh wow, you are right! I did put my machine in the DMZ but to tell you the
truth, I really don't see much of a difference now with it. I use port
forwarding in the linux firewall to make stuff work on the doze machines
and open the ports on the linux firewall (Firestarter) for what I need,
e.g.: httpd, vsftpd, pop3, etc.
What is the DMZ supposed to do, Alan?
Anyway, the issue is that the Fedora box will not connect to this
routher. When I boot, eth0 failed to get an IP address and thus in
disabled. The computer is not online anymore since connecting the
Linksys router in between the cable modem and the Fedora Box. It just
does not work. I can even try "service network restart" and
"Determining IP information for eth0" times out and fails. The
Windows XP machines have no problem at all with connecting to the
Linksys, they boot fine and work great on the Internet.
One thing that I have noticed is that I have always used
192.168.0.xxx for my home LAN NAT addresses. The Linux box used
192.168.0.1 as it's local address and the other machines on the LAN
fall into that range. The Linksys router on the other hand, dishes
out IP addresses in the 192.168.15.xxx range, starting at
192.168.15.100 and is set to go to 192.168.15.50.
I suspect a typo here - 100 to 250 maybe?
Yep, typo. That should read:
The Linksys router on the other hand, dishes out IP addresses in the
192.168.15.xxx range, starting at 192.168.15.100 and is set to go to
192.168.15.150. The default amount of DHCP addresses is 50, but you can put
in any number you like.
What is the problem here and what do I have to do in order to get my
Fedora Core 5 server to get an IP address from the linksys? This
really bites, I desperatly need to get this Linux box back online and
am stumped, why won't it get an IP address from the router?
I don't know Fedora. Do you have any of the IP setup fields defined,
e.g. do you still have a netmask or a gateway defined? That might
interfere with DHCP.
Alan, this setup has worked perfectly up to the day when all hell broke
loose, for no apparent reason, and then nothing would connect or work. No
internet, no home LAN, and anything else you can think of. The settings did
not just "go bad". Something else must've happened. I started out by going
basic and just trying to get the Linux box to pull and IP and DNS from the
Linksys. The Windows machines had no problem with it, what is Linux looking
for that it does not see?
I decided to use Webmin to disable the eth0 and eth1 interfaces. No sense
in having them both up and confusing things when all I am trying to do now
is to get the darned thing to work. I ended up shuting off eth0 and did not
notice any difference. I could still connect to the Linksys config page
with Firefox. I then disaled eth2 and that was all it took to render Webmin
useless. I could no longer connect to the router. I turned eth0 back on,
that is the one that goes to the Linksys and nothing happened. I still
could not access my adminstration.
Hmmm, something aweful scwewy awound here. I shutoff eth0 and enabled eth1.
Now I could connect to the linksys. <applause>
This means that the network interfaces must have swapped out in the linux
box. Easy enough to test, just switch the eth0 and eth1 cables. It worked,
it was just the network got confused. After switching the Ethernet cables,
we were back in business.
However if you want to use the DMZ facility the manual says you need[snip]
to use a static address, so I would do that. Just make sure it is
outside the DHCP range.
With DMZ your server has an address which is in your LAN range, and
the router forwards requests to it. Those requests come in on the
router's IP address. The issue here is that you need a static address
on the WAN side of the router - or use dyndns.org. The remote clients
need a way to find your router.
Forgive me Alan, I have been working very hard and have fallen asleep at
the keyboard 3 times already. I wakup and see like hundreds of whatever
character I had my finger on all over the screen.
I will come back when I am not so tired. Thanks for your insight.
Happy New Year!
--
~Ohmster
theohmster at comcast dot net
Put "messageforohmster" in message body
to pass my spam filter.
.
- References:
- Prev by Date: Re: Voange WRT54GP2 router to Fedora Core 5 - eth0 won't get IP address and won't start
- Next by Date: One computer only on home net having DNS lookup trouble
- Previous by thread: Re: Voange WRT54GP2 router to Fedora Core 5 - eth0 won't get IP address and won't start
- Next by thread: USB to ethernet
- Index(es):
Relevant Pages
|
