Penguin

Differences between version 2 and predecessor to the previous major change of Billion7100.

Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History

Newer page: version 2 Last edited on Tuesday, June 10, 2008 7:15:17 am by PeterScott Revert
Older page: version 1 Last edited on Monday, April 28, 2008 10:24:05 am by PeterScott Revert
@@ -1,50 +1,52 @@
 !Getting Billion 7100 into Half Bidge Howto. 
 (also works on a wide varierty of cheap adsl routers because they pretty much all use the same chipset) 
  
-a. Quick start | username and password, PPPoA VCMUX, VPI=, VCI=100 , dhcp server on, save config and reboot, confirm connects under NAT
+a. hard reset the modem , making sure you know the login. dhcp on your pc , browse to 192.168.1 .254  
  
-b. Configuration | Advanced | Misc Configuration | Half bridge | Enabled  
+b. Quick start | username and password, PPPoA VCMUX, VPI=, VCI=100, tick automatically reconnect, save config and restart, confirm connects under NAT.  
  
-c. Configuration | Advanced | Misc Configuration | HTTP Server Port | 81  
+c. Configuration | Advanced | Misc Configuration | Half bridge | Enabled  
  
-d. Go back to Configuration | WAN | pvc0 submit| and return the encapsulation to pppoa VC-MUX, Half bridge alters this wrongly to ppoe llc 
+d. Configuration | WAN | pvc0 submit| and return the encapsulation to pppoa VC-MUX, Half bridge alters this wrongly to ppoe llc 
  
-e . reboot router,  
+b0 . Save settings and restart  
  
-f. use dhcp client downstream, and there you have it, your WAN ip address on your box, check your firewall
+c . Configuration | Advanced | Misc Configuration | HTTP Server Port | 81  
  
-These and many similar modems support `DMZ` , but all this does is NAT to a static LAN address, sans firewall. Turn off NAT and DMZ doesnt work . This might get around some folks `port forwarding`/virtual server issues , but youre still stuck with a weak NAT implementation
+b0. Save settings and restart  
+  
+And there you have it , if you are lucky, and the stars line up, your WAN ip address on your box , check your firewall. Whether it will survive a reboot depends . Now you can get back into the modem at 192.168.1.254:81  
+  
+While the above worked for me in 2008 using Xnet, attempts to reproduce it that same year using more or less identical hardware , but another ISP,Planet, were eratic at best. YMMV
  
 !Getting Billion 7100 into 1:1 NAT+DMZ 
  
-You could however try this, it worked here. It is said that 1:1 NAT removes a NAT step, but theres still more routing going on than necessary
+This is an alternative method if half bridge doesnt work well. The modem just maps all incoming traffic to the static ip address of your linux router
  
 a. Configuration | LAN | DHCP server | off 
-  
-a2. Check device IP address and netmask {same subnet as your linux router}  
  
 b. Configuration | Advanced | NAT | Enabled 
  
-c. Configuration | Advanced | NAT | mode | NAT (static NAT) 
+c. Configuration | Advanced | NAT | mode | NAT (sometimes static NAT) 
  
 d. Configuration | Advanced | NAT | Session name config 
  
 d2. Enter: {yourname}, interface: PPPoPvc0, add, submit 
  
 d. Configuration | Advanced | NAT | Session name config | go back to nat config 
  
-e. Enter: session: {yourname}, users IP= {static IP of your linux router }, add, submit 
+e. Enter: session: {yourname}, IP= 192.168.1.1 }, add, submit 
  
 f. Configuration | Advanced | Misc config | DMZ | Enabled 
  
-f2. Under DMZ Host IP, enter: {static IP of you linux router}  
+f2. Configuration | Advanced | Misc config | Host IP | 192.168.1.1  
  
 g. Save settings and reboot 
  
 h. setup your linux router with a static IP on the same subnet as the modem. 
  
-This will forward all incoming ports to the linux router, and basically map the dynamic WAN ISP to your linux routers static IP, directly and exclusively. The advantage of this is if your firewall ruleset needs to know its WAN IP (which it will if your iptables is tight), then its much easier with a static IP on the routers WAN. 
+Set your linux router to have a stsic WAN address 192.168.1.1. The will forward all incoming ports to the linux router, and basically map the dynamic WAN ISP to your linux routers static IP, directly and exclusively. The advantage of this is if your firewall ruleset needs to know its WAN IP then its easier with a static IP on the routers WAN. 
  
 If you have anyway to compare the performance of these two methods let us know, edit the page! 
  
 !Dynalink RTA1320