Is there a Konsole command to interrogate a router ?

English Network/Internet
1

What I want to do from the console is send something to a router, to which I am hard wired to ask this:

HEY !!! who are you and what is your IP address ?
I know that Linux is magic and has some wonderful tools. lol!

I guess that I am not sure of its IP address, though I had thought that I knew it.

I know that I can always do a factory reset but would prefer not to have to do that.

thanks

2

If your system knows that it exists, then it probably received a packet from that “router”. And the IP address is in that packet.

It is very unclear what you are wanting to do.


netstat -rn

will tell you about the routing that your system is currently using.

Better to call it a “terminal command” or a CLI command (CLI=command line interface). People who don’t use KDE might not recognize “Konsole”, which is just one of the several terminal emulators available.

3

Ok, CLI, I know and as further explanation, this is what I am after.
I am connected by wire to a router and I want to get into its management page and I don’t know it’s IP address. Usually I use it as the URL in Firefox and it opens the setup page.
But now I get a “host unreachable” when I ping it with what I had thought the IP address is.

The netstat -rn returns:

Destination Gateway Genmask Flags MSS Window irtt Iface
0.0.0.0 192.168.10.1 0.0.0.0 UG 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 l0
169.254.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
192.168.10.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0

Destination Gateway Genmask Flags MSS Window irtt Iface

4

192.168.10.1 is your default route, so if you are able to get to other
networks (like the Internet) through this wired connection then that is
likely the router which you are seeking (unless you have multiples on your
network).

The other magical Linux command is one that will show you which boxes are
on your network by doing a ping sweep. Since we know you’re on
192.168.10.x with a typical class C network, this is the command:

Code:

nmap -sn 192.168.10.1-254

The output should resemble this, telling you all of the systems on your
network which are up and responding to pinging:

Code:

Nmap scan report for 192.168.10.1
Host is up (0.0023s latency).
Nmap scan report for 192.168.10.15
Host is up (0.022s latency).
Nmap scan report for 192.168.10.17
Host is up (0.012s latency).

If the nmap command is not found, then install it:

Code:

sudo zypper in nmap

Good luck.

5

Well, I figured out what I need to know, and it was Wireshark that told me.

What had happened was that my main router an ATT 2Wire 3800HGV, changed the IP address of my 2nd router to 10.0.0.1, unbeknownst to me. I guess it did not like it having an IP address in the range that it managed, though it was reserved.
ATT range = 192.168.1.10 ~ 192,168.1.50 with a static reserved for 192.168.1.11
Netgear static = 192.168.1.11

Wireshark told me that, thank you Joe for alerting me to it.

Now back to the drawing boards for a simple subnet design.
This should not be so darn difficult, for smart guys like y’all.

6

Strange.

My 3800HGV is assigning my Buffalo router an IP of 192.168.1.65 (that’s the WAN side of the Buffalo router). The LAN side of the Buffalo router uses 192.168.254.* for its IP addresses.

You probably have your Netgear router using DMZplus mode. I disabled that in the 3800HGV, by turning off the check for “router behind router”.

7

nrickert, have you posted a thread talking about how you went about cofiguring your 2 routers ?

The ones that I have been reading so far are very confusing and contradict themselves mid stream.

8

If there is, it would be from 2009 at DSLReports Home : Broadband ISP Reviews News Tools and Forums. But I’m not sure whether I ever started a thread on it.

I did originally set the router to be in DMZplus mode, though that was a different router. But a firmware change on the 3800HGV made the DMZplus mode less reliable, so I turned that off.

9

Typically,
What you’re asking for is best accomplished by a good port scanner, not a packet scanner like Wireshark. A good port scanner will interrogate every port which will automatically return results that include a sorts of information about the target.

But, if you want to get a very simple node name, PING should be able to do this. Since I haven’t done this specific test on openSUSE, I decided to do a little investigation. It seems that the following command should work, but when I tested on my 12.3, the command isn’t supported. Maybe a new version from factory might support? I’m just surprised because this is a fairly common need.

ping -N

TSU