NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R8500 Iptables access from Raspberry Pi using Python or shell script
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 ...
> [...] 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.
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
HI
Thanks for the link - am able to telnet but dont see iptables.
Any suggestions?
Thanks,
> [...] 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.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..