Discussion:
Wireless Router ?
(too old to reply)
Terry A. Haimann
2004-12-04 17:31:04 UTC
Permalink
I have recently bought a AT&T 6800G Wireless/Wired Router. The wired aspects do work,
I have replaced my conventional wired router with the wireless router.
All of my wired pc work well.

But to configure the wireless part of the router, AT&T documentation says
to point a web browser to either:

http://ATT.Router or
http://192.168.0.1

I have tried this and the browser connection times out. I have also tried pinging these
addresses and get a message saying the address is unreachable.

My Linux network consists of

192.168.1.250 yngstr.oldboy.com, This is a Redhat 8 box, this pc is the gateway to the internet
(uses an iptable firewall) and is also running a version of samba.

192.168.1.10 My workstation, Fedora 1, running Samba, MySQL and Apache.

There are also several Win-nn workstations on the network, 1 98se, 1
me (Via Win4Lin) & 1 xp.

In an attempt to connect to the router, I have tried temporarily dropping the firewall.
I have also tried adding the following to my /etc/hosts file:

192.168.0.1 router

I have tried contacting AT&T, their help desk was totally uninformed about
linux, but they have opened up a service ticket and promised to contact me
by e-mail.

Any recommendations?
Randy McLaughlin
2004-12-04 18:13:11 UTC
Permalink
Post by Terry A. Haimann
I have recently bought a AT&T 6800G Wireless/Wired Router. The wired aspects do work,
I have replaced my conventional wired router with the wireless router.
All of my wired pc work well.
But to configure the wireless part of the router, AT&T documentation says
http://ATT.Router or
http://192.168.0.1
I have tried this and the browser connection times out. I have also tried pinging these
addresses and get a message saying the address is unreachable.
My Linux network consists of
192.168.1.250 yngstr.oldboy.com, This is a Redhat 8 box, this pc is the
gateway to the internet
Post by Terry A. Haimann
(uses an iptable firewall) and is also running a version of samba.
192.168.1.10 My workstation, Fedora 1, running Samba, MySQL and Apache.
There are also several Win-nn workstations on the network, 1 98se, 1
me (Via Win4Lin) & 1 xp.
In an attempt to connect to the router, I have tried temporarily dropping the firewall.
192.168.0.1 router
I have tried contacting AT&T, their help desk was totally uninformed about
linux, but they have opened up a service ticket and promised to contact me
by e-mail.
Any recommendations?
Your router is on a different network. I would use one PC and put it on the
same network as the router (192.168.0.xxx preferably by enabling DHCP) and
then log into the router and reconfigure it for your network
(192.168.1.xxx). You might try reading the networking howto's to understand
netmask etc.


Randy
Terry A. Haimann
2004-12-05 04:10:42 UTC
Permalink
Post by Randy McLaughlin
Your router is on a different network.
Please explain how my router is on a different network.
Lenard
2004-12-05 04:50:54 UTC
Permalink
Post by Terry A. Haimann
Post by Randy McLaughlin
Your router is on a different network.
Please explain how my router is on a different network.
Not on a different network, but not on the same IP address range; Hint:
netmask 255.255.255.0

From your original posting;

But to configure the wireless part of the router, AT&T documentation says
to point a web browser to either:

http://ATT.Router or http://192.168.0.1

And;

My Linux network consists of

192.168.1.250 yngstr.oldboy.com, This is a Redhat 8 box, this pc is the
gateway to the internet (uses an iptable firewall) and is also running a
version of samba.

Simply change the IP (temporary) of your Redhat 8 box to 192.168.0.250,
change the router internal IP address to 192.168.1.XXX while configuring
and save. Change your Redhat Linux box back when done.
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." -- B. Franklin, 1759
Randy McLaughlin
2004-12-05 08:25:58 UTC
Permalink
Post by Lenard
Post by Terry A. Haimann
Post by Randy McLaughlin
Your router is on a different network.
Please explain how my router is on a different network.
netmask 255.255.255.0
From your original posting;
But to configure the wireless part of the router, AT&T documentation says
http://ATT.Router or http://192.168.0.1
And;
My Linux network consists of
192.168.1.250 yngstr.oldboy.com, This is a Redhat 8 box, this pc is the
gateway to the internet (uses an iptable firewall) and is also running a
version of samba.
Simply change the IP (temporary) of your Redhat 8 box to 192.168.0.250,
change the router internal IP address to 192.168.1.XXX while configuring
and save. Change your Redhat Linux box back when done.
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." -- B. Franklin, 1759
Actually it is a different network: The default netmask of 255.255.255.0
defines the network of the router in the range of 192.168.0.0~192.168.0.255
while the network of the computers as 192.168.1.0~192.168.1.255.

They are different networks, please do what I recomended and read the
network howto in the LDP.


