[gentoo-user] Network problem
Hi, I have a problem with my ehternet connection and would be pleased if someone could help me: I emerged some things (don't ask me what exactly...) and am unable to ping anything now. The ip-address and co. are alright, I can just boot another operating system on my pc (sabayon or windows) and eth0 is working fine using the same configuration. Ifconfig eth0 gives me this: Link encap: UNSPEC HWaddr 44-4F-C0-00-14-31-AC-10-00-00-00-00-00-00-00-00 inet addr:192.168.0.45 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:72 (72.0 b) I'm pretty sure the Mac-Addr is too long.. that's weird, Also, when using Sabayon, the first line differs: "Link encap:ether" and the mac is correct I tried to change the mac with: ifconfig eth0 hw ether 10:20:30:40:50:60 but then, I get th following: SIOCSIFHWADDR: Invalid argument Very strange: I have two independend pcs and BOTH of them have the same problem meanwhile! Any ideas?
Re: [gentoo-user] Network problem
Hi, On Mon, 12 Feb 2007 09:54:42 +0100 "Roman Naumann" <[EMAIL PROTECTED]> wrote: > Ifconfig eth0 gives me this: > > Link encap: > > UNSPEC HWaddr 44-4F-C0-00-14-31-AC-10-00-00-00-00-00-00-00-00 > [...] > I'm pretty sure the Mac-Addr is too long.. that's weird, > Also, when using Sabayon, the first line differs: "Link encap:ether" > and the mac is correct > > I tried to change the mac with: > ifconfig eth0 hw ether 10:20:30:40:50:60 > but then, I get th following: > SIOCSIFHWADDR: Invalid argument eth0 doesn't seem to be what it has been anymore. You probably compiled a new kernel with some extra network drivers (USB devices? Firewire?). Looking at the "MAC" address above, I'd say it's something designated for a peer-to-peer connection. use "ifconfig -a" to find your real network interface. If it's not shown there (under different name, of course), you're probably missing the right modules. You might want to use udev to give your interfaces a persistent naming in the future, that will save you these troubles. -hwh -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Network problem
On 2/12/07, Hans-Werner Hilse <[EMAIL PROTECTED]> wrote: Hi, On Mon, 12 Feb 2007 09:54:42 +0100 "Roman Naumann" <[EMAIL PROTECTED]> wrote: > Ifconfig eth0 gives me this: > > Link encap: > > UNSPEC HWaddr 44-4F-C0-00-14-31-AC-10-00-00-00-00-00-00-00-00 > [...] > I'm pretty sure the Mac-Addr is too long.. that's weird, > Also, when using Sabayon, the first line differs: "Link encap:ether" > and the mac is correct > > I tried to change the mac with: > ifconfig eth0 hw ether 10:20:30:40:50:60 > but then, I get th following: > SIOCSIFHWADDR: Invalid argument eth0 doesn't seem to be what it has been anymore. You probably compiled a new kernel with some extra network drivers (USB devices? Firewire?). Looking at the "MAC" address above, I'd say it's something designated for a peer-to-peer connection. use "ifconfig -a" to find your real network interface. If it's not shown there (under different name, of course), you're probably missing the right modules. You might want to use udev to give your interfaces a persistent naming in the future, that will save you these troubles. -hwh -- gentoo-user@gentoo.org mailing list thanks for your quick answer. yes, there is a new interface named eth1 and it works. (so it seems that this problem was caused by replacing coldplug with udev)
Re: [gentoo-user] Network problem
On 2/12/07, Roman Naumann <[EMAIL PROTECTED]> wrote: On 2/12/07, Hans-Werner Hilse <[EMAIL PROTECTED]> wrote: > Hi, > > On Mon, 12 Feb 2007 09:54:42 +0100 "Roman Naumann" > <[EMAIL PROTECTED]> wrote: > > > Ifconfig eth0 gives me this: > > > > Link encap: > > > > UNSPEC HWaddr 44-4F-C0-00-14-31-AC-10-00-00-00-00-00-00-00-00 > > [...] > > I'm pretty sure the Mac-Addr is too long.. that's weird, > > Also, when using Sabayon, the first line differs: "Link encap:ether" > > and the mac is correct > > > > I tried to change the mac with: > > ifconfig eth0 hw ether 10:20:30:40:50:60 > > but then, I get th following: > > SIOCSIFHWADDR: Invalid argument > > eth0 doesn't seem to be what it has been anymore. You probably compiled > a new kernel with some extra network drivers (USB devices? Firewire?). > Looking at the "MAC" address above, I'd say it's something designated > for a peer-to-peer connection. > > use "ifconfig -a" to find your real network interface. If it's not > shown there (under different name, of course), you're probably missing > the right modules. You might want to use udev to give your interfaces a > persistent naming in the future, that will save you these troubles. > > -hwh > > > -- > gentoo-user@gentoo.org mailing list > > thanks for your quick answer. yes, there is a new interface named eth1 and it works. (so it seems that this problem was caused by replacing coldplug with udev) In fact, you may have a firewire connection, and that is being recognized as eth0, try adding "nofirewire" to your kernel boot line, and check if eth0 will be your network card again. Also, there was a similar problem on the list a few days ago and the OP of that thread asked for UDEV rules to set names to its interfaces, check the archives. -- Daniel da Veiga Computer Operator - RS - Brazil -BEGIN GEEK CODE BLOCK- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ --END GEEK CODE BLOCK-- -- gentoo-user@gentoo.org mailing list
[gentoo-user] network problem :: new install
Hi, I have a new notebook and trying to setup my Gentoo. I've followed the Gentoo handbook and setup the network as DHCP. But during the boot I have error like this: eth0 does not exist I have to missed something but I have no idea :-( Could someone push me ??? Thanks a lot. Pat -- gentoo-user@gentoo.org mailing list
[gentoo-user] Network problem with linux server
Hi All. This problem is not strictly related to gentoo, however I'm sure someone here will be able to help me in some way: sorry if I bother you! I'm having a really strange problem: for some reason, everytime I reboot my server, the default gateway gets attached to the 'lo' interface, even if I correctly attached it to the eth0 device. I fixed the problem editing the /etc/sysconfig/network file and adding GATEWAY=195.75.145.1 GATEWAYDEV=eth0 however I'm not sure this is the solution: I already configured the default gateway only in the ifcfg-eth0 file! After this, I have an even worse problem: doing an ssh 195.75.145.1, I get an answer from my own server like if it was a loopback address ! Here is the output of ifconfig: eth0 Link encap:Ethernet HWaddr 5C:F3:FC:55:63:42 inet addr:195.75.145.122 Bcast:195.75.145.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4281 errors:0 dropped:0 overruns:0 frame:0 TX packets:25 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4934949 (4.7 MiB) TX bytes:2133 (2.0 KiB) Interrupt:28 Memory:9200-92012800 eth2 Link encap:Ethernet HWaddr 00:1B:21:8E:0A:86 inet addr:192.168.19.95 Bcast:192.168.19.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2049 errors:0 dropped:0 overruns:0 frame:0 TX packets:917 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:236160 (230.6 KiB) TX bytes:99635 (97.2 KiB) Memory:97d8-97e0 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:56 errors:0 dropped:0 overruns:0 frame:0 TX packets:56 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:7714 (7.5 KiB) TX bytes:7714 (7.5 KiB) lo:0 Link encap:Local Loopback inet addr:195.75.145.120 Mask:255.255.255.0 UP LOOPBACK RUNNING MTU:16436 Metric:1 here is the output of ip route 192.168.19.0/24 dev eth2 proto kernel scope link src 192.168.19.95 195.75.145.0/24 dev eth0 proto kernel scope link src 195.75.145.122 169.254.0.0/16 dev eth0 scope link metric 1002 169.254.0.0/16 dev eth2 scope link metric 1004 default via 195.75.145.1 dev eth0 Please!! Do you have any advice? Thanks, Massimiliano
Re: [gentoo-user] network problem :: new install
On Dec 8, 2005, at 11:14 pm, pat wrote: I have a new notebook and trying to setup my Gentoo. I've followed the Gentoo handbook and setup the network as DHCP. But during the boot I have error like this: eth0 does not exist Sounds like the driver for your network card isn't loaded. If the NIC works with the liveCD but not with the kernel you compiled then you may just be able to `modprobe` it in, otherwise you may need to recompile. Try running `lsmod` from the LiveCD, and maybe post the output of `lspci` here. Stroller. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] network problem :: new install
Stroller wrote: > > On Dec 8, 2005, at 11:14 pm, pat wrote: > >> >> I have a new notebook and trying to setup my Gentoo. I've followed >> the Gentoo >> handbook and setup the network as DHCP. >> >> But during the boot I have error like this: >> eth0 does not exist > > > Sounds like the driver for your network card isn't loaded. If the NIC > works with the liveCD but not with the kernel you compiled then you > may just be able to `modprobe` it in, otherwise you may need to > recompile. Try running `lsmod` from the LiveCD, and maybe post the > output of `lspci` here. > > Stroller. > I did this once. It lists the modules that are available but not loaded. modprobe -l . That may help. Dale :-) -- To err is human, I'm most certainly human. I have four rigs: 1: Home built; Abit NF7 ver 2.0 w/ AMD 2500+ CPU, 1GB of ram and right now two 80GB hard drives. 2: Home built; Iwill KK266-R w/ AMD 1GHz CPU, 256MBs of ram and a 4GB drive. 3: Home built; Gigabyte GA-71XE4 w/ 800MHz CPU, 128MBs of ram and a 2.5GB drive. 4: Compaq Proliant 6000 Server w/ Quad 200MHz CPUs, 128MBs of ram and a 4.3GB SCSI drive. All run Gentoo, all run folding. #1 is my desktop, 2, 3, and 4 are set up as servers. -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] Network problem with linux server
On Mon, November 7, 2011 12:13 pm, Massimiliano Ziccardi wrote: > Hi All. > > This problem is not strictly related to gentoo, however I'm sure someone > here will be able to help me in some way: sorry if I bother you! > > I'm having a really strange problem: for some reason, everytime I reboot > my > server, the default gateway gets attached to the 'lo' interface, even if I > correctly attached it to the eth0 device. > > I fixed the problem editing the /etc/sysconfig/network file and adding > > GATEWAY=195.75.145.1 > GATEWAYDEV=eth0 > > however I'm not sure this is the solution: I already configured the > default > gateway only in the ifcfg-eth0 file! Which Linux distribution are you using? Gentoo does not use those files. Try editing the /etc/conf.d/net file to match your network settings. -- Joost
Re: [gentoo-user] Network problem with linux server
You are totally right: I'm not using gentoo, but I'm serching for help and gentoo's mailing list is the most technical one: I'm truly sorry for the OT. Just some hint about what could be wrong or some command to launch to understand what's wrong would be great: I'm getting crazy!! My distribution is CENTOS but couldn't get much help there, so I tried here. Thanks a lot! Massimiliano On Mon, Nov 7, 2011 at 12:24, J. Roeleveld wrote: > On Mon, November 7, 2011 12:13 pm, Massimiliano Ziccardi wrote: > > Hi All. > > > > This problem is not strictly related to gentoo, however I'm sure someone > > here will be able to help me in some way: sorry if I bother you! > > > > I'm having a really strange problem: for some reason, everytime I reboot > > my > > server, the default gateway gets attached to the 'lo' interface, even if > I > > correctly attached it to the eth0 device. > > > > I fixed the problem editing the /etc/sysconfig/network file and adding > > > > GATEWAY=195.75.145.1 > > GATEWAYDEV=eth0 > > > > however I'm not sure this is the solution: I already configured the > > default > > gateway only in the ifcfg-eth0 file! > > Which Linux distribution are you using? > Gentoo does not use those files. > > Try editing the /etc/conf.d/net file to match your network settings. > > -- > Joost > > >
Re: [gentoo-user] Network problem with linux server
Am 07/11/2011 12:13, schrieb Massimiliano Ziccardi: Hi All. [SNIP] Please!! Do you have any advice? yes. read and follow the manuals provided by your distribution (your description doesn't sound gentoo-ish, but EVERY distro should have this in their documentation). Thanks, Massimiliano
Re: [gentoo-user] Network problem with linux server
Hi, Am Montag, 7. November 2011, 12:13:58 schrieb Massimiliano Ziccardi: > Hi All. > > This problem is not strictly related to gentoo, however I'm sure someone > here will be able to help me in some way: sorry if I bother you! have a look at: http://www.centos.org/docs/5/html/5.1/Deployment_Guide/s1-networkscripts- static-routes.html Best, Michael
Re: [gentoo-user] Network problem with linux server
Already done. I asked here because I hoped someone would be able to give me some hint about why with the routes I sent in the previous e-mail pinging the default gateway it pings itself (I verified that pinging every server with address 195.75.145.xxx pings the server itself as if it was a loopback address). Thanks, Massimiliano On Mon, Nov 7, 2011 at 12:52, Michael Schreckenbauer wrote: > Hi, > > Am Montag, 7. November 2011, 12:13:58 schrieb Massimiliano Ziccardi: > > Hi All. > > > > This problem is not strictly related to gentoo, however I'm sure someone > > here will be able to help me in some way: sorry if I bother you! > > have a look at: > http://www.centos.org/docs/5/html/5.1/Deployment_Guide/s1-networkscripts- > static-routes.html > > Best, > Michael > > >
Re: [gentoo-user] Network problem with linux server
Please do NOT top-post. On Mon, November 7, 2011 12:34 pm, Massimiliano Ziccardi wrote: > You are totally right: I'm not using gentoo, but I'm serching for help and > gentoo's mailing list is the most technical one: I'm truly sorry for the > OT. If asking questions on how to do things on non-Gentoo installations, please always mention the distribution in your email. > > Just some hint about what could be wrong or some command to launch to > understand what's wrong would be great: I'm getting crazy!! > > My distribution is CENTOS but couldn't get much help there, so I tried > here. What about the documentation? I have noticed that most binary distros require the use of their graphical admin tools to make any changes to the configuration. -- Joost
Re: [gentoo-user] Network problem with linux server
> > Please do NOT top-post Sorry. If asking questions on how to do things on non-Gentoo installations, > please always mention the distribution in your email. Ok, sorry again! What about the documentation? > I have noticed that most binary distros require the use of their graphical > admin tools to make any changes to the configuration. I read the documentation and tried to carefully follow it. Now I'm getting this strange behaviour and don't know what's happening. I tried both editing the config files and using the network config tool, but with no luck. I thought it was a routing problem, but as you can see, the routes I sent seems to be ok. However, I'm not a networking guru, so I don't know what to look else. Maybe the arp tables? Here is the arptables -L output: Chain IN (policy ACCEPT) target source-ipdestination-ip source-hw destination-hw hlen op hrdpro Chain OUT (policy ACCEPT) target source-ipdestination-ip source-hw destination-hw hlen op hrdpro Chain FORWARD (policy ACCEPT) target source-ipdestination-ip source-hw destination-hw hlen op hrdpro
Re: [gentoo-user] Network problem with linux server
On Mon, November 7, 2011 1:15 pm, Massimiliano Ziccardi wrote: > What about the documentation? >> I have noticed that most binary distros require the use of their >> graphical >> admin tools to make any changes to the configuration. > > > I read the documentation and tried to carefully follow it. Now I'm getting > this strange behaviour and don't know what's happening. > I tried both editing the config files and using the network config tool, > but with no luck. > > I thought it was a routing problem, but as you can see, the routes I sent > seems to be ok. The routes and ifconfig seems correct to me. How is the router configured? I specifically mean, does it have any firewall configurations redirecting SSH-traffic to your machine? -- Joost
Re: [gentoo-user] Network problem with linux server
Hi, Am Montag, 7. November 2011, 13:15:53 schrieb Massimiliano Ziccardi: > I thought it was a routing problem, but as you can see, the routes I sent > seems to be ok. you have those link-local entries in your routes (169.254.0.0/16), Try adding NOZEROCONF= yes to /etc/sysconfig/network Best, Michael
Re: [gentoo-user] Network problem with linux server
Hi All. >The routes and ifconfig seems correct to me. >How is the router configured? >I specifically mean, does it have any firewall configurations redirecting >SSH-traffic to your machine? I don't have access to the routers, however they are used for many other servers too. Moreover, I tried the ssh command because I wanted to be sure I was pinging the right servers (for some reason they can't ping me!) and I discovered that I was pinging myself. Moreover I'm trying to ping/ssh on servers that are on the same lan and the network technician (?!) assured me there is no firewall between my server and, for example, 195.75.145.33. Another strange thing I noticed is that : 1. 195.75.146.104 (that passes through a firewall!!) is able to ping my server 2. 195.75.145.33 (that is on the same net without firewall) is not able to ping my server I have the dubt something strange happens in the routers/switch, etc. However, since I have that strange behaviour on my machine (ping itself, etc.), thay says my server is bad configured. Moreover, 195.75.145.33 is able to ping many other servers on the same net but mine. Don't know what else to do... Regards, Massimiliano
Re: [gentoo-user] Network problem with linux server
> you have those link-local entries in your routes (169.254.0.0/16), Try > adding > NOZEROCONF= yes to /etc/sysconfig/network Already tried, but no luck... Thanks, Massimiliano
Re: [gentoo-user] Network problem with linux server
Am Montag, 7. November 2011, 13:47:49 schrieb Massimiliano Ziccardi: > > you have those link-local entries in your routes (169.254.0.0/16), Try > > adding > > NOZEROCONF= yes to /etc/sysconfig/network > > Already tried, but no luck... could you post the output of ip route with zeroconf disabled? > Thanks, > Massimiliano Best, Michael
Re: [gentoo-user] Network problem with linux server
> > could you post the output of > ip route > with zeroconf disabled? Here it is! 192.168.19.0/24 dev eth2 proto kernel scope link src 192.168.19.95 195.75.145.0/24 dev eth0 proto kernel scope link src 195.75.145.122 default via 195.75.145.1 dev eth0 Thanks, Massimiliano
Re: [gentoo-user] Network problem with linux server
Am Montag, 7. November 2011, 14:15:39 schrieb Massimiliano Ziccardi: > > could you post the output of > > ip route > > with zeroconf disabled? > > Here it is! > > 192.168.19.0/24 dev eth2 proto kernel scope link src 192.168.19.95 > 195.75.145.0/24 dev eth0 proto kernel scope link src 195.75.145.122 > default via 195.75.145.1 dev eth0 seems to be a really tricky one... What does tracepath 195.75.145.33 give? > Thanks, > Massimiliano Best, Michael
Re: [gentoo-user] Network problem with linux server
> > seems to be a really tricky one... > What does > tracepath 195.75.145.33 > give? Here is the output: 1: 195.75.145.33 (195.75.145.33) 0.074ms pmtu 16436 1: 195.75.145.33 (195.75.145.33) 0.039ms reached 1: 195.75.145.33 (195.75.145.33) 0.028ms reached I tried shutting down localhost with: ifconfig lo down. Now I can't ping 195.75.145.33 anymore (as all the other 195.75.145.xx addresses). And now tracepath gives: 1: send failed Resume: pmtu 65535 So, for some reason, seems it always uses the 'lo' device... Any idea? Regards, Massimiliano
Re: [gentoo-user] Network problem with linux server
On Nov 7, 2011 8:38 PM, "Massimiliano Ziccardi" < massimiliano.zicca...@gmail.com> wrote: >> >> seems to be a really tricky one... >> What does >> tracepath 195.75.145.33 >> give? > > > Here is the output: > > 1: 195.75.145.33 (195.75.145.33) 0.074ms pmtu 16436 > 1: 195.75.145.33 (195.75.145.33) 0.039ms reached > 1: 195.75.145.33 (195.75.145.33) 0.028ms reached > > I tried shutting down localhost with: > > ifconfig lo down. > > Now I can't ping 195.75.145.33 anymore (as all the other 195.75.145.xx addresses). > > And now tracepath gives: > > 1: send failed > Resume: pmtu 65535 > > So, for some reason, seems it always uses the 'lo' device... > > Any idea? > I've been deploying multi-interface Linux gateways since 2008, so I'll try. Please post: - output of ip rule sh - output of ip route sh table $t, where $t is *all* table names/numbers you get from the first output ( "... lookup $t" ) Rgds,
Re: [gentoo-user] Network problem with linux server
Am Montag, 7. November 2011, 14:35:46 schrieb Massimiliano Ziccardi: > > seems to be a really tricky one... > > What does > > tracepath 195.75.145.33 > > give? > > Here is the output: > > 1: 195.75.145.33 (195.75.145.33) 0.074ms pmtu > 16436 > 1: 195.75.145.33 (195.75.145.33) 0.039ms reached > 1: 195.75.145.33 (195.75.145.33) 0.028ms reached > > I tried shutting down localhost with: > > ifconfig lo down. > > Now I can't ping 195.75.145.33 anymore (as all the other 195.75.145.xx > addresses). > > And now tracepath gives: > > 1: send failed > Resume: pmtu 65535 > > So, for some reason, seems it always uses the 'lo' device... > > Any idea? I noticed lo:0 is on the same net and has the same netmask as eth0. Where does lo:0 come from? Is it needed? I have no idea, if this is the problem or even related, just wondering. > Regards, > Massimiliano Best, Michael
Re: [gentoo-user] Network problem with linux server
> > I've been deploying multi-interface Linux gateways since 2008, so I'll try. > Please post: > - output of ip rule sh # ip rule sh 0: from all lookup local 32766: from all lookup main 32767: from all lookup default # ip route sh table 0 192.168.19.0/24 dev eth2 proto kernel scope link src 192.168.19.95 195.75.145.0/24 dev eth0 proto kernel scope link src 195.75.145.122 default via 195.75.145.1 dev lo scope link broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 local 195.75.145.122 dev eth0 table local proto kernel scope host src 195.75.145.122 broadcast 192.168.19.0 dev eth2 table local proto kernel scope link src 192.168.19.95 broadcast 195.75.145.255 dev eth0 table local proto kernel scope link src 195.75.145.122 broadcast 195.75.145.255 dev lo table local proto kernel scope link src 195.75.145.120 local 195.75.145.120 dev lo table local proto kernel scope host src 195.75.145.120 local 192.168.19.95 dev eth2 table local proto kernel scope host src 192.168.19.95 broadcast 192.168.19.255 dev eth2 table local proto kernel scope link src 192.168.19.95 broadcast 195.75.145.0 dev eth0 table local proto kernel scope link src 195.75.145.122 broadcast 195.75.145.0 dev lo table local proto kernel scope link src 195.75.145.120 broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1 local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 local 195.75.145.0/24 dev lo table local proto kernel scope host src 195.75.145.120 local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 # ip route sh table 32766 # ip route sh table 32767 Both 32766 and 32767 are empty Thanks very much! Regards, Massimiliano On Mon, Nov 7, 2011 at 14:59, Pandu Poluan wrote: > > On Nov 7, 2011 8:38 PM, "Massimiliano Ziccardi" < > massimiliano.zicca...@gmail.com> wrote: > >> > >> seems to be a really tricky one... > >> What does > >> tracepath 195.75.145.33 > >> give? > > > > > > Here is the output: > > > > 1: 195.75.145.33 (195.75.145.33) 0.074ms pmtu > 16436 > > 1: 195.75.145.33 (195.75.145.33) 0.039ms > reached > > 1: 195.75.145.33 (195.75.145.33) 0.028ms > reached > > > > I tried shutting down localhost with: > > > > ifconfig lo down. > > > > Now I can't ping 195.75.145.33 anymore (as all the other 195.75.145.xx > addresses). > > > > And now tracepath gives: > > > > 1: send failed > > Resume: pmtu 65535 > > > > So, for some reason, seems it always uses the 'lo' device... > > > > Any idea? > > > > I've been deploying multi-interface Linux gateways since 2008, so I'll try. > > Please post: > > - output of ip rule sh > - output of ip route sh table $t, where $t is *all* table names/numbers > you get from the first output ( "... lookup $t" ) > > Rgds, >
Re: [gentoo-user] Network problem with linux server
Our network admin told me to create a lo:0 to that address to create a VIP to be balanced by the network load balancer. That is why lo:0 is there... Thanks! Regards, Massimiliano Ziccardi On Mon, Nov 7, 2011 at 15:01, Michael Schreckenbauer wrote: > Am Montag, 7. November 2011, 14:35:46 schrieb Massimiliano Ziccardi: > > > seems to be a really tricky one... > > > What does > > > tracepath 195.75.145.33 > > > give? > > > > Here is the output: > > > > 1: 195.75.145.33 (195.75.145.33) 0.074ms pmtu > > 16436 > > 1: 195.75.145.33 (195.75.145.33) 0.039ms > reached > > 1: 195.75.145.33 (195.75.145.33) 0.028ms > reached > > > > I tried shutting down localhost with: > > > > ifconfig lo down. > > > > Now I can't ping 195.75.145.33 anymore (as all the other 195.75.145.xx > > addresses). > > > > And now tracepath gives: > > > > 1: send failed > > Resume: pmtu 65535 > > > > So, for some reason, seems it always uses the 'lo' device... > > > > Any idea? > > I noticed lo:0 is on the same net and has the same netmask as eth0. > Where does lo:0 come from? Is it needed? > I have no idea, if this is the problem or even related, just wondering. > > > Regards, > > Massimiliano > > Best, > Michael > > >
Re: [gentoo-user] Network problem with linux server
Sorry, I sent you the wrong output of ip route sh table 0. Follows the right one (sorry!) # ip route sh table 0 192.168.19.0/24 dev eth2 proto kernel scope link src 192.168.19.95 195.75.145.0/24 dev eth0 proto kernel scope link src 195.75.145.122 default via 195.75.145.1 dev eth0 broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1 local 195.75.145.122 dev eth0 table local proto kernel scope host src 195.75.145.122 broadcast 192.168.19.0 dev eth2 table local proto kernel scope link src 192.168.19.95 broadcast 195.75.145.255 dev eth0 table local proto kernel scope link src 195.75.145.122 broadcast 195.75.145.255 dev lo table local proto kernel scope link src 195.75.145.120 local 195.75.145.120 dev lo table local proto kernel scope host src 195.75.145.120 local 192.168.19.95 dev eth2 table local proto kernel scope host src 192.168.19.95 broadcast 192.168.19.255 dev eth2 table local proto kernel scope link src 192.168.19.95 broadcast 195.75.145.0 dev eth0 table local proto kernel scope link src 195.75.145.122 broadcast 195.75.145.0 dev lo table local proto kernel scope link src 195.75.145.120 broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1 local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1 local 195.75.145.0/24 dev lo table local proto kernel scope host src 195.75.145.120 local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1 Regards, Massimiliano On Mon, Nov 7, 2011 at 14:59, Pandu Poluan wrote: > > On Nov 7, 2011 8:38 PM, "Massimiliano Ziccardi" < > massimiliano.zicca...@gmail.com> wrote: > >> > >> seems to be a really tricky one... > >> What does > >> tracepath 195.75.145.33 > >> give? > > > > > > Here is the output: > > > > 1: 195.75.145.33 (195.75.145.33) 0.074ms pmtu > 16436 > > 1: 195.75.145.33 (195.75.145.33) 0.039ms > reached > > 1: 195.75.145.33 (195.75.145.33) 0.028ms > reached > > > > I tried shutting down localhost with: > > > > ifconfig lo down. > > > > Now I can't ping 195.75.145.33 anymore (as all the other 195.75.145.xx > addresses). > > > > And now tracepath gives: > > > > 1: send failed > > Resume: pmtu 65535 > > > > So, for some reason, seems it always uses the 'lo' device... > > > > Any idea? > > > > I've been deploying multi-interface Linux gateways since 2008, so I'll try. > > Please post: > > - output of ip rule sh > - output of ip route sh table $t, where $t is *all* table names/numbers > you get from the first output ( "... lookup $t" ) > > Rgds, >
Re: [gentoo-user] Network problem with linux server
Maybe I found where the problem is! Shutting down lo:0 everything seems to work properly! However I need to configure lo:0 for local triangulation (balancing through RADWARE): how should I configure it to not conflict with the other network cards? Thanks! Massimiliano Ziccardi
Re: [gentoo-user] Network problem with linux server
I'm going to highlight anomalous routes, those that have no business in the local table. On Nov 7, 2011 9:14 PM, "Massimiliano Ziccardi" < massimiliano.zicca...@gmail.com> wrote: >> >> I've been deploying multi-interface Linux gateways since 2008, so I'll try. >> Please post: >> - output of ip rule sh > > > # ip rule sh > 0: from all lookup local > 32766: from all lookup main > 32767: from all lookup default > > # ip route sh table 0 > 192.168.19.0/24 dev eth2 proto kernel scope link src 192.168.19.95 > 195.75.145.0/24 dev eth0 proto kernel scope link src 195.75.145.122 > default via 195.75.145.1 dev lo scope link These 3 should be in main. In addition, default must not go through dev lo. > local 195.75.145.0/24 dev lo table local proto kernel scope host src 195.75.145.120 This is also highly suspect: a subnet should be attached to an ethX dev, not dev lo. Except 127.0.0.0/8 > # ip route sh table 32766 > # ip route sh table 32767 > > Both 32766 and 32767 are empty > It's normal for 32767 to be empty, but very irregular for main to be empty. Rgds,
Re: [gentoo-user] Network problem with linux server
Am Montag, 7. November 2011, 15:20:12 schrieb Massimiliano Ziccardi: > Maybe I found where the problem is! > Shutting down lo:0 everything seems to work properly! > However I need to configure lo:0 for local triangulation (balancing through > RADWARE): how should I configure it to not conflict with the other network > cards? try assigning a netmask of 255.255.255.255 to it. > Thanks! > Massimiliano Ziccardi Best, Michael
Re: [gentoo-user] Network problem with linux server
> > try assigning a netmask of 255.255.255.255 to it. Seems to work! I'm asking to the network administrators if 255.255.255.255 is ok ! I'll let you know! Thank you all! Gentoo's mailing list il always the best one! Thanks!
Re: [gentoo-user] Network problem with linux server
they told me 255.255.255.255 is ok I really thank you all very much for your support! Regards, Massimiliano On Mon, Nov 7, 2011 at 15:48, Massimiliano Ziccardi < massimiliano.zicca...@gmail.com> wrote: > try assigning a netmask of 255.255.255.255 to it. > > > Seems to work! > I'm asking to the network administrators if 255.255.255.255 is ok ! > > I'll let you know! > > Thank you all! Gentoo's mailing list il always the best one! > > Thanks! > >
Re: [gentoo-user] Network problem with linux server
On Nov 7, 2011 10:17 PM, "Massimiliano Ziccardi" < massimiliano.zicca...@gmail.com> wrote: > > they told me 255.255.255.255 is ok > > I really thank you all very much for your support! > Cool! That should solve the problem of a subnet being associated to dev lo Anyways, this is also a good knowledge for me :-) Rgds,
[gentoo-user] Network problem: following gentoo diskless howto for PXE diskless systems
Hi, I am following the gentoo diskless howto for PXE diskless systems but I cant seem to stop the slave from restarting its network partway through and losing its root fs (if I have the problem correct). I am using "config_eth0=( "noop" )" as suggested in the howto but the network still seems to startup, getting a new dhcp lease with a blank rootpath=, after which init fails: #_ ip-config: Complete: device= ... lot of text that looks ok ... bootserver=192.168.1.1, rootserver=192.168.1.1,rootpath= ... VFS: Mounted root (nfs filesystem) readonly ... kernel panic: - not syncing: No init found. Try passing ... #_ Hints? BillK -- William Kenworthy <[EMAIL PROTECTED]> Home in Perth! -- gentoo-user@lists.gentoo.org mailing list
[gentoo-user] Network problem when rebooting Fedora qemu/kvm guest on Gentoo host
Hello, I have some problem with some of my qemu/kvm guests running Fedora on a Gentoo host where my Gentoo guests works without problem. The problem that I have is that when I reboot (shutdown -r now) the Fedora guest "loses" (ifconfig does not show a IP-address) their network connections. The Gentoo guests reboots without problem. All the guests have same HW-configuration, only Name/DiskImage/MAC- addresses differ. Here some technical details: Host: DistributionGentoo Kernel 4.9.95-gentoo Qemuapp-emulation/qemu-2.11.1-r2 USE="aio bzip2 caps curl fdt filecaps gnutls jpeg lzo ncurses nls pin-upstream-blobs png sdl seccomp vhost-net vnc xattr" QEMU_SOFTMMU_TARGETS="x86_64" QEMU_USER_TARGETS="x86_64" libvirt app-emulation/libvirt-4.3.0 USE="caps dbus libvirtd nls qemu udev" Guest DistributionFedora 28 Kernel 4.16.15-300.fc28.x86_64 Networkmanager NetworkManager.x86_64 1:1.10.8-1.fc28 Any suggestions? -- Dan Johansson *** This message is printed on 100% recycled electrons! *** 0x17EB372A2FB894AD.asc Description: application/pgp-keys smime.p7s Description: S/MIME Cryptographic Signature
Re: [gentoo-user] Network problem: following gentoo diskless howto for PXE diskless systems
William Kenworthy <[EMAIL PROTECTED]> writes: > > I am using "config_eth0=( "noop" )" as suggested in the howto but the > network still seems to startup, getting a new dhcp lease with a blank > rootpath=, after which init fails: > Does it work if you don't start net.eth0 with the init scripts? That is how I got my diskless nodes to boot and they all have network access without problems: rc-update show | grep net.eth0 net.eth0 | Cheers, Roger -- gentoo-user@lists.gentoo.org mailing list
