I have a Raspberry pi Device I want to use the (eth0) ethernet port/Cable to connect to a local network with ip range from 192.168.x.x. And i have a 4G usb dongle which connects to the internet on the eth1 interface. Dongles default Ip is 192.168.1.1(not sure this has anything to do with the problem) and reconfigures to the ip connecting to internet.
current setting - eth0 ip - 192.168.200.200 netmask 255.255.255.0 - eth1 ip - 10.228.171.93 netmask 255.255.255.252
The issue arises when i try to change the netmask of eth0 to 255.255.0.0 to connect to the local network. once i change it, access to internet on the device stops and i am not able to ping to google.com or its ip address.
Required setting - eth0 ip - 192.168.200.200 netmask 255.255.0.0 - eth1 ip - 10.228.171.93 netmask 255.255.255.252
I searched similar issues and tried out a few steps but none of it seems to work. resolv.conf has the following IP.
cat /etc/resolv.conf # Generated by resolvconf nameserver 192.168.1.1
/etc/network/interfaces file is as below
cat /etc/network/interfaces # interfaces(5) file used by ifup(8) and ifdown(8) # Please note that this file is written to be used with dhcpcd # For static IP, consult /etc/dhcpcd.conf and 'man dhcpcd.conf' # Include files from /etc/network/interfaces.d: source-directory /etc/network/interfaces.d # auto lo # iface lo inet loopback auto eth0 allow-hotplug eth0 iface eth0 inet static address 192.168.200.200 netmask 255.255.0.0 # gateway 192.168.230.230 # auto eth1 # allow-hotplug eth1 #iface eth1 inet dhcp
/etc/dhcpcd.conf file is as below
cat /etc/dhcpcd.conf # A sample configuration for dhcpcd. # See dhcpcd.conf(5) for details. # Allow users of this group to interact with dhcpcd via the control socket. #controlgroup wheel # Inform the DHCP server of our hostname for DDNS. hostname # Use the hardware address of the interface for the Client ID. clientid # or # Use the same DUID + IAID as set in DHCPv6 for DHCPv4 ClientID as per RFC4361. # Some non-RFC compliant DHCP servers do not reply with this set. # In this case, comment out duid and enable clientid above. #duid # Persist interface configuration when dhcpcd exits. persistent # Rapid commit support. # Safe to enable by default because it requires the equivalent option set # on the server to actually work. option rapid_commit # A list of options to request from the DHCP server. option domain_name_servers, domain_name, domain_search, host_name option classless_static_routes # Most distributions have NTP support. option ntp_servers # Respect the network MTU. This is applied to DHCP routes. option interface_mtu # A ServerID is required by RFC2131. require dhcp_server_identifier # Generate Stable Private IPv6 Addresses instead of hardware based ones slaac private # Example static IP configuration: interface eth0 static ip_address=192.168.200.200/24 # static ip6_address=fd51:42f8:caae:d92e::ff/64 # static routers=192.168.8.1 # static domain_name_servers=192.168.8.1 18.104.22.168 # It is possible to fall back to a static IP if DHCP fails: # define static profile # profile static_eth0 static ip_address=192.168.200.200/24 static netmask=255.255.0.0 # static routers=192.168.1.1 # static domain_name_servers=192.168.1.1 # fallback to static profile on eth0 #interface eth0 #fallback static_eth0
I need both the network interface to work
through eth0 i should be able to ping 192.168.x.x through eth1 i should be able to ping google.com