Randy
Lenard
2004-12-05 17:53:10 UTC
Permalink
Post by Randy McLaughlin
Actually it is a different network: The default netmask of
255.255.255.0 defines the network of the router in the range of
192.168.0.0~192.168.0.255 while the network of the computers as
192.168.1.0~192.168.1.255.
They are different networks, please do what I recomended and read the
network howto in the LDP.
No, the devices in question are on the same physical network, they cannot
(or could not) communicate with each other because they are (or were) on
different TCP/IP (a combination of two communication protocols) segments
of the same network. Here's some definitions;

www.library.yale.edu/~llicense/definiti.shtml

And I have read;

http://www.tldp.org/HOWTO/Networking-Overview-HOWTO.html Section 3
provides additional information about TCP/IP and other protocols.

http://www.tldp.org/HOWTO/NET3-4-HOWTO.html

Along with numerous other HOWTO's and guides at http://www.tldp.org and
other places on the Internet. Which one are you suggesting I read?
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." -- B. Franklin, 1759
Minderbinder
2004-12-05 19:37:01 UTC
Permalink
Post by Lenard
Post by Randy McLaughlin
Actually it is a different network: The default netmask of
255.255.255.0 defines the network of the router in the range of
192.168.0.0~192.168.0.255 while the network of the computers as
192.168.1.0~192.168.1.255.
They are different networks, please do what I recomended and read the
network howto in the LDP.
No, the devices in question are on the same physical network, they
cannot (or could not) communicate with each other because they are (or
were) on different TCP/IP (a combination of two communication protocols)
segments of the same network. Here's some definitions;
My take on the terminology for IP networks:

I would have defined 192.168.0 and 192.168.1 as different subnets on the
same network in this case - drawing the network boundary where the
physical link to the ISP's network begins. Of course it's a subjective
measure...

At any rate, it's pretty normal to define a network as the physical
infrastructure belonging to a particular entity, and any logical
partitions thereof as subnets. Joining two or more networks forms an
internet, and anything joined to the public internet is part of the
(capital "I") Internet.

This can be blurry, of course - if you have a privately owned link between
two companies' networks, is this an internet, or is it a WAN with two
subnets? It would probably depend on how the different segments were
managed... What was I talking about again? Time to get some sleep.

Minderbinder.
Terry A. Haimann
2004-12-06 01:01:28 UTC
Permalink
You have all lost me, I am not a network guru.

What I understand right now is that I will need to start up a dhcp server.
Once I do that, is there going to be some commands that I will need to
issue?

And Will I or won't I need to redefine one of my pc's to 192.168.0.nnn?

Terry
Post by Terry A. Haimann
I have recently bought a AT&T 6800G Wireless/Wired Router. The wired aspects do work,
I have replaced my conventional wired router with the wireless router.
All of my wired pc work well.
But to configure the wireless part of the router, AT&T documentation says
http://ATT.Router or
http://192.168.0.1
I have tried this and the browser connection times out. I have also tried pinging these
addresses and get a message saying the address is unreachable.
My Linux network consists of
192.168.1.250 yngstr.oldboy.com, This is a Redhat 8 box, this pc is the gateway to the internet
(uses an iptable firewall) and is also running a version of samba.
192.168.1.10 My workstation, Fedora 1, running Samba, MySQL and Apache.
There are also several Win-nn workstations on the network, 1 98se, 1
me (Via Win4Lin) & 1 xp.
In an attempt to connect to the router, I have tried temporarily dropping the firewall.
192.168.0.1 router
I have tried contacting AT&T, their help desk was totally uninformed about
linux, but they have opened up a service ticket and promised to contact me
by e-mail.
Any recommendations?
Randy McLaughlin
2004-12-06 01:37:11 UTC
Permalink
Post by Terry A. Haimann
You have all lost me, I am not a network guru.
What I understand right now is that I will need to start up a dhcp server.
Once I do that, is there going to be some commands that I will need to
issue?
And Will I or won't I need to redefine one of my pc's to 192.168.0.nnn?
Terry
<snip>

No, the router comes with DHCP turned on. It is a DHCP server.

All you need to do is to change one of your PC's IP address to match the
router: use dynamic IP addressing (use the routers DHCP server).

After you change your PC's IP address you will be able to login to the
router and set it up (change the internal IP address to 192.168.1.1), maybe
turn off DHCP.

When your done tell the router to restart and restore the PC's IP address.

Is there a good reason you have static IP addresses? If you don't need
static IP addresses just change all the systems to dynamic IP addressing
without doing anything to the router.

One other question I always ask: If you have a linux system why buy a
router? Any Linux system is happy to act as a router if add a seconf NIC,
turn on bind and it will run faster than a router.


