Home / ubuntu / Questions

Questions[connection-sharing](ubuntu)

Martin Hope
saxbophone
Asked: 2019-08-03 12:15:40 +0800 CST
  • 2

I have my own LAN for a computing cluster which is separate from my household LAN. The cluster LAN has a WiFi router in it which provides DHCP services. The cluster LAN has no connection to the public internet of its own, the public internet can be accessed from the household LAN only.

I have configured my desktop computer (Ubuntu 16.04) to share its internet access (which it gets from a WiFi connection to the household LAN) to the cluster LAN via Ethernet. I am doing this by setting the Ethernet settings in Ubuntu's Network Manager to "Shared to other computers". This works fine and when the desktop is powered up and connected to both WiFi and Ethernet, I can access the public internet from the cluster LAN.

However, if I boot the machines on the cluster LAN after the desktop is booted, they do not receive their reserved IP addresses from the DHCP server running on the WiFi router in the cluster LAN, but different addresses instead. I would assume that this is because Ubuntu's Network Manager also provides a DHCP server built-in and this is taking precedence over the DHCP server in the cluster LAN.

Is it possible to disable the DHCP server that network manager (presumably) provides when sharing internet connection in this way, or will I have to resort to a different method to share the internet connection only?

networking network-manager dhcp lan connection-sharing
Martin Hope
Yoni Keren
Asked: 2018-09-14 01:41:24 +0800 CST
  • 4

So I'm trying to debug my server code without deploying it (which takes a long time).

I'm serving my website through angular (the framework doesn't matter IMO) ng serve --port 8080.

When I type http://localhost:8080 into the browser everything is fine and the website is loading.

192.168.1.39 is the address my router gave my laptop (I saw that on the router's admin configuration page).

When I type http://192.168.1.39:8080/ (localhost should be the same as this ip address!) it's the same message as on a phone connected to the same Wifi network(which is what I actually want-there's an issue when it comes to mobile phones images)- connection refused.

Following the debugging instructions here https://serverfault.com/questions/725262/what-causes-the-connection-refused-message

We can clearly see that on port 8080 ng is listening-

yoni@yoni-Lenovo-Z710:~/Projects/Server$ sudo netstat -tnlp | grep :8080
tcp        0      0 127.0.0.1:8080          0.0.0.0:*               LISTEN      5879/ng

and I've completely disabled the firewall through

sudo ufw disable

restarted my laptop- still connection refused.

(I know it's not recommended but I really want figure things out and this became quite frustrating after a few hours).

On top of that I've tried ports other than 8080 (the default angular's 4200 for example).

Oh yeah, and I've tried to forward all the requests from ports 4000 to 9000 to my laptop (router configuration). Same result- connection refused ;)

What do i do? How do I debug this problem?

server connection 16.04 connection-sharing
Martin Hope
Richard Quint
Asked: 2018-05-04 09:08:12 +0800 CST
  • 14

After upgrading non-essential PCs to 18.04, while keeping my primary PC on 17.10, I'm running into a minor problem with networking and Nautilus in 18.04.

When I select Other Locations in the Nautilus sidebar, I expect to see the other machines on my network plus my Windows network. They are all there on machines running 17.10, but don't appear in 18.04. Also in 18.04 although there is an icon for the Windows network, clicking on it doesn't bring up the existing Workgroups as it does in 17.10.

My /etc/samba/smb.conf files are identical on all machines. I can access the shares from the 18.04 machines by running:

nautilus smb://<ip address>

in a terminal, which is why I suspect it has something to do with Nautilus rather than Samba. The Nautilus version on the 17.10 machines is 3.26.0, on the 18.04 machines is 3.26.3.

nautilus networking samba 18.04 connection-sharing
Martin Hope
nonoitall
Asked: 2018-04-24 22:15:10 +0800 CST
  • 4

I have Ubuntu (Armbian) running on an Orange Pi, and I'm using NetworkManager's internet connection sharing to share a wifi connection with an attached wired ethernet device. (The "wired connection" in NetworkManager has its IPv4 configured to Shared.) This works fine for basic internet sharing, but the wifi network I'm connected to has IPv6 enabled, and I'd like to pass that connectivity along to the wired device. How can I do that?

networking ipv6 network-manager internet connection-sharing
Martin Hope
Speedysnail6
Asked: 2014-03-17 17:58:45 +0800 CST
  • 4

I have followed Luis Alvarado's post on Sharing Connection to other PCs (Via Wired Ethernet) up until the "Client PC" part and am now sharing my laptop's internet connection with my Desktop server with an ethernet cable.

However, only my laptop can see the server (at 10.42.0.50), no other machines on the network have access to it. How can I make my server visible to the entire network?

IFCONFIG for client laptop:

eth0      Link encap:Ethernet  HWaddr 88:51:fb:fc:53:83  
          inet addr:10.42.0.1  Bcast:10.42.0.255  Mask:255.255.255.0
          inet6 addr: fe80::8a51:fbff:fefc:5383/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:45824 errors:0 dropped:0 overruns:0 frame:0
          TX packets:79374 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3211077 (3.2 MB)  TX bytes:119560393 (119.5 MB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:48417 errors:0 dropped:0 overruns:0 frame:0
          TX packets:48417 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:20154679 (20.1 MB)  TX bytes:20154679 (20.1 MB)

virbr0    Link encap:Ethernet  HWaddr 26:61:43:c4:5a:eb  
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          UP BROADCAST 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:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  HWaddr 60:36:dd:05:21:de  
          inet addr:192.168.1.4  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::6236:ddff:fe05:21de/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1221932 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1361697 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:480592551 (480.5 MB)  TX bytes:1308414648 (1.3 GB)

IFCONFIG for server: 

eth0      Link encap:Ethernet  HWaddr 00:16:76:90:b6:87  
          inet addr:10.42.0.50  Bcast:10.42.0.255  Mask:255.255.255.0
          inet6 addr: fe80::216:76ff:fe90:b687/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:23833 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13747 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:35930553 (35.9 MB)  TX bytes:971695 (971.6 KB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  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:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
connection-sharing