Hi All, I have 2 NICS in this system. CentOS 6.4 eth0 is the virtual IP from PFSense mapping connected to the router, works fine. eth1 is a second NIC that I have assigned a private IP to and connected it to a switch on the private network. I have many other private devices, so I know this setup works. When I connect the cable to the switch and bring up eth1 the system basically stops taking requests. I can no longer SSH in, Websites stop responding, etc. If I walk over to the server and take down eth1, everything works fine. Here is eth0: DEVICE=eth0 HWADDR=00:1b:21:cd:80:bf TYPE=Ethernet UUID=68a95912-3915-4b1a-9080-eb2017330153 ONBOOT=yes NM_CONTROLLED=yes BOOTPROTO=none IPADDR=192.168.1.27 NETMASK=255.255.255.0 DNS2=8.8.4.4 GATEWAY=192.168.1.1 DNS1=8.8.8.8 IPV6INIT=no USERCTL=no Here is eth1: DEVICE=eth1 HWADDR=00:0a:cd:17:07:7e TYPE=Ethernet UUID=b3851363-ae9e-4066-8993-caed07b9945b ONBOOT=no NM_CONTROLLED=yes BOOTPROTO=none IPADDR=10.0.254.11 NETMASK=255.255.255.0 GATEWAY=10.0.254.1 DNS1=8.8.8.8 DNS2=8.8.4.4 IPV6INIT=no USERCTL=no I have never experienced this before. Also, when I check system-config-network-tui, some .bak, which I made, but deleted the files from the file system when I was trying a few things. But how do I get rid of them? I attached a screenshot Jason
On 04/16/2013 01:37 PM, Jason T. Slack-Moehrle wrote:> Hi All, > > I have 2 NICS in this system. CentOS 6.4 > > eth0 is the virtual IP from PFSense mapping connected to the router, works > fine. > > eth1 is a second NIC that I have assigned a private IP to and connected it > to a switch on the private network. I have many other private devices, so I > know this setup works. > > When I connect the cable to the switch and bring up eth1 the system > basically stops taking requests. I can no longer SSH in, Websites stop > responding, etc. If I walk over to the server and take down eth1, > everything works fine. > > Here is eth0: > DEVICE=eth0 > HWADDR=00:1b:21:cd:80:bf > TYPE=Ethernet > UUID=68a95912-3915-4b1a-9080-eb2017330153 > ONBOOT=yes > NM_CONTROLLED=yes > BOOTPROTO=none > IPADDR=192.168.1.27 > NETMASK=255.255.255.0 > DNS2=8.8.4.4 > GATEWAY=192.168.1.1 > DNS1=8.8.8.8 > IPV6INIT=no > USERCTL=no > > Here is eth1: > DEVICE=eth1 > HWADDR=00:0a:cd:17:07:7e > TYPE=Ethernet > UUID=b3851363-ae9e-4066-8993-caed07b9945b > ONBOOT=no > NM_CONTROLLED=yes > BOOTPROTO=none > IPADDR=10.0.254.11 > NETMASK=255.255.255.0 > GATEWAY=10.0.254.1 > DNS1=8.8.8.8 > DNS2=8.8.4.4 > IPV6INIT=no > USERCTL=no > > I have never experienced this before.Remove the GATEWAY line from eth1, unless you have another router (with its own access to the Internet) at 10.0.254.1. If eth0 points at your upstream, then this is unlikely. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 555 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20130416/48a5eb50/attachment.sig>
I do have another gateway at 10.0.254.1, it is a Linksys router that all the provate stuff plugs into, and that Linksys plugs directly into our modem. On Tue, Apr 16, 2013 at 10:42 AM, Michael Mol <mikemol at gmail.com> wrote:> On 04/16/2013 01:37 PM, Jason T. Slack-Moehrle wrote: > > Hi All, > > > > I have 2 NICS in this system. CentOS 6.4 > > > > eth0 is the virtual IP from PFSense mapping connected to the router, > works > > fine. > > > > eth1 is a second NIC that I have assigned a private IP to and connected > it > > to a switch on the private network. I have many other private devices, > so I > > know this setup works. > > > > When I connect the cable to the switch and bring up eth1 the system > > basically stops taking requests. I can no longer SSH in, Websites stop > > responding, etc. If I walk over to the server and take down eth1, > > everything works fine. > > > > Here is eth0: > > DEVICE=eth0 > > HWADDR=00:1b:21:cd:80:bf > > TYPE=Ethernet > > UUID=68a95912-3915-4b1a-9080-eb2017330153 > > ONBOOT=yes > > NM_CONTROLLED=yes > > BOOTPROTO=none > > IPADDR=192.168.1.27 > > NETMASK=255.255.255.0 > > DNS2=8.8.4.4 > > GATEWAY=192.168.1.1 > > DNS1=8.8.8.8 > > IPV6INIT=no > > USERCTL=no > > > > Here is eth1: > > DEVICE=eth1 > > HWADDR=00:0a:cd:17:07:7e > > TYPE=Ethernet > > UUID=b3851363-ae9e-4066-8993-caed07b9945b > > ONBOOT=no > > NM_CONTROLLED=yes > > BOOTPROTO=none > > IPADDR=10.0.254.11 > > NETMASK=255.255.255.0 > > GATEWAY=10.0.254.1 > > DNS1=8.8.8.8 > > DNS2=8.8.4.4 > > IPV6INIT=no > > USERCTL=no > > > > I have never experienced this before. > > Remove the GATEWAY line from eth1, unless you have another router (with > its own access to the Internet) at 10.0.254.1. If eth0 points at your > upstream, then this is unlikely. > > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > >
On 4/16/2013 11:05 AM, Jason T. Slack-Moehrle wrote:> I do have another gateway at 10.0.254.1, it is a Linksys router that all > the provate stuff plugs into, and that Linksys plugs directly into our > modem.multiple gateways is problematic. there should be only one default route to 0.0.0.0/0 so you have a pfSense firewall AND a linksys soho router both connected to the internet? sounds messy. -- john r pierce 37N 122W somewhere on the middle of the left coast
Hi John,> I do have another gateway at 10.0.254.1, it is a Linksys router that all> > the provate stuff plugs into, and that Linksys plugs directly into our > > modem. > > multiple gateways is problematic. there should be only one default > route to 0.0.0.0/0 > > > so you have a pfSense firewall AND a linksys soho router both connected > to the internet? sounds messy. >Yes, indeed. We have a pfsense box with servers behind it connected to our modem as well as a router connected with private stuff behind it. We do need to move the private stuff behind the pfsense box as well. It is on the list. Jason