I have a freedompop Ubee stick that I would like to connect to my beaglebone black (running angstrom with 3.2.0-54-generic kernel). After solving some issues with hotswapping (it's not possible apparently), I am seeing the the interface in using ifconfig. But when I try bringing it up nothing happens:
root#beaglebone:~# ifconfig eth1 up
root#beaglebone:~# udhcpc eth1
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending discover...
Something also strange is that the interface initially has an address:
root#beaglebone:~# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:1D:88:53:2F:52
inet addr:192.168.14.2 Bcast:192.168.14.255 Mask:255.255.255.0
inet6 addr: fe80::21d:88ff:fe53:2f52/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:22 errors:0 dropped:0 overruns:0 frame:0
TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2542 (2.4 KiB) TX bytes:9062 (8.8 KiB)
But a few moments ( < 1 minute) later, if I run the same command, eth1 no longer has an address, bcast, etc:
root#beaglebone:~# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:1D:88:53:2F:52
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25 errors:0 dropped:0 overruns:0 frame:0
TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2730 (2.6 KiB) TX bytes:9240 (9.0 KiB)
Under no circumstance (before or after address is stripped in ifconfig) can I ever ping something.
I have tried re-assigning the address, mask, etc, but nothing helps. Bring the interface up or down does not help. I tried manually creating an interfaces file and that didn't help either.
To solve this problem, I had to:
Add an inet dhcp interface in /etc/network/interfaces:
iface eth1 inet dhcp
Add the freedompop as a nameserver in resolve.conf
nameserver 192.168.14.1
Bring up the interface
ifup eth1
Related
I have hosted Microstack, in my Macbook. Everything works fine, I am able to boot instances from the Microstack.
But on the Xenial Server instance I have booted from my Microstack has no internet. I am planning to install docker and create containers.
ubuntu#xone:~$ ifconfig
ens3 Link encap:Ethernet HWaddr fa:16:3e:b7:14:e0
inet addr:94.23.76.87 Bcast:94.23.76.255 Mask:255.255.255.0
inet6 addr: fe80::f816:3eff:feb7:14e0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1450 Metric:1
RX packets:169 errors:0 dropped:0 overruns:0 frame:0
TX packets:117 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:15821 (15.8 KB) TX bytes:16228 (16.2 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:14708 errors:0 dropped:0 overruns:0 frame:0
TX packets:14708 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:1091208 (1.0 MB) TX bytes:1091208 (1.0 MB)
When I run ifconfig in my Xenial Server instance, this is the result I'm getting.
I am able to both ping router_gateway and router_interface from my xone(Xenial instance). Both 10.20.20.82 and 192.168.222.1.
But I am unable to ping 8.8.8.8 from xone instance. How best I can resolve this issue?
Thanks to https://bugs.launchpad.net/microstack/+bug/1812415.
I was able to resolve this issue by running the following commands in the host (OpenStack) instance:
sudo iptables -t nat -A POSTROUTING -s 10.20.20.1/24 ! -d 10.20.20.1/24 -j MASQUERADE
sudo sysctl net.ipv4.ip_forward=1
I'm developing a WordPress site with Vagrant box "vccw-team/xenial64", which can be found at vccw.cc. The website was slow with waiting times that average around 5 seconds, did some googling and many people where pointing at Vagrants synced folder wich is slow in combination with Virtualbox. The solution: nfs. Nfs doesn't exist on Windows so that gave rise to the Vagrant plugin winnfsd.
I installed the plugin and changed the Vagrantfile as such:
config.vm.network :private_network, ip: "192.168.33.10"
config.vm.synced_folder _conf['synced_folder'],
_conf['document_root'], :create => "true", :mount_options => ['dmode=755', 'fmode=644'], type: "nfs"
On vagrant up, I receive this message:
==> vccw.dev: Mounting NFS shared folders...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -o vers=3,udp,dmode=755,fmode=644 192.168.33.1:/D/_projects/Vagrant/vccw/wordpress /var/www/html
Stdout from the command:
Stderr from the command:
mount.nfs: an incorrect mount option was specified
I guess the portion 192.168.33.1:/D/_projects/Vagrant/vccw/wordpress might be wrong because D/_projects/Vagrant/vccw/wordpress exist on the host and not on the guest (192.168.33.1).
Other people managed to get the plugin working. Does anyone know what I'm doing wrong?
Versions:
Vagrant: 2.0.0
vagrant-winnfsd: 1.3.1
Virtualbox: 5.1.26 r117224 (Qt5.6.2)
I enabled DHCP in Vagrantfile like so:
config.vm.network :private_network, ip: "192.168.33.11", type: "dhcp"
But that resulted in the error:
NFS requires a host-only network to be created. Please add a host-only network to the machine (with either DHCP or a static IP) for NFS to work
Then I read in another question on StackOverflow that one can configure a host-only network by using the code below in the Vagrantfile:
config.vm.network :private_network, ip: "192.168.33.11"
config.vm.network :public_network, ip: "192.168.44.12"
config.vm.synced_folder _conf['synced_folder'],
_conf['document_root'], type: "nfs"
I think 192.168.44.0 255.255.255.0 is now the hosted network, derived from ip: "192.168.44.12". It work's now and my WordPress site is faster with a loading time that averages around 3 seconds. I appreciate the improvement but I'll be hawking for other tweaks.
Extra info, the output of ifconfig in the guest:
vagrant#vccw:~$ ifconfig
enp0s3 Link encap:Ethernet HWaddr 08:00:27:a8:df:8b
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fea8:df8b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1156 errors:0 dropped:0 overruns:0 frame:0
TX packets:788 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:277602 (277.6 KB) TX bytes:97056 (97.0 KB)
enp0s8 Link encap:Ethernet HWaddr 08:00:27:da:65:a0
inet addr:192.168.33.11 Bcast:192.168.33.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:feda:65a0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12461 errors:0 dropped:0 overruns:0 frame:0
TX packets:7004 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10059912 (10.0 MB) TX bytes:2671763 (2.6 MB)
enp0s9 Link encap:Ethernet HWaddr 08:00:27:62:47:ec
inet addr:192.168.44.12 Bcast:192.168.44.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe62:47ec/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:204 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:18654 (18.6 KB) TX bytes:648 (648.0 B)
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:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:1658 (1.6 KB) TX bytes:1658 (1.6 KB)
I created a vagrant environment where there is 2 VM's in the private network , i need this because i want them to be able to communicate with each other like application server and database server.So here is my vagrantfile:
Vagrant.configure("2") do |config|
config.vm.define "mac1" do |mac1|
mac1.vm.box = "kaorimatz/centos-6.8-x86_64"
mac1.vm.network :private_network, ip: "192.168.56.101"
mac1.vm.network "forwarded_port", guest: 80, host: 8080
end
config.vm.define "mac2" do |mac2|
mac2.vm.box = "fully-functional"
mac2.vm.network :private_network, ip: "192.168.56.102"
mac2.vm.network "forwarded_port", guest: 80, host: 8081
mac2.vm.synced_folder "./piwik", "/var/www/html"
end
end
now lets say i want to reach only mac2 VM via browser.but i am putting the url like http://localhost:8081 but it says site is not reachable.In that machine when i run the command ifconfig here is the result:
eth0 Link encap:Ethernet HWaddr 08:00:27:AF:D5:5C
inet addr:10.0.2.15 Bcast:10.0.2.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:feaf:d55c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2779 errors:0 dropped:0 overruns:0 frame:0
TX packets:1504 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:221177 (215.9 KiB) TX bytes:165269 (161.3 KiB)
eth1 Link encap:Ethernet HWaddr 08:00:27:4E:48:A7
inet addr:192.168.56.102 Bcast:192.168.56.255 Mask:255.255.255.0
inet6 addr: fe80::a00:27ff:fe4e:48a7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1114 (1.0 KiB) TX bytes:2408 (2.3 KiB)
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)
I also added that lines to apache conf :
<VirtualHost *:80>
ServerName mac2.com
DocumentRoot /var/www/html
</VirtualHost>
And i can also listen to the port 8081 like telnet localhost 8081
but i couldnt reach the webserver by any means however i can try.Pls help thank you in advance.
I had the same thing with two vagrant instances using the "kaorimatz/centos-6.8-x86_64" box (even after being fully updated during provisioning):
When I used a different box, I was then able to forward ports. The only change I made was with the Vagrantfile config.vm.box value. I suspect it's a "kaorimatz/centos-6.8-x86_64" issue but I'm not going to investigate the kaorimatz box as the alternative box worked.
(I used the "bmcgonigle/centos68" box.)
#config.vm.box = "kaorimatz/centos-6.8-x86_64"
config.vm.box = "bmcgonigle/centos68"
I had tried the same thing with the private network but had no success with it. I got suspicious of the kaorimatz box when I noticed that I had other vagrant dev configs that forwarded ports with no issues. Best of luck!
I am trying to deploy my Shiny App on a Virtual Machine (CentOS 6.7). I have configured a bridged connection (I think I did it correctly) for the Virtual Machine, and I have my Static IP Address for the web application. The sample application works on localhost:3838.
I am behind a corporate proxy, so I am using a proxy to connect to the internet. The proxy is set in http_proxy. I can also connect to the internet successfully on the Virtual Machine.
When I try to access <my_VM_static_IP_Address>:3838 the website does not connect.
I can ping both the host IP address and the guest (static) IP address successfully from another PC that is connected to the network.
br0 Link encap:Ethernet HWaddr 70:F3:95:03:B5:CC
inet addr:<My Static IP Address> Bcast:<my_broadcast_address> Mask:255.255.254.0
inet6 addr: fe80::72f3:95ff:fe03:b5cc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:69753 errors:0 dropped:0 overruns:0 frame:0
TX packets:9698 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:34003791 (32.4 MiB) TX bytes:843817 (824.0 KiB)
eth0 Link encap:Ethernet HWaddr 70:F3:95:03:B5:CC
inet6 addr: fe80::72f3:95ff:fe03:b5cc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:130187 errors:0 dropped:0 overruns:0 frame:0
TX packets:9704 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:45704171 (43.5 MiB) TX bytes:845299 (825.4 KiB)
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:439 errors:0 dropped:0 overruns:0 frame:0
TX packets:439 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:814679 (795.5 KiB) TX bytes:814679 (795.5 KiB)
My host default gateway and subnet mask are the same on the VM Guest and the host.
Any support is greatly appreciated!
Investigate whether a firewall on the host prevents port 3838 from being accessible from the rest of the network. It seems like you have a Windows host, correct?
A quick and easy way to check is to telnet to that port on your guest OS's IP from another machine on the network. If the connection is refused with an error, you know something is blocking the port. A blank screen means an open port.
From some other machine on the network, telnet to your guest VM's IP on port 3838. A blocked port will cause telnet to quickly return an error. If the telnet command sits with a blank screen, you have an open port.
How do I print which packets are dropped by by the interface ???
I have an interface wherein RX packets are dropped , see below :
eth0 Link encap:Ethernet HWaddr DE:AD:BE:EF:42:46
inet addr:192.168.122.86 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::dcad:beff:feef:4246/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
**RX packets:10963521 errors:0 dropped:1006 overruns:0 frame:0**
TX packets:6221974 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3108701252 (2.8 GiB) TX bytes:3842229777 (3.5 GiB)
Interrupt:10 Base address:0xe000
In Windows you can enable dropped packets logging:
Step 1. Change Windows Firewall configuration:
auditpol.exe /set /SubCategory:"Filtering Platform Packet Drop" /failure:enable
Step 2. Restart firewall service
net stop MPSSVC
net start MPSSVC
More info on http://technet.microsoft.com/en-us/library/cc754714(v=ws.10).aspx.