| reply to Frankenstien
Re: [BC] TELUS (Siemens) SE567 brdbnd (ADSL) wireless gtwy as hu I am not really sure what it is that you are trying to accomplish. I highly recommend using fixed IP addressing rather than DHCP served addressing. This is not always possible with notebook computers that connect to different networks, in which case DHCP is the only logical option.
Switch port #4 (LAN/WAN) is slightly different that the other 3. When I was using the Siemens router, I just used a single port and connected it to an 8 port hub. Port #4 would not work for that purpose. According to Glowduke:
PORT 4 on the Siemens in the TELUS setup is designed to be default a LAN port. But if you attach a connection to the 4th port that provides a DHCP connection (ie, Thompson modem) you will have a WAN connection. Allows us as techs to use the modem in various applications. Such as giving customers the second IP address(Using Thompson Modem to Switch and two routers, etc).
I think what he is saying there is that you can plug modem into the WAN port (nothing in the ADSL port), and then the SE567 can be used as a switch to feed 2 other routers. Why you wouldn't just use a dumb switch/hub for that purpose is beyond me. Far less chance of things screwing up. |
|
|
|
| couttsj ... I'm just trying to get the SE567 to behave as a switch AND be a WAP. If it's going to also be a WAP, then I assume it has to be able to offer up DHCP IPs to any wireless-G clients that ask for one (I've restricted the SE567 to wireless-G stations only). This aspect of operations seems to work fine.
What I am finding is that my wired clients (directly attached to the SE567) are sometimes getting IP's from my network router, the BEFW11S4 V4 (in the 192.168.1.102-149 range), and sometimes from the SE567 (in the 192.168.1.200-253 range). I have even seen a wireless-B client (that can only be communicating with the BEFW11S4 V4) pull down a 192.168.1.20x IP. Puzzling.
I've still got some sort of configuring to do to get the SE567 to simply pass hard-wired traffic and not act as a router for hard-wired, directly attached clients.
I know I should just ditch this thing and go get 1GB switches, but I thought I'd give this an honest attempt.
FFF
--
In every corporate organization, there will be an individual who knows everything that goes on at any given moment - this person MUST be fired immediately! |
|
| said by Frankenstien:What I am finding is that my wired clients (directly attached to the SE567) are sometimes getting IP's from my network router, the BEFW11S4 V4 (in the 192.168.1.102-149 range), and sometimes from the SE567 (in the 192.168.1.200-253 range). I have even seen a wireless-B client (that can only be communicating with the BEFW11S4 V4) pull down a 192.168.1.20x IP. Puzzling. A machine connecting to a network sends out a DHCP broadcast. It doesn't have an IP address yet, so it can't use the TCP/IP stack. If you have more than one DHCP server on a network, both servers will respond to the request, but the connecting computer will only acknowledge the first one received. It would really help if I had a diagram of your network. I see this as a possibility:
ADSL Siemens
modem WAN port port 3 port 2 port 1
---o----------------x-----------x--------x-------x
|
|
0--------o-------o-------o------0
LinkSys
WAN port port 4 port 3 port 2 port 1 |
|
| It removed all the spacing on me. Let me try again:
o ADSL modem
|
| Siemens
| WAN port port 3 port 2 port 1
x------------x-------x------x
|
|
0----------o------o------o-----0
LinkSys
WAN port port 4 port 3 port 2 port 1 |
|
| That's still not right. The LinkSys should be connected to port 3 of the Siemens. |
|
| Sorry about the long lag on getting back to my thread ... I do appreciate the help and am just trying to figure out the best way to diagram my network so others can visualize what I've got going on here and possibly recommend what to change, configuration-wise, if anything, on the SE567.
While I draft a detailed diagram in case it's needed, here's a written overview:
- my ADSL modem is the Thomson speedtouch
- the speedtouch connects to one of the LAN ports of a D-Link DI-604 E1 (acting as a 100Mbps switch, DHCP definately disabled)
- the Linksys BEFW11S4 V4 (my intended primary [& only?] 'router') connects to another of the LAN ports of the D-Link DI-604 E1
- a server PC connects to another of the LAN ports of the D-Link DI-604 E1
Note: with my residential enhanced high speed plan (3Mbps), I can pull down 2 dynamic IPs from TELUS - one for the server PC and the other for the BEFW11S4 V4, which in turn feeds various PCs through a 6-port 10Mbps hub, a 4-port 10Mbps hub & specified-MAC, WPA-PSK wireless-B.
The above arrangement has worked well for some time now.
So, what I have introduced is the SE567 as a downline 100Mbps switch ... to eliminate the 4-port hub 10Mbps bottleneck in my living/dining room area. Using the SE567 as a wireless-G WAP is an added bonus.
Even if I could figure out how to disable DHCP on the SE567, I believe I need to leave it enabled for wireless-G clients ... no?
couttsj ... if I understand you correctly, ports 1, 2 & 3 of the SE567 are not, strictly speaking, identical in nature (you say specifically to use port 3 for the Linksys BEFW11S4 V4 - why would that be?). This latter aspect I do not get (yet) ... I thought I should only avoid port 4 (the WAN port) of the SE567.
FFF
--
In every corporate organization, there will be an individual who knows everything that goes on at any given moment - this person MUST be fired immediately! |
|
| said by Frankenstien:couttsj ... if I understand you correctly, ports 1, 2 & 3 of the SE567 are not, strictly speaking, identical in nature (you say specifically to use port 3 for the Linksys BEFW11S4 V4 - why would that be?). This latter aspect I do not get (yet) ... I thought I should only avoid port 4 (the WAN port) of the SE567. The only difference between a hub and a switch is that a hub transmits all packets to all ports, whereas a switch has the ability to learn the IP address of the connected equipment and transmit packets only to the intended destination. There is a misconception that a switch is more efficient than a hub, but the difference is extremely marginal on a small network.
Port #4 on the Siemens router has the ability to act as a LAN switch port, or a modem WAN port if the ADSL port is not in use. The other 3 are just normal switch ports. I only chose #3 port to make the diagram more orderly. What I did discover is that port #4 cannot be used to piggy back to another hub/switch. |
|
| I see ... well, I'm learning quite a bit from you couttsj ... and I thank you for that ...
I take it then that my original intended use of the SE567 would have been as a 'switch' ... as opposed to a 'hub' ... except that now I also want it to be a WAP and may need to leave DHCP enabled, thus, the SE567 would now be functioning more as a 'router'.
Would you say that DHCP should / must be left enabled on the SE567 for WAP (wireless-G) functionality?
Can DHCP even be disabled on the SE567?
- if so, I cannot immediately see how to do so.
What, if anything else, would you say I should do with the SE567 config?
I have its' firewall turned off, my rationale being that it is behind the BEFW11S4 V4 and should not require this level of protection, however, this security hole still gives me pause for thought.
I have noticed that the SE567 is unable to establish system time for itself (ie. for the System Log), very likely due to having no ADSL internet connection.
From a useability / security standpoint, does it matter which router is handing out IPs? The current situation where the SE567 typically beats the BEFW11S4 to the draw (DHCP IP address allocation-wise) doesn't immediately concern me, however, it just seems messy overall.
FFF
--
In every corporate organization, there will be an individual who knows everything that goes on at any given moment - this person MUST be fired immediately! |
|
| said by Frankenstien:I take it then that my original intended use of the SE567 would have been as a 'switch' ... as opposed to a 'hub' ... except that now I also want it to be a WAP and may need to leave DHCP enabled, thus, the SE567 would now be functioning more as a 'router'. The only configuration information I have is what was supplied by Glowduke. In that configuration, the SE567 was the first router using port #4, with another router plugged into one of the other ports. He did not say if the wireless was still functional, but I suspect that it is.
said by Frankenstien:Would you say that DHCP should / must be left enabled on the SE567 for WAP (wireless-G) functionality? I do not know enough about wireless to answer your question.
said by Frankenstien:Can DHCP even be disabled on the SE567? - if so, I cannot immediately see how to do so. Yes, but it is not necessary to do so. You can use both simply by using fixed IP addressing.
said by Frankenstien:What, if anything else, would you say I should do with the SE567 config? Use fixed IP addressing where possible. Whenever you are using 2 networks (2 public addresses), make sure that you define 2 networks properly using the IP/Netmask combination. For example, 192.168.1.0/255.255.255.0 defines a network of 254 addresses (the first & last numbers are unusable). 192.168.1.0/255.255.255.224 defines a network of 30 addresses (192.168.1.31 is the broadcast address).
said by Frankenstien:I have its' firewall turned off, my rationale being that it is behind the BEFW11S4 V4 and should not require this level of protection, however, this security hole still gives me pause for thought. No comment.
said by Frankenstien:I have noticed that the SE567 is unable to establish system time for itself (ie. for the System Log), very likely due to having no ADSL internet connection. Correct, it has to be connected to one of the public addresses.
said by Frankenstien:From a useability / security standpoint, does it matter which router is handing out IPs? The current situation where the SE567 typically beats the BEFW11S4 to the draw (DHCP IP address allocation-wise) doesn't immediately concern me, however, it just seems messy overall. As I stated earlier, you don't need to worry about DHCP on the private network if you use fixed IP addressing. On the public network, you have no choice; you have to use DHCP. Fixed IP addressing is more reliable, and the routing is consistent. |
|
| couttsj ... thanks for all the help eh?
I'll search out Glowduke's SE567 threads / posts and see what else I can glean about using this gateway device as a switch / WAP, whether I should pursue disabling DHCP on it (still require specific procedure) and any other configuration changes worth making (ie. re-enabling firewall and enabled level).
FFF
--
In every corporate organization, there will be an individual who knows everything that goes on at any given moment - this person MUST be fired immediately! |
|
Glowduke
join:2009-03-14
Calgary, AB
kudos:4 | WOW. I will have to dig out the books on the SE567, but I believe you can not turn off the DHCP service(s) of the device. I will double check. The WAN port of the SE567 is designed to learn an IP address to which it transmits the packets upsteam, etc. However will retain a Private networking set up, ie, 192.x. Thus giving IP addresses to MACs as they request IPs, etc.
As for the WAP, unless we can turn off the DHCP service, will remain assigning IPs within its range. I will have to check further on this device. Hopefully I can respond with findings by Mid-afternoon on Friday.
--
The views expressed herein are that of my own and not necessarily that of my employer or any associated entities. |
|
| Glowduke ... thanks for helping out ... FFF |
|
Glowduke
join:2009-03-14
Calgary, AB
kudos:4 | WOW, I am sorry about the delay. I have been a bit busy over here. Anyhow, I dug out the Siemens and tried to muck with the settings, it is not an easy device. I believe that what we are trying to achieve is beyond the scope of the device.
The Siemens does not allow the DHCP services to be shut down. So it will retain private networking and support IP's within its DHCP range. Reading that your intended purpose was to use the Siemens as a 100MB Switch in your dining room, I think we are left to purchase a Simple Switch at 100/1000MB Speeds.
Good Luck, let me know if you have more ideas.
--
The views expressed herein are that of my own and not necessarily that of my employer or any associated entities. |
|
