Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Chrysalis]

for now get a telnet software client like putty.

add the commands to the auto login configuration, so then all you need to do is login once and its all done.

whats your username on mdws? if you not there, get yourself on there after all this work

[SignedAdam]

Thanks for your help again! this would not have been possible, with out your help 

[SignedAdam]

login to the R7000 (dd-wrt) router, then go to the Administrator - Commands tab (Diagnostics)

enter the following command, as shown, here, all in one

Code: [Select]

ifconfig vlan2:1 192.168.3.253 netmask 255.255.255.0
iptables -t nat -I POSTROUTING ! -s $(nvram get lan_ipaddr) -d 192.168.3.0/24 -j SNAT --to 192.168.3.253
then press (Save Startup)

every time the router boots, it will run this command, meaning even if theres a power cut, the settings will stay the same, sharme the same, cant be said about the HG612

I've tried saving the config file, then re uploading it, but it seems the settings you input in to the HG612 by telnet, don't show up in the UI, so after a rebootor power cut, the modem will always need the settings sent to it, again and again.... if anyone knows how to make it keep the settings, please share

[Chrysalis]

why have you added a static route to the hg612? it doesnt need it.

[SignedAdam]

would that not do the same thing as the ifconfig command ?

Code: [Select]

ifconfig br1 192.168.3.1 netmask 255.255.255.0
if you look at the Author post, they go on about doing it someway by this ?

http://forum.kitz.co.uk/index.php/topic,17596.0.html hhkb

[Chrysalis]

no its not the same thing.

there is no way to do what that command does in the GUI.

I think so people dont get misled his post should be deleted. (hhkb)

[SignedAdam]

I should be the Author of this post, thats why im confused?

[burakkucat]

Silently, stealthily, just like a ninja b*cat applies a furry black paw and the transformation has taken place. SignedAdam is now the originating poster of this thread and hhkb's post has disappeared from view.   

[SignedAdam]

Thanks alot, everything has became clear! cats rule the world

[Dray]

What I don't understand is why you have to give the modem another IP address to make this work. It's already got one, why does it need two?

[Chrysalis]

you dont have to but I think this is the easiest method, billion router's by default come with a 2nd subnet on the wan interface which is what made me start using this method. (this is why there is no messing around modem side on the billion guide).

The other way is to add route's to route specific ip's over the other interface, which would still need a route command in the cli on both devices. (it would also probably need a shrinkage of the first lan subnet on the main interface which is actually more complex).

[Dray]

I'm just wondering whether the problem is simply the Port Binding check-box shown here
http://wiki.kitz.co.uk/index.php/Huawei_HG612_-_Basic#WAN_settings
as the help says

Port binding

It is used to specify which LAN ports are bound to the WAN connection. The bound LAN ports can access the network through only the designated WAN connection.

[Chrysalis]

that's what this essentially does but as far as I know the hg612 has no way to bind lan traffic to specific ports in the UI.  That is for WAN.

[kitzuser87430]

It was either on this forum (or another) that if you untick the bindings on both lan ports, then your router (by adding a VLAN in the same subnet as the modem) could access line stats....

1) Untick bindings.

2) Set 2nd LAN subnet on router (along with required firewall rules)

VOILA...devices on the normal LAN can access the hg612 GUI

Ian

[Dray]

Yes I think you're right, I have a vague recollection of seeing that somewhere. I've just been looking at the pfsense documentation here https://doc.pfsense.org/index.php/Accessing_modem_from_inside_firewall  which says

Some DSL or cable modems have web interfaces on private IP addresses. Since these sit outside the firewall and don't have a public IP, accessing them isn't as straight forward as it might seem. The firewall is typically assigned a public IP, and sends all outbound traffic upstream to the ISP. The ISP won't route the private subnet back to the modem, leaving it unreachable. This page describes the work around needed to access the management interface on the modem from the inside of the network.

Note: The modem's management IP must be on a different IP subnet than the internal network. If it is not, attempts to connect to it will never go to the firewall to be routed out to the modem, as hosts on the internal network would try to connect to it on the local network and fail.