R8500 Iptables access from Raspberry Pi using Python or shell script

[Prasadx]

Hi
I wanted to know how we could access the iptables from netgear router 8500 from a connected Raspberry Pi . In our case the router is not connected to the Internet and we want to access via Python or shell script not via the browser ( which we are able to access from connected windows/MacBook clients).

I have looked at the telnetenable route at https://wiki.openwrt.org/toh/netgear/telnet.console is that still the only supported way for R8500 also?

Thanks for your help.

[antinode · Accepted solution]

> [...] am able to telnet but dont see iptables.

   You know about as much as I do about the soft/firmware on these
things, and (I'd hope) more about "iptables".  Around here (D7000), a
command like "iptables -L" dumps a bunch of stuff.  I see no local "man"
information, but:

# type iptables
iptables is a tracked alias for /sbin/iptables

# iptables --version
iptables v1.4.16.3

so I'd guess that there's some hope of learning more about the
"iptables" program being used.

   As an example of how much I don't know, that "iptables -L" command
here shows stuff like the internal SSH and Telnet ports for 10.0.0.9:

[...]
Chain PORT_FORWARD (1 references)
[...]
ACCEPT     tcp  --  anywhere             10.0.0.9             tcp dpts:22:23
[...]

but I don't see anything about the external ports which get forwarded to
these internal ports.  If you learn anything in your travels which
covers the front end of port forwarding, I'd be interested.

[antinode]

   I doubt that any way is actually supported, but, if your R8500 is
anything like my D7000 and R7000, then it should work.  It's easy enough
to try.  Possibly of interest: http://antinode.info/nte

[Prasadx]

HI

Thanks for the link - am able to telnet but dont see iptables.

Any suggestions?

Thanks,

[antinode · Accepted solution]

> [...] am able to telnet but dont see iptables.

   You know about as much as I do about the soft/firmware on these
things, and (I'd hope) more about "iptables".  Around here (D7000), a
command like "iptables -L" dumps a bunch of stuff.  I see no local "man"
information, but:

# type iptables
iptables is a tracked alias for /sbin/iptables

# iptables --version
iptables v1.4.16.3

so I'd guess that there's some hope of learning more about the
"iptables" program being used.

   As an example of how much I don't know, that "iptables -L" command
here shows stuff like the internal SSH and Telnet ports for 10.0.0.9:

[...]
Chain PORT_FORWARD (1 references)
[...]
ACCEPT     tcp  --  anywhere             10.0.0.9             tcp dpts:22:23
[...]

but I don't see anything about the external ports which get forwarded to
these internal ports.  If you learn anything in your travels which
covers the front end of port forwarding, I'd be interested.

[Prasadx]

Thanks and sure thing will update you. The error I got was missing library when I try iptables.. maybe some path needs to be set..

[antinode]

> [...] The error I got was missing library when I try iptables.. maybe
> some path needs to be set..

   Hmmm.  That's different from my D7000.  What's the "missing library"?
If you can find it somewhere, then perhaps a command like:

      LD_LIBRARY_PATH=/path/to/dir iptables

would work.  Only one way to find out.  Dealing with the firmware on
these things often resembles the old Adventure game.  ("You are in a
maze of twisty little passages, all different."  Or was that: "You are
in a little maze of twisty passages, all different."?  Or, ...)