Let me start off by saying everything WAS working...I have a lab environment comprised of two subnets (.1.128/25 and .2.0/25). On the .1, I have 3 Solaris 8 servers running NIS, NFS, databases, DNS, various services, etc... the network was setup on VLAN'd Layer 3 switches with the VLAN interface addresses acting as default gateways (dgw) for the two networks (on a single switch). The switch dgw was a router for outside connectivity. The servers are running ODCS OpenSSH.I was having problems with the VLANs, so I reconfigured the network so that each subnet had it's own switch as a dgw, and they route through a point-to-point static route setup as 192.168.0.1&2 on a separate VLAN between the two gateway switches.Here's where the problems start:First, ALL the services (NIS,NFS,databases,DNS,etc) are STILL WORKING. I can ping all the addresses. Traceroutes show the proper path thru the point-to-point, etc. There are NO firewalls setup, hardware or software, network or host-based... no iptables running, etc.
The three servers are on the .1 network. I can ssh to them from hosts on the .2 network no problem. However, I cannot complete an ssh login to them from any host on the .1 network. I get a password prompt, enter the pwd, and then it hangs until I receive a "Connection timed out" error message several minutes later. The next time I log in however, it shows "Last successful login" from the failed attempt.While the connection is hung, netstat on the server shows "ESTABLISHED" to the client on the proper port. nother odd indication is that I CAN sftp to the servers from hosts on the .1 network.
I'd like a way to see all of the devices on my local network and what their local IP address is. I recall that I used wireshark to troubleshoot a similar problem a while back, but it doesn't seem to have a way to see all of the devices- only the traffic. (I'd like to do this without having to physically interface with my router if possible, and I am in an encrypted network if that matters)
I have installed a web server on my local network. Everything is well configured and web pages are shown correctly from Internet (outside the local network) using the domain or the public IP.The issue is if I try to see that web pages (using the domain or the public IP) from inside the local network. In that case the router config page (192.168.1.1) is shown instead of the web pages.From inside the local network I'm only able to see the web pages using the internal IP address (192.168.1.XX).
I've got an Ubuntu server hosting our websites and other various things here in our own home. We recently switched to a router that doesn't support loopback (abomination), so I've set up hosts files on our computers so we can access our own sites when on our home LAN.
However, we often take our laptops as we travel about, and I'm guessing due to the hosts files when we try to access our sites, it'll look on whatever local network we're connected to for our server, which won't work, obviously.
Is there a way to set up something like a hosts file that'll only try to look up the local IP of the server when we're on a specific network (our home one), or have one that tries to look for the local IP first, then proceeds to try and resolve the domain name and use the external IP if the local IP doesn't work?
I've followed several guides and am trying to get NFS working on my local network. For starters, I think I should be able to NFS mount a drive on the server (192.168.1.65) TO the server. From there I'll work with another client (currently 192.168.1.80)
I have a Dell PowerEdge 1650 server with 3 NICs in it. I am trying to use one NIC (eth0) to connect to the internet, the second NIC (eth1) to share the internet connection to a LAN, and the third NIC (eth2) to connect to the LAN.
It is running Ubuntu server 8.10
The problem that I'm having is that NetworkManager (version 0.7.0) keeps setting eth2 as the default connection, and then I don't get any internet at all from the server.
My main goal is to be able to share files from the server to computers on the LAN. The secondary goal is to have a virtual machine hosting a Halo server, connected through eth2, so that it can host LAN games. But that is a secondary goal after I get the connections to work.
I've been looking around and finding other people who have done bits and pieces of this, but not the whole thing. I had been hoping to simply use the NetworkManger, but I don't mind editing config files.
Also I can't seem to find any good instructions on editing the /etc/network/interfaces file. The man file is incomplete, and everything seems to point back to the man file.
I'm working with a Ubuntu 10.04 LTS system with two network interfaces (both Ethernet). I wish to setup this system such that it is simultaneously connected to my local and an OpenVPN network and able direct traffic between the connections depending on what program is sending the traffic. The problem: Under my current OpenVPN configuration all network traffic is directed to the VPN.
In practice, I would like OpenVPN to operate out of one of my two network interfaces and leave the other interface connected to the local network. Then by default all network traffic should be directed to my local network unless I specify (on a per program bases) that certain traffic should go though the VPN. These two network connections can (should) stay completely independent of each other and do not need to talk to each other.
I have two networks. One of them is wired, the other is wireless. The wired has an internet connection and a few other computers connected to it. The wireless network has a few hosts connected to it too, but it has no internet connection. What I've been trying, fruitlessly, to do, is make all connections that are bound to the internet, or my wired network, be routed that way, and all the connections to the hosts of the wireless network go that way.
Here's the setup..
Wired:
192.168.1.0/24 Gateway = 192.168.1.1
Route internet through here
Wireless
192.168.2.0/24 Gateway = 192.168.2.1
If my computer sends a packet to the internet, it should be routed through 192.168.1.1 If I send a packet to one of the local hosts of the wireless network, it should be routed through 192.168.2.1. Here's the routing table I've set up(This is one of many configurations I've tried)
Code:
$ ip route show 192.168.2.1 dev wlan0 scope link 192.168.2.0/24 via 192.168.2.1 dev wlan0 src 192.168.2.4
[code]....
With this, and everything else, I get destination host unreachable when pinging. The strange thing is that, if I unplug my eth cable, reboot and connect to the wireless network, everything is fine and I can access the router and the others. I'm trying to improve my networking skills, as I've had this of setting up a small linux box as a router for quite some time, for the fun of it, but I need to get routing under control before I go ruin my network.
As it looks like the number of DNS Top Level Domains are just going to proliferate in the near future, use locally on an RFC 1918 private network in order to prevent a future name collision issue?
.local is the most obvious one but as that was stolen by Apple for mDNS/rendezvous use it's probably wise to avoid it now.
If i want to use SSH to log on to my home computer, which is connected to the router, how do I go about connecting to it?If I get my external IP of the computer at home, it will show me the external IP of the router correct? Then I need to forward the router's external IP to my computer at home. But then, how do I connect using ssh? or do I need to consider my local IP of the computer at the router's network?
how to resolve an ip with a port in linux?, how to include this on the dns. So the user don't have to remember the ip address and the port. like the user will only type http://scanfiles then it will resolve the corresponding ip. is it possible?
Running Ubuntu 9.10. In the Remote Desktop config dialog I get: "Your desktop is only reachable over the local network. Others can access your computer using the address 127.0.0.1 or tabatha.local." I understand this means only the loopback ip address is available. All my other machines show their true local ip address (e.g., 192.168.1.104) in this dialog. Thus I cannot log on to this desktop from other machines.
When I try to do a remote logon from another Ubuntu 9.10 box (or from an XP box using a VNC viewer), I get: "Connection to 192.168.1.102 has been closed." What steps are needed to make this machine show its actual ip address? All file sharing between the various machines is working properly and all windows shares back and forth between XP and 'nix, and among the the vaious XP boxes and linux boxes are available as designed.
up until about four days ago connecting to the local LAN was as simple as booting Ubuntu, and letting nm-applet automatically connect on Auto Eth0 But the other day it just randomly stopped working, with no cause that I can think of. I can still connect to the internet (This is via a PPPOE connection, running through the same wired interface) so it can't be a hardware problem with the ethernet port/cables themselves. nm-applet just stays spinning in circles, and nothing ever happens. I tried deleting the auto Eth0 entry, and creating another LAN entry with exactly the same settings, but I still get the same problems. way to completely restore nm-applet settings? Or some other way to give me access to the local network?
I've been having strange local network behavior with my Ubuntu 10.04 box. First off DNS was pretty flakey, but I replaced the automated DHCP servers with 8.8.8.8 and 4.4.4.4. Now I see very strange behavior in my local network, the symptoms of which are frequent dropped connections trying to use FTP, VNC, or Samba to try and connect to my other machines. I did a tracepath and got this back:
tracepath 192.168.1.136 1: 192.168.1.105 (192.168.1.105) 0.112ms pmtu 1500 1: no reply 2: no reply 3: no reply 3: 192.168.1.105 (192.168.1.105) 3002.961ms !H Resume: pmtu 1500 [Code],,,,
Have a domain registered on a public ip. The domain server for the domain is on the same local network as the web server that uses the domain. The web server naturally has a local and public ip address.
The problem is that whenever I try to access the domain from my local network the lookup for the domain fails, as it cannot find the server from the local network. What's the most painless solution to this problem?
TL;DR: need for my domain to be accessible from both my local network and the outside world, now it's only from the outside which is a problem.
My router is a DHCP Server.My Access Point is a DHCP Server.I'm wondering if it is really necessary and usefull.Is it possible to get an IP from the Router through the Access Point.For exemple I connect my laptop to the wifi Access Point and the IP is given by the router only.
I Have Ubuntu 9.10 Server installed and for some reason after updating our server with the ubuntu update manager, we can no longer connect to the network via remote desktop, let alone not even able to ping. We are actually able to connect to the internet itself just fine so I dont understand why this isn't working
# Generated by iptables-save v1.4.5 on Mon Jan 11 12:22:25 2010 *raw :PREROUTING ACCEPT [1038480:666298388]
[code]....
somehow iptables -t nat -A PREROUTING -i eth2 -d x.y.z.a -j DNAT --to-destination 192.168.1.1 helps, but imho there should be some other solution. kernel is 2.6.31.6, architecture is x86_64.
P.S. i've also tried iptables -A POSTROUTING ! -d x.y.z.a -s 192.168.1.0/24 -j MASQUERADE that didn't help either.
I have a subdomain called www3 and I cant see it outside of our network. It's added in vhosts.conf in /etc/httpd/conf.d, and I can access it through [URL], but only when on vpn.
We have another www2 that is both local AND outside the vpn. I am testing the site live and need access to it. Is there another file besides vhosts.conf that I need to add the ssubdomain in? Here's what I added in my vhosts.conf
icmp request from an ip that is in the same network as one of the local interfaces is not responded to, if the ping request is received via an interface in a different network. Is this some security feature?
I know there are tons of help guides out there for this, and I have looked at and tried them all. I am trying to do something really simple, and just can't seem to get it working. I have been trying on and off for the better part of a week now, with not much luck. What I am tyring to do is have a Ubuntu 10.10 server serve out DHCP addresses and be the DNS for the local network. The local network will have no internet access, so it only needs to know the names of the local server. My network setup is as follows:
1: Windows Vista web server 2: Ubuntu DHCP3 and BIND server to give IP's and resolve local names. 3: A bunch of tablet computers connected via dhcp to the network, that need to access the web server on the Windows machine.
I have DHCP working nicely, but it fails to propagate the hostnames to the tablet computers. Unfortunately I need this to work, as the tablets do not have the capability of having a 'hosts' file.I have tried just about every self-help guide I can find, and just can't seem to get this work. Everything seems to work fine except for the name resolution. Any help would be great, I don't have that much hair left to pull out!
I am trying to connect to a nfs server on my local network ( the server is a fedora 12 box ) using slackware 13.1 but I am having some problems. First of all I am sure that the server is configured ok and my desktop can ping the server but when I try :
mount -t nfs 10.0.0.1:/home/usr/file /home/usr/tmp I get the following error : mount.nfs: No route to host
And when I try to rpcinfo -p 10.0.0.1 I get the error :
rpcinfo: can't contact portmapper: RPC: Remote system error - No route to host
One question that weight a lot of points was about ethernet... the professor asked why ethernet is used only in local area network? resuming i wrote that ethernet is used only in LAN because it is shared and so for big network there could be a lot problem in using the shared channel.. for istance using protocol such as CSMA/CD, if a big network has a lot of hosts, they could wait a long time before sending...is it right or am I wrong?
I want to write a custom rule to allow all connections to the ip addresses on my local network (192.168.2.2 through ...99) but I don't know how. I know adding a custom rule asks me to read a file and put it in "iptables" format, but I don't know how...
I remember back when I used Windows, there was a shell command call "net view", which would allow me to see all the other users on my wireless net.
Is there any command or application that can do this? I dont mind if it is a terminal command either, but I would really like to know a way that I could see other users on my network.
What I am trying to do is reasonably simple, I have 1 Ubuntu Desktop PC and 2 Ubuntu Laptops that are all connected via wireless network (remote desktop works perfect so no network issues)All I want to do is utilise the huge drive space on the desktop machine as a kind of fileshare for the two laptops so backups and music/photo sync can be done. I have managed to do this using Samba in that from the laptops I can write files in Nautilus to the fileshare BUT the files have no owner, no group, and no permissions, this is the if I view from the client or server side.
IE I can navigate on the laptop to the shared are by the URL...in Nautilus right click and add a blank document and call it say "test".If I now have a look at the permissions it says "The permissions of test could not be determined"
I'll apologize in advance for I'm sure this has been covered already, but I'm not sure of the search terms to even use to begin solving this problem. I don't know what I don't know.
I have three computers on my home network and want to reach them by their name instead of IP address since their ip is dynamically assigned. I'm using a Linksys WRT54GL router and have noticed that there exists a "DHCP Clients Table" in the router that seems to hold all the necessary information - host names and ip addresses.
How can I get my computers to use that as the lookup table to resolve the host names? And is this even an optimal way of being able to resolve local names?
I have (adsl router "rebotic") and we are 3 nodes sharing Internet the question is: want make network (exchange files) between me (ubuntu os) and one of my internet members ,and I don't know how can I set up network between us in ubuntu.
