On Thu, May 30, 2013 at 05:20:18PM +1000, Tony Langdon wrote:
On 29/05/13 3:29 PM, Craig Sanders wrote:
what sort of router are you using?
if it's running linux, you may be able to do port-forwarding or run a simple http/https proxy so that connections from your LAN (i.e. your PC) to a particular port on your router get forwarded to port 80 or 443 on your d-link modem.
That isn't an option. It can't even see the d-link. The Ethernet interface doesn't get an IP address, only the PPP interface gets an IP when PPPoE comes up. Pings get rejected by a router further downstream, so it's obvious that they're not going where I want. I can't see a way of accessing the d-link without a switch (or using a totally different router).
too bad. have you tried manually adding an IP address to the router's ethernet interface? this may be difficult or impossible unless it's running linux and you have shell access to it. i've got my adsl modem (in bridged mode) connected to one of the two NICs on my main machine (gateway/firewall/server/desktop), with 192.168.1.1 on that interface as well as the PPPoE (the modem itself defaults to 192.168.1.254). at various times, i've had netcomm, d-link and another brand i can't remember as the bridging modem. it's currently a billion 7401. i've had no trouble accessing the modem's web admin interface, shell, and snmp over the 192.168 IP address. e.g. a trivial little snmp script i wrote ages ago (so long ago i can't even remember if the snmp OIDs are generic or specific to the billion modem): # get-billion-sync-speed.sh Down: 14001700 Up: 1023900 #! /bin/bash MODEM='192.168.1.254' DN=$(snmpget -v1 -c public -Ov -Oq "$MODEM" '1.3.6.1.2.1.10.94.1.1.4.1.2.3') UP=$(snmpget -v1 -c public -Ov -Oq "$MODEM" '1.3.6.1.2.1.10.94.1.1.5.1.2.3') echo "Down: $DN" echo " Up: $UP" craig -- craig sanders <cas@taz.net.au> BOFH excuse #339: manager in the cable duct