joep42
join:2002-02-19
Clarks Summit, PA
1 edit | reply to mn wonder
Re: Siemens Gigaset SE567 Port Forward Problems AN EASIER WAY TO BRIDGE A SIEMENS 567 TO A LINKSYS WIRELESS ROUTER
Frontier replaced my SpeedStream 5200 with a Siemens SE567 and when the tech guy saw my Linksys SRX200 wireless router, he said that it was a far superior wireless box then the Siemens. So he bridged the Siemens to the SRX200 and unfortunately, I really didn't pay attention to how he did it. But everything worked superfine until my son and I decided to rearrange some of our computer gear.
We thought we would try the Siemens all in one box (DSL modem/wireless router). As already noted by others, documentations is non existent but after some hard resets we got it working. The wired (Ethernet) ports worked perfectly but the wireless side really sucked. Basically, if you weren't within spitting range of the Siemens box, the wireless signal was erratic and was often dropped. If we rebooted one of our wireless laptops that was not near the Siemens box (which had been connected OK), it refused to reconnect without re-booting the Siemens box. After tinkering with this for about a week, including relocating the Siemens box, we took the Linksys SRX200 out of storage.
I thought bridging to the SRX200 was going to be a nightmare based on everything I read in this and other posts. However, my son, a network guru, found an much easier solution which is as follows.
BRIDGING SIEMENS SE567 TO LINKSYS SRX200 WIRELESS ROUTER
Make/Ensure the following setting in the Siemens:
Under Local Gateway IP Network Custom Settings
-Ensure DCHP Server is enabled
-Default Gateway has WAN checked.
-IP Range was reduced to 15 (optional).
LAN is checked on LAN/WAN Port Screen (yes - LAN, not WAN)
The Gateway Wireless is Disabled
UPnP is Disabled.
Under Security, the Firewall was Disabled (would be duplicate effort to the SRX200).
No changes were made to the ISP Connection - ATM settings. The ISP Connection was left at PPPoE 8/35.
A short RJ45 cable was connected between port 4 (LAN/WAN) on the Siemens and the Internet connection on the SRX200. All RJ45 cables were moved to the Linksys as well.
On the SRX200 the only change necessary was in Internet Setup Screen. Change PPPoE to Automatic Configuration - DCHP. Configure the Linksys for the desired security and wireless access.
In addition to avoid the nightmare of bridging the Siemens, another benefit is I can plug a RJ45 cable into the Siemens and my laptop I can still access it by entering 192.168.254.254. Of course we can access our Linksys SRX200 anytime by entering 192.168.1.1.
Everything is solid as a rock, signal strength 5 times better than the Siemens, no dropouts, no loss of download speed, no problems, all is well. |
|
 guypd
join:2008-05-08
Silver Springs, NY | This wouldn't be bridging the Siemens Gigaset SE567. The SE567, would still be acting as a router. That is what enabling the DCHP means. |
|
 Doctor OldsI Need A Remedy For What's Ailing Me.Premium,VIP
