Access router's control panel

Nexer · 12-04-2003, 11:28 AM

I'm using Slackware 9.1 and just bought a Solwise SAR130 ADSL router. I need to set it up through it's control panel but keep getting a can't connect message every time I try to access it (192.168.7.1). I've tried changing my IP address, subnet mask, gateway IP, etc by editing rc.inet1.conf but I still can't connect, so I'm assuming that's not the right way to go about it... If it isn't then what is? Thanks

superbondbond · 12-04-2003, 11:46 AM

the IP setting of your computer will have no affect on access the router. You need to access the IP of the router itself.
For example, my Linksys router (factory default) is 192.168.1.1. Once I access the router control, it can be changed to whatever I want.

Did the router documentation specifically say 192.168.7.1? If so and it is not working, try resetting the router back to factory settings and try again.

Nexer · 12-04-2003, 11:58 AM

On my last router all I had to do was enter the router's IP (192.168.1.2) and it worked, but on this one I have to manually enter the gateway IP, subnet mask and everything before I can even enter the control panel.

The manual specifically said the router's IP is 192.168.7.1 and gave instructions on how to configure everything before entering the router, but of course that was for Winblows...

There's no reset button either.

Nexer · 12-04-2003, 01:35 PM

Update: I changed my internal IP using "ifconfig address eth0 192.168.7.2" then tried to connect to my router at 192.168.7.1, it asked me for a password, I entered the defaults, it accepted and the browser said it was connecting but it never connected.

In effect what I'm asking for is how in slackware, do I configure my

Routers IP address to 192.168.7.1

Subnet mask to 255.255.255.0

My computers IP to 192.168.7.2

and configure the DNS

The only thing I've edited to try to get it to work (apart from the ifconfig thing I just mentioned) is my /etc/rc.d/rc.inet1.conf file, which looks like this:

Code:

# /etc/rc.d/rc.inet1.conf
#
# This file contains the configuration settings for network interfaces.
# If USE_DHCP[interface] is set to "yes", this overrides any other settings.
# If you don't have an interface, leave the settings null ("").

# Config information for eth0:
IPADDR[0]="192.168.7.2"
NETMASK[0]="255.255.255.0"
USE_DHCP[0]="yes"
DHCP_HOSTNAME[0]="My ISP's DNS here*"

# Config information for eth1:
IPADDR[1]=""
NETMASK[1]=""
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""

# Config information for eth2:
IPADDR[2]=""
NETMASK[2]=""
USE_DHCP[2]=""
DHCP_HOSTNAME[2]=""

# Config information for eth3:
IPADDR[3]=""
NETMASK[3]=""
USE_DHCP[3]=""
DHCP_HOSTNAME[3]=""

# Default gateway IP address:
GATEWAY="192.168.7.1"

# Change this to "yes" for debugging output to stdout.  Unfortunately,
# /sbin/hotplug seems to disable stdout so you'll only see debugging output
# when rc.inet1 is called directly.
DEBUG_ETH_UP="yes"

*edited out my ISP's DNS.

Thanks in advance

superbondbond · 12-04-2003, 02:20 PM

I don't think you enter the DNS server IP where it asks for DHCP_HOSTNAME.

This information should be in /etc/resolv.conf kinda like this

Code:

nameserver xxx.xxx.xxx.xxx
nameserver xxx.xxx.xxx.xxx
search domain.whatever

Nexer · 12-04-2003, 04:41 PM

Well I managed to get into the control panel after issuing the ifconfig command, which took around 3 minutes and I changed my resolv.conf file.. still not working though

superbondbond · 12-04-2003, 04:58 PM

I noticed in your earlier post from you rc.inet1.conf you specify an IP of 192.168.7.2 and you also have a "yes" comment for DHCP.

You want to comment out the DHCP line by putting a number sign at the front. Like this:

Code:

 #USE_DHCP[0]="yes"

Now that line will be ignored when the script us run.
Once you change that, re-run that script.

teval · 12-04-2003, 05:24 PM

Try to run the dhcp client, it works with my LinkSys.

dhcpcd

See if that allows you to enter your router now. It's most likely running the dhcp service (so it can serve the correct adresses to your windows computers)
I suggest you exchange it for a LinkSys router if that doesn't work. Lazyness rules, nothing beats setting things up with 1 command.

Nexer · 12-04-2003, 05:37 PM

Uncommenting that line worked. Cheers :D

Teval: I can enter my router, it's just that it takes an eternity to do so. Hmm.. think that's gonna be my next problem ;)