Randy
Terry A. Haimann
2004-12-06 03:26:17 UTC
Permalink
I'm feeling really stupid, but I don't know how to change my linux boxes
ip address. Exactly what am I supposed to do?
Post by Randy McLaughlin
Post by Terry A. Haimann
You have all lost me, I am not a network guru.
What I understand right now is that I will need to start up a dhcp server.
Once I do that, is there going to be some commands that I will need to
issue?
And Will I or won't I need to redefine one of my pc's to 192.168.0.nnn?
Terry
<snip>
No, the router comes with DHCP turned on. It is a DHCP server.
All you need to do is to change one of your PC's IP address to match the
router: use dynamic IP addressing (use the routers DHCP server).
After you change your PC's IP address you will be able to login to the
router and set it up (change the internal IP address to 192.168.1.1), maybe
turn off DHCP.
When your done tell the router to restart and restore the PC's IP address.
Is there a good reason you have static IP addresses? If you don't need
static IP addresses just change all the systems to dynamic IP addressing
without doing anything to the router.
One other question I always ask: If you have a linux system why buy a
router? Any Linux system is happy to act as a router if add a seconf NIC,
turn on bind and it will run faster than a router.
Randy
Randy McLaughlin
2004-12-06 05:24:23 UTC
Permalink
Post by Terry A. Haimann
I'm feeling really stupid, but I don't know how to change my linux boxes
ip address. Exactly what am I supposed to do?
<snip>

There is nothing wrong to say it is over your head, especially with changing
network settings.

The problem is that if anyone tells you what to do and there is a problem it
really screws up the system. There are two solutions:

Get someone locally that is able to do it.

Or download Knoppix. Knoppix is a Linux that runs from a CD. It will boot
and configure itself to your system without ever changing your system. From
Knoppix you can login to the router and change its IP address to be
compatible with your network.

You can download Knoppix from http://www.linuxiso.org/ and just burn it to a
CD.

Just boot on the CD and it will configure itself to your router.

There are other answers but these two are probably the easiest.

Randy
Terry A. Haimann
2004-12-06 23:58:34 UTC
Permalink
A 700 meg d/l on a dialup modem is just to large. I went to the Win98
box, changed its ip address to 192.168.0.5 and then was able to log into
the router. Interestingly ie wouldn't connect to the router, but Netscape
7.2 would. But to get everything to work, I had to use Firefox.

Now when I bring the wireless connection up, the network and the xp box
are sending packets back and forth, but they arn't talking. Do I need a
dhcp server up and running or is there another issue going on?

Terry
Post by Randy McLaughlin
Post by Terry A. Haimann
I'm feeling really stupid, but I don't know how to change my linux boxes
ip address. Exactly what am I supposed to do?
<snip>
There is nothing wrong to say it is over your head, especially with changing
network settings.
The problem is that if anyone tells you what to do and there is a problem it
Get someone locally that is able to do it.
Or download Knoppix. Knoppix is a Linux that runs from a CD. It will boot
and configure itself to your system without ever changing your system. From
Knoppix you can login to the router and change its IP address to be
compatible with your network.
You can download Knoppix from http://www.linuxiso.org/ and just burn it to a
CD.
Just boot on the CD and it will configure itself to your router.
There are other answers but these two are probably the easiest.
Randy
Randy McLaughlin
2004-12-07 00:39:26 UTC
Permalink
Post by Terry A. Haimann
A 700 meg d/l on a dialup modem is just to large. I went to the Win98
box, changed its ip address to 192.168.0.5 and then was able to log into
the router. Interestingly ie wouldn't connect to the router, but Netscape
7.2 would. But to get everything to work, I had to use Firefox.
Now when I bring the wireless connection up, the network and the xp box
are sending packets back and forth, but they arn't talking. Do I need a
dhcp server up and running or is there another issue going on?
Terry
<snip>

I almost always use DHCP, but it sounds like someone already configured your
system with static IP addresses.

On your Win98 system save yourself some problems:

Go into internet options (from control panel or IE Tools) and delete all
temporary files (click on delete cookies, then delete files).

Add the following lines to your C:\AUTOEXEC.BAT file (or create new bat
file):

deltree /y c:\windows\temp
md c:\windows\temp


Windows accumulates a huge amount of junk in the temporary directories which
interfere with windows working. You will immediately notice your machine
running better and faster.

If you can you need to check the IP addresses of your systems and write them
down, then tell all of your systems to obtain their IP address dynamically.
If anything goes wrong you can put the IP addresses back.

People used to always specify the IP addresses (static) but today I consider
it bad practice, DHCP is too easy.

I keep repeating this so pay attention:

Most routers come with their DHCP server turned on, you should already have
a DHCP server running (the router). Use it when possible!



From GNOME you can go to the network settings in the system settings folder
and edit the settings (obtain IP address from DHCP).

This will cause problems if you telnet into your system or do something else
that needs an IP address.

There are few absolute answers to your questions. They may seem simple to
you but it depends on what you are doing with your network or what you plan
to do with it. You don't have the technical skills to administer most
networks and you will not learn everything you need to know quickly and
easily, in learning it is a matter of trial and error (everyone has lots of
errors).

If this is for your home use you can play around and figure it out. If it
is for a business hire someone quickly.


Randy

Loading...