join:2001-04-19
1970 442 W30
kudos:18 | reply to joep42
said by joep42:I thought bridging to the SRX200 was going to be a nightmare based on everything I read in this and other posts. Actually it is quite easy to do. You simply edit the fist VC setting in the SE567 and that is it. Maybe 3 or 4 steps all in all.said by joep42:However, my son, a network guru, found an much easier solution which is as follows. BRIDGING SIEMENS SE567 TO LINKSYS SRX200 WIRELESS ROUTER Make/Ensure the following setting in the Siemens: Under Local Gateway IP Network Custom Settings -Ensure DCHP Server is enabled -Default Gateway has WAN checked. -IP Range was reduced to 15 (optional). LAN is checked on LAN/WAN Port Screen (yes - LAN, not WAN) The Gateway Wireless is Disabled UPnP is Disabled. Under Security, the Firewall was Disabled (would be duplicate effort to the SRX200). No changes were made to the ISP Connection - ATM settings. The ISP Connection was left at PPPoE 8/35. That is Doubled NAP/NAPT when using DHCP behind another Router and makes opening any ports a real pain. DHCP is Automatic IP assignment and Automatic IP requesting between a DHCP Server and a DHCP Client. It takes no experience to use DHCP as it is all automatic. If the SE567 was Bridged, the Linksys would be setup for PPPoE and it would have a Public IP instead of the Private IP is has now.
For each packet coming in and going out there is double translation going on. First the SE567 converts everything from the Public IP to the SE567 LAN IP range (192.168.251.1 ) and now your Linksys converts that that Private IP to a new Private IP for the Linksys LAN range (192.168.1.2)
said by joep42:In addition to avoid the nightmare of bridging the Siemens, another benefit is I can plug a RJ45 cable into the Siemens and my laptop I can still access it by entering 192.168.254.254. Of course we can access our Linksys SRX200 anytime by entering 192.168.1.1 You can do that without having to plug your Laptop into the SE567, since when you have the Linksys DHCPed to the SE567, 192.168.254.254 is a valid reachable IP from the Linksys LAN as it gets translated on the Linksys WAN over to the SE567 LAN. Try it.
Regards,
Doctor Olds
--
What’s the point of owning a supercar if you can’t scare yourself stupid from time to time? |
|
joep42
join:2002-02-19
Clarks Summit, PA | Doctor Olds (I'm a former Buick 455 muscle car owner) - you are right, I can access my Siemens without a cable. Thanks.
I learn something new everyday. My question now: Is one method of using the SE567/Linksys SRX200 combo better than the other? In other words, bridge the Siemens SE567 (by editing the VC settings) to the Linksys or running as I have now with DHCP set to Automatic on the SRX200? Right now everything in the later mode is rock solid and I ran Steve Gibson's Shields Up suite and passed with flying colors.
I read your comments about opening ports. I have NAP disabled on the Siemens, but not NAPT. My college age kids have been playing World of War Craft (one wirelessly, one on Ethernet) without a hiccup.
So - should I leave well enough alone (if it ain't broke don't fix it) or should I bridge the Siemens for better performance?
Thanks again (retired geek). |
|
 Smith6612Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:21 | Whatever you'd like to do. Bridging won't allow you to get modem stats should you ever have a problem, but it will allow you to do port forwarding and such a lot better than the Seimens can do. |
|
Doctor OldsI Need A Remedy For What's Ailing Me.Premium,VIP
join:2001-04-19
1970 442 W30
kudos:18 | reply to joep42
If it ain't broke, then of course you are OK to leave it as currently configured now. Performance wise, you won't see any speed changes with either setup. The only thing that would be possible is issues with complex applications requiring special Port Forwarding. If you have no current problems now, then you can of course leave it just as it is. If you ever do run into any issues, then you may want to Bridge Mode the SE567, but until then enjoy.
When I posted NAT/NAPT, I meant it as either/or not concurrent. NAPT is really a subset of NAT, yet different Router Makers use different terms. I personally subscribe to the Siemens definition (see image below). NAT is a "one to one" translation (1 Public to 1 Private) while NAPT is a "one to many" translation (1 Public to Many Private) then there is Concurrent NAT/NAPT which we will not go over now as it requires a Static Public WAN IP. The default is NAPT Only in the Siemens/Efficient Product Line.
Regards,
Doctor Olds
--
What’s the point of owning a supercar if you can’t scare yourself stupid from time to time? |
|
Doctor OldsI Need A Remedy For What's Ailing Me.Premium,VIP
join:2001-04-19
1970 442 W30
kudos:18 | reply to Smith6612
said by Smith6612:Whatever you'd like to do. Bridging won't allow you to get modem stats should you ever have a problem, but it will allow you to do port forwarding and such a lot better than the Seimens can do. You can actually reach a Bridged Siemens's Modem by changing your Router behind it to Static Private IP to match the range the Siemens uses on it's LAN instead of the current PPPoE connection type and then read the DSL Stats easily with no cable swapping involved. Or on the Tomato Firmware Routers, you can setup to actually Route to a Private IP on the WAN while also keeping the PPPoE active on the WAN which other Routers don't always have as an available feature. Again, no cable swapping required. The problem is a lot of people do not know how to setup Static IP Routes which alters the Routing Table (the Routing Table is seen on this page »192.168.254.254/routestatsx.htm ). All Routers have a Routing Table, but not all allow manual additions to the table nor do people know what IP data to place in the blank fields.
As far as Port Forwarding, the setting up of rules for open ports is just as easy as any other Router I've worked with, in fact it is easier than some others I've seen.
Regards,
Doctor Olds
--
What’s the point of owning a supercar if you can’t scare yourself stupid from time to time? |
|
Smith6612Premium,MVM
join:2008-02-01
North Tonawanda, NY
kudos:21 | I forgot you could there lol, thanks Doctor Olds. It sounds like it's the same way I would access my Verizon Westell modem if I had it bridged. |
|
