Linux - Networking This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
01-21-2006, 05:03 AM
|
#1
|
|
Member
Registered: Apr 2002
Location: Poland, Gliwice/Pszczyna
Distribution: Mandrake, Slackware
Posts: 41
Rep:
|
problem after changing IP class
Hi
I've changed internal ip adresses from someip/24 to someip/23 and since then i can't ssh to my router from the internal network, i can't access web server, but i can ping my router. Anybody knows what may be the cause of that problem? I'm using Slackware 10.2 with 2.6.14 kernel. Internal network is working on brigde made of two interfaces. Before changing my IP class everything was working fine.
P.S As usual - sorry for my english 
|
|
|
|
01-22-2006, 02:04 PM
|
#2
|
|
Moderator
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 42,711
|
well you clearly arsed up your netmask... not sure why you're even asking what the cause is 
|
|
|
|
01-22-2006, 03:47 PM
|
#3
|
|
Senior Member
Registered: Dec 2005
Location: Massachusetts, USA
Distribution: Ubuntu 10.04 and CentOS 5.5
Posts: 3,873
|
I'm guessing here but I would try using a netmask of 255.255.254.0
|
|
|
|
01-22-2006, 04:00 PM
|
#4
|
|
Moderator
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 42,711
|
that IS /23, which is what caused this situation.
|
|
|
|
01-22-2006, 06:25 PM
|
#5
|
|
Senior Member
Registered: Dec 2005
Location: Massachusetts, USA
Distribution: Ubuntu 10.04 and CentOS 5.5
Posts: 3,873
|
Quote:
|
Originally Posted by acid_kewpie
that IS /23, which is what caused this situation.
|
I know perfectly well that "that IS /23". Gotta love those caps.
How do you know that he did this? Maybe he just started changing the third octet for nine bit host numbers but forgot to change the netmask. The original post isn't clear what was and what was not done. Or maybe the broadcast mask is wrong.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 01:08 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|