| View previous topic :: View next topic |
| Author |
Message |
Joe_Astor
n00b
Joined: 29 Aug 2005
Posts: 18
|
 Posted: Mon Aug 29, 2005 1:39 pm Post subject: Problems Connecting To Machine |
 |
|
Hi there.
I'm having problems connecting to IPs I have set up on my machine and I'm not quite sure what the problem is.
The setup I am trying to get working has worked for me before, but now for some reason it is choosing not to.
On my Gentoo box I have the eth0 configured with the IP address 192.168.0.2.
I want to add another IP address of 192.168.1.2 for a server I intend to run.
I type in ifconfig eth0:1 192.168.1.2 up, and then ifconfig on its own and I get this;
eth0 Link encap:Ethernet HWaddr 00:0D:87:14:F3:CE
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20d:87ff:fe14:f3ce/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9533471 errors:0 dropped:0 overruns:0 frame:0
TX packets:9558645 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:59253197 (56.5 Mb) TX bytes:480407858 (458.1 Mb)
Interrupt:11 Base address:0xe800
eth0:1 Link encap:Ethernet HWaddr 00:0D:87:14:F3:CE
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0xe800
When I ping the new IP or connect to it FROM the Gentoo box, everything works fine.
But if I try to ping the new IP or connect to it in any way from my Windows machine, I get no response.
I dont have any firewalls or routers or such between the 2 PCs.
This has worked for me in the past, but for some reason it refuses to work for me now 
I realise it may well be a Windows issue and not a Gentoo issue, but in either case, any help you could give me would be appreciated. |
|
| Back to top |
|
 |
Ph0eniX
Guru
Joined: 24 Sep 2004
Posts: 502
Location: New York, U.S.
|
| Posted: Mon Aug 29, 2005 2:32 pm Post subject: Re: Problems Connecting To Machine |
|
|
| Joe_Astor wrote: | Hi there.
I'm having problems connecting to IPs I have set up on my machine and I'm not quite sure what the problem is.
The setup I am trying to get working has worked for me before, but now for some reason it is choosing not to.
On my Gentoo box I have the eth0 configured with the IP address 192.168.0.2.
I want to add another IP address of 192.168.1.2 for a server I intend to run.
I type in ifconfig eth0:1 192.168.1.2 up, and then ifconfig on its own and I get this;
eth0 Link encap:Ethernet HWaddr 00:0D:87:14:F3:CE
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20d:87ff:fe14:f3ce/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9533471 errors:0 dropped:0 overruns:0 frame:0
TX packets:9558645 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:59253197 (56.5 Mb) TX bytes:480407858 (458.1 Mb)
Interrupt:11 Base address:0xe800
eth0:1 Link encap:Ethernet HWaddr 00:0D:87:14:F3:CE
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0xe800
When I ping the new IP or connect to it FROM the Gentoo box, everything works fine.
But if I try to ping the new IP or connect to it in any way from my Windows machine, I get no response.
I dont have any firewalls or routers or such between the 2 PCs.
This has worked for me in the past, but for some reason it refuses to work for me now
I realise it may well be a Windows issue and not a Gentoo issue, but in either case, any help you could give me would be appreciated. |
The two IP addresses are on different subnets. No systems that are on 192.168.0.0/24 will be able to get to 192.168.1.0/24 without some type of routing. If you want just another IP for the 192.168.0.2 host, then make it 192.168.0.x - where x is any number between 3 and 254 (assuming that those addresses are not already in use). |
|
| Back to top |
|
|
Joe_Astor
n00b
Joined: 29 Aug 2005
Posts: 18
|
| Posted: Mon Aug 29, 2005 2:47 pm Post subject: Re: Problems Connecting To Machine |
|
|
| Ph0eniX wrote: |
The two IP addresses are on different subnets. No systems that are on 192.168.0.0/24 will be able to get to 192.168.1.0/24 without some type of routing. If you want just another IP for the 192.168.0.2 host, then make it 192.168.0.x - where x is any number between 3 and 254 (assuming that those addresses are not already in use). |
So if I had a Router (even though it's only over a LAN) I wouldn't have this problem? |
|
| Back to top |
|
|
Ph0eniX
Guru
Joined: 24 Sep 2004
Posts: 502
Location: New York, U.S.
|
| Posted: Mon Aug 29, 2005 3:05 pm Post subject: Re: Problems Connecting To Machine |
|
|
| Joe_Astor wrote: | | Ph0eniX wrote: |
The two IP addresses are on different subnets. No systems that are on 192.168.0.0/24 will be able to get to 192.168.1.0/24 without some type of routing. If you want just another IP for the 192.168.0.2 host, then make it 192.168.0.x - where x is any number between 3 and 254 (assuming that those addresses are not already in use). |
So if I had a Router (even though it's only over a LAN) I wouldn't have this problem? |
Why don't you start by explaining what you're trying to accomplish? As I said, if all you need is another IP, then all you have to do is give it one in the 192.168.0.0/24 subnet and everyone is happy. Otherwise, you can configure your Gentoo system as a router and make sure that other systems on the network are aware of it (by adding static routes) ...another solution would be to add addresses on the 192.168.1.0/24 subnet to all the hosts that need to access the secondary address on the Gentoo box. There are many ways of slicing the pizza. |
|
| Back to top |
|
|
Joe_Astor
n00b
Joined: 29 Aug 2005
Posts: 18
|
| Posted: Mon Aug 29, 2005 4:36 pm Post subject: |
|
|
I'm trying to set up servers on my box, each with their own IP address, but running through the same NIC.
For example,
192.168.1.0 would use
1 PTR dns.jason.org.nz.
2 PTR irc.jason.org.nz.
3 PTR mail.jason.org.nz.
etc etc.
But I'd like to keep 192.168.0.0 available for other, non server related uses.
Hopefully that would explain my intentions 
Also now that you reminded me about it, the last time I used this sort of setup I had the use of a router and there was no problems.
At the moment I only have a crossover cable.
I'm hoping that if I get another router, that would correct any problems? And there would be no hassles connecting between 192.168.0.0 and 1.0 ? |
|
| Back to top |
|
|
Ph0eniX
Guru
Joined: 24 Sep 2004
Posts: 502
Location: New York, U.S.
|
| Posted: Mon Aug 29, 2005 7:09 pm Post subject: |
|
|
| Joe_Astor wrote: | I'm trying to set up servers on my box, each with their own IP address, but running through the same NIC.
For example,
192.168.1.0 would use
1 PTR dns.jason.org.nz.
2 PTR irc.jason.org.nz.
3 PTR mail.jason.org.nz.
etc etc.
But I'd like to keep 192.168.0.0 available for other, non server related uses.
Hopefully that would explain my intentions
Also now that you reminded me about it, the last time I used this sort of setup I had the use of a router and there was no problems.
At the moment I only have a crossover cable.
I'm hoping that if I get another router, that would correct any problems? And there would be no hassles connecting between 192.168.0.0 and 1.0 ? |
I'm still not clear what you're trying to do. 192.168.0.0/16 addresses are used for private networks (NAT-ed). They can't be routed to/from over the internet so defining mail.jason.org.nz (or any other internet hostname) on your DNS server(s) and pointing it to one of those addresses would have no effect. If your ISP gave you enough public IP addresses then you can use those to define the DNS entries and then have your internet gateway/router forward requests for them to a 192.168.1.0/24 address.
I hope you realize though that adding an IP address alias does not give you any extra security since all the packets are still routed on the same physical interface so you might as well configure port forwarding to the 192.168.0.0/24 range. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Networking & Security
