Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Whilst I can take it offline (to the LAN) and administer my DSL modem, I cannot access the administration facility from the LAN, eg to view datacomms speeds, assign new port-forwards...
I have separate DSL modem, router, switch, and wireless access point boxes - picked up at different times, over the years... Accordingly the route to/from the Internet is modem - router - switch or AP - SuSE PC.
The router is actually a Freecom FSG-3 Internet Gateway 'appliance': web server, email server, database server, (Samba) file server, multimedia server, as well as router - and it runs LAN DHCP and DNS using dnsmasq. The older DSL modem was set as 192.168.1.1 (per Linksys) 'inside' and is on a static IPaddr 'outside'. The router WAN port was set to be on 192.168.1.2 and the LAN port to 192.168.2.3 - different sub-nets!
Now I have a new ADSL2 modem on a 7~8Mbps link, but I noticed that its port forwarding facilities are limited to the 'inside' sub-net only, ie if the modem were to stay as 192.168.1.1 then it will only forward to 192.168.1.nnn addresses. Oops!
So I disposed of the 'NAT'/DMZ-ish/'dead zone' and brought the new modem in as 192.168.2.1 and changed the router's WAN settings accordingly. All works very well (from the inside going out: web, email...). However I cannot access the modem, either by name (through DNS) or by IPaddr.
I tried setting both router masks to 255.255.255.2 but that didn't work either... Any ideas/wisdom/solution please?
Alternatively, did I make a mistake trying to collapse the sub-nets into one. Should I set up the modem separately (back to where it was) and then have IT port-forward to the router and have the router port-forward to the appropriate server/client - can one even forward-a-forward like that?
Regards,
=dn
Summary:
router LAN settings: 192.168.2.3, mask 255.255.255.0, gateway 192.168.2.1
servers and printer are on fixed IP addresses 'low down'
DHCP operates for laptops etc 192.168.2.128 and higher
router WAN settings: 192.168.2.2, mask 255.255.255.0, gateway 192.168.2.1
modem set to 192.168.2.1, with outside static IPaddr and DNS etc
Not 100% sure, but I think you may be in the wrong forum. Are You looking for help in configuring your DSL modem?
But, if I had your network setup, I would bridge the modem and allow the router to do all port forwarding and any routing that needs to done. The DSL modem would need to be configured to bridge but once you have done that theonly device you would really be configuring is your router which are typically much easier to configure and give you more controll.
Do a google search on your type of modem and how to configure it for bridge mode. I know DSLreports.com has very in depth guides on how to config different modems so you might want to start there. Hope that helps!
Thank you for your response. I can't quibble on forum choice - it seems like a LAN issue to me, but...
I'm not familiar with bridging. I have not disappeared into the Linksys docs to check out the ability of this modem to run in bridge(d) mode. So that's today's 'homework'.
However, if the modem is bridged, my recollection is that all of the declarations and authentication data would then be declared in the router. Correct? Unfortunately I (think) that this cannot be done - in this case.
Further information:
- I am (now) in the UK
- UK DSL is PPPoA
- the router offers PPPoE and DHCP but not PPPoA mode
Apologies if this 'new' data affects the consideration.
http://www.dslreports.com/faq/6323
This is to configure a westel DSL modem and linksys router for bridge mode. BUT....Yes the router will do the authentication.
Is there a Firmware update to the router that will allow PPPoA auth? If not, you may be able to find a router hack that will allow it (Please make sure you know what your doing with this because you can brick your router). Which router model do you have?
If you can not do updates, then how about opening all ports from the modem to your router? That is put your router in a DMZ and then have it do all the forwarding/port handling. What modem model do you have?
Also apologies for making this tough. Perhaps I'm going about things the wrong way. Should I perhaps put the modem on a sub-net of its own/different to the router and in-house PCs, and then set the modem to forward everything to the router which (might?) then forwards to the individual chosen PC?
The modem is a Linksys AM-200
The router is a Freecom FSG-3
There is no further firmware update for the router.
I'm going to try the bridging idea, but I don't think it will work because the router will need to offer authentication over PPPoA - let's try though!
Thanks for the reference. I also found Forums » Equipment Support » Hardware By Brand » Linksys » [General] BEFSX41 / Siemens 4100 DSL Modem problem and solution
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.