Thread: [SSI-users] can't access public nic
Brought to you by:
brucewalker,
rogertsang
Menu
▾
▴
ssic-linux-users
|
From: jhansen <jef...@gm...> - 2009-03-28 00:44:03
|
Hi, I am attempting to install open ssi on lenny. I have 2 nics on #1 node. I can't seem to access the public internet from my root node... >From my base Linux install I did the following: I have configured my "public" nic to use dchp and it resolves to a typical class "C" config on eth0. ip address is 192.168.0.70, with 192.168.0.1 as the gateway. I configured a static class "A" address on my "private" eth1 nic. 10.0.0.2. mask 255.0.0.0 gateway 10.0.0.2. I verified connectivity to public nic with google, and private nic with ping. I installed openssi per the instructions for Lenny and selected the "private" eth1 nic as the interconnect. The installation seemed to work but access to public intenet is broken and network config seems strange. Typing "route" I see only 1 entry for the 10.0.0.0 network and that is on eth0 (shouldnt that be eth1?). Any suggestions? Thank in advance. -- View this message in context: http://www.nabble.com/can%27t-access-public-nic-tp22751847p22751847.html Sent from the ssic-linux-users mailing list archive at Nabble.com. |
|
From: John H. <john@Calva.COM> - 2009-03-28 10:02:49
|
jhansen wrote: > Hi, > I am attempting to install open ssi on lenny. I have 2 nics on #1 node. I > can't seem to access the public internet from my root node... > > >From my base Linux install I did the following: > I have configured my "public" nic to use dchp and it resolves to a typical > class "C" config on eth0. ip address is 192.168.0.70, with 192.168.0.1 as > the gateway. > > I configured a static class "A" address on my "private" eth1 nic. 10.0.0.2. > mask 255.0.0.0 gateway 10.0.0.2. > I verified connectivity to public nic with google, and private nic with > ping. > > I installed openssi per the instructions for Lenny and selected the > "private" eth1 nic as the interconnect. The installation seemed to work but > access to public intenet is broken and network config seems strange. Typing > "route" I see only 1 entry for the 10.0.0.0 network and that is on eth0 > (shouldnt that be eth1?). > > On linux the "eth0", "eth1" names are almost randomly chosen - they simply reflect the order the nic was found by the kernel. Since the OpenSSI initrd loads the interconnect nic module first (for obvious reasons) the interconnect nic is almost guaranteed to be eth0, so your other nic is probably eth1 when using OpenSSI. Change the /etc/networks/config file, changing all references to eth0 to eth1. If you want to see what nics the kernel has found use the "ip link show" command. (Or "ifconfig -a", but ifconfig is old and crufty). Personaly I use udev to give meaningful names to my nics. (And one day I'd like OpenSSI to change the name of the interconnect nic). |
|
From: jhansen <jef...@gm...> - 2009-03-30 01:49:52
|
Hello, So I went to my /etc/network/interfaces file and switched the eth0 to eth1 and eth1 to eth0 and rebooted. Still no luck getting to my public nic. I ran ip link list and came up with the following: 1: lo <LOOPBACK, UP> .... etc... 2: sit0: <NOARP> ...etc...... link / sit 0.0.0.0 brd 0.0..0 3: eth0: <BROADCAST, MULTICAST, UP> etc.... "route" command brings back the 10.0.0.0 network on eth0 I attempted to bring up eth1 explicitely by using "ifup eth1" which resulted in: SIOCSIIFADDR: no such device eth1: Error wil getting interface flags: no such device Bind socket to interface: no such device failed to bind eth1 Any other thoughs? Thanks in advance. jhansen wrote: > > Hi, > I am attempting to install open ssi on lenny. I have 2 nics on #1 node. I > can't seem to access the public internet from my root node... > > From my base Linux install I did the following: > I have configured my "public" nic to use dchp and it resolves to a typical > class "C" config on eth0. ip address is 192.168.0.70, with 192.168.0.1 as > the gateway. > > I configured a static class "A" address on my "private" eth1 nic. > 10.0.0.2. mask 255.0.0.0 gateway 10.0.0.2. > I verified connectivity to public nic with google, and private nic with > ping. > > I installed openssi per the instructions for Lenny and selected the > "private" eth1 nic as the interconnect. The installation seemed to work > but access to public intenet is broken and network config seems strange. > Typing "route" I see only 1 entry for the 10.0.0.0 network and that is on > eth0 (shouldnt that be eth1?). > > Any suggestions? > > Thank in advance. > -- View this message in context: http://www.nabble.com/can%27t-access-public-nic-tp22751847p22775098.html Sent from the ssic-linux-users mailing list archive at Nabble.com. |
|
From: John H. <john@Calva.COM> - 2009-03-30 08:01:10
|
jhansen wrote: > Hello, > > So I went to my /etc/network/interfaces file and switched the eth0 to eth1 > and eth1 to eth0 and rebooted. Still no luck getting to my public nic. > I ran ip link list and came up with the following: > 1: lo <LOOPBACK, UP> .... etc... > 2: sit0: <NOARP> ...etc...... link / sit 0.0.0.0 brd 0.0..0 > 3: eth0: <BROADCAST, MULTICAST, UP> etc.... > > So the kernel doesn't think your second nic exists. What type is it? Maybe we don't have a driver for it? What does lspci show? |
|
From: <jef...@gm...> - 2009-03-31 03:04:25
|
lspci shows among other things, both nics: private nic: is 3COM 3c905 B 100base TX (rev 30) public nic: is Intell Ethernet Pro 100 (rev 08). On Mar 30, 2009 2:00am, John Hughes <jo...@ca...> wrote: > jhansen wrote: > Hello, > So I went to my /etc/network/interfaces file and switched the eth0 to eth1 > and eth1 to eth0 and rebooted. Still no luck getting to my public nic. > I ran ip link list and came up with the following: > 1: lo .... etc... > 2: sit0: ...etc...... link / sit 0.0.0.0 brd 0.0..0 > 3: eth0: etc.... > So the kernel doesn't think your second nic exists. > What type is it? Maybe we don't have a driver for it? > What does lspci show? |
|
From: jhansen <jef...@gm...> - 2009-03-31 03:11:13
|
I had that backwords lspci shows among other things, both nics: public nic: is 3COM 3c905 B 100base TX (rev 30) private nic: is Intell Ethernet Pro 100 (rev 08). sorry for te double post -- View this message in context: http://www.nabble.com/can%27t-access-public-nic-tp22751847p22797524.html Sent from the ssic-linux-users mailing list archive at Nabble.com. |
|
From: John H. <john@Calva.COM> - 2009-03-31 08:20:11
|
jef...@gm... wrote: > lspci shows among other things, both nics: > > private nic: is 3COM 3c905 B 100base TX (rev 30) > public nic: is Intell Ethernet Pro 100 (rev 08). And is the module for the public loaded? This sounds a lot like the problem Sergi Barroso <hi...@li...> was having - maybe I've screwed up my lenny instructions somewhere. What do you have in /etc/udev/rules.d? |
|
From: jhansen <jef...@gm...> - 2009-04-01 03:31:23
|
And is the module for the public loaded?
--> in /etc/mkinitrd/modules? I just have the interconnect per my
instructions so, no. I can try reinstall again and add 3C509?
What do you have in /etc/udev/rules.d?
-->There is nothing in this directory.
------------------------------------------------------------------------------
_______________________________________________
Ssic-linux-users mailing list
Ssi...@li...
https://lists.sourceforge.net/lists/listinfo/ssic-linux-users
--
View this message in context: http://www.nabble.com/can%27t-access-public-nic-tp22751847p22819190.html
Sent from the ssic-linux-users mailing list archive at Nabble.com.
|
|
From: Sergi B. <hi...@li...> - 2009-04-01 06:06:11
|
jhansen escribió: > And is the module for the public loaded? > --> in /etc/mkinitrd/modules? I just have the interconnect per my > instructions so, no. I can try reinstall again and add 3C509? > > What do you have in /etc/udev/rules.d? > -->There is nothing in this directory. > > ------------------------------------------------------------------------------ > _______________________________________________ > Ssic-linux-users mailing list > Ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > > > > Hi! I also put all my nic drivers in /etc/mkinitrd/modules, and not deleted udev rules files, if you want I can send it to you, or maybe you want to reinstall it. -- Sergi Barroso Linux user #313577 PGPID: D318F5E8 http://www.lionclan.org |
|
From: John H. <john@Calva.COM> - 2009-04-01 08:58:59
|
Sergi Barroso wrote: > I also put all my nic drivers in /etc/mkinitrd/modules, and not deleted > udev rules files, if you want I can send it to you, or maybe you want to > reinstall it. > Do you get udev errors on boot? |
|
From: John H. <john@Calva.COM> - 2009-04-01 08:58:19
|
jhansen wrote: > And is the module for the public loaded? > --> in /etc/mkinitrd/modules? No, I meant does it show up in lsmod. And if it's not does the nic show up if you do a modprobe. > I just have the interconnect per my > instructions so, no. I can try reinstall again and add 3C509? > Shouldn't need to. It should be loaded by udev > What do you have in /etc/udev/rules.d? > -->There is nothing in this directory. > And this is the problem. In my instructions it says to delete /etc/udev/rules.d *before* doing the apt-get dist-upgrade. The dist-upgrade is supposed to load a new (older) version of udev that should load its own rules. Something seems to be going wrong. I'm going to have to try this out myself today. I'll get back to you when I have more information. |
|
From: Sergi B. <hi...@li...> - 2009-04-01 10:15:16
|
John Hughes escribió: > jhansen wrote: > >> And is the module for the public loaded? >> --> in /etc/mkinitrd/modules? >> > No, I meant does it show up in lsmod. And if it's not does the nic show > up if you do a modprobe. > >> I just have the interconnect per my >> instructions so, no. I can try reinstall again and add 3C509? >> >> > Shouldn't need to. It should be loaded by udev > >> What do you have in /etc/udev/rules.d? >> -->There is nothing in this directory. >> >> > And this is the problem. > > In my instructions it says to delete /etc/udev/rules.d *before* doing > the apt-get dist-upgrade. The dist-upgrade is supposed to load a new > (older) version of udev that should load its own rules. Something seems > to be going wrong. > > I'm going to have to try this out myself today. I'll get back to you > when I have more information. > > > ------------------------------------------------------------------------------ > _______________________________________________ > Ssic-linux-users mailing list > Ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-users > Downgrading udev don't load old rules version, the solution is don't delete it. -- Sergi Barroso Linux user #313577 PGPID: D318F5E8 http://www.lionclan.org |
|
From: John H. <john@Calva.COM> - 2009-04-01 10:51:35
|
Sergi Barroso wrote: > Downgrading udev don't load old rules version, the solution is don't > delete it. > > This is really wierd. I'm going to get around to checking it out later. |
|
From: John H. <john@Calva.COM> - 2009-04-01 14:50:40
|
Sergi Barroso wrote:
> Downgrading udev don't load old rules version, the solution is don't
> delete it.
>
>
Well, the problem is both simpler and harder than I thought.
In my instructions I have:
...
1. As we're going to downgrade udev we must zap all rules our old
version isn't smart enough to handle:
rm /etc/udev/rules.d/*
2. As we're going to remove the running kernel we must modprobe all
modules needed to build the initrd or we won't be able to make a
bootable system (*don't forget this or you'll be stuck with an
unbootable system*):
modprobe loop
modprobe ext2
3.
apt-get dist-upgrade
At this point you will be warned that the running kernel will be
removed. This is because of a necessary downgrade of udev. Allow
it to happen.
:-( Warning - your system is unbootable starting from this point.
But, in fact,udev *is not* downgraded when we do the apt-get
dist-upgrade. It looks like apt has been modified to use the same
algorithm as aptitude and not consider downgrades when we ask it to upgrade.
An extra step has to be added, before the "apt-get dist-upgrade" we need
a "apt-get install udev" which will force the install of our old version
of udev.
There is still a problem with the creation of the rules.d directory, but
at least that should get things working better.
|
|
From: Sergi B. <hi...@li...> - 2009-04-01 20:46:13
|
John Hughes escribió: > Sergi Barroso wrote: >> Downgrading udev don't load old rules version, the solution is don't >> delete it. >> >> > Well, the problem is both simpler and harder than I thought. > > In my instructions I have: > > ... > > 1. As we're going to downgrade udev we must zap all rules our old > version isn't smart enough to handle: > rm /etc/udev/rules.d/* > > 2. As we're going to remove the running kernel we must modprobe all > modules needed to build the initrd or we won't be able to make a > bootable system (*don't forget this or you'll be stuck with an > unbootable system*): > modprobe loop > modprobe ext2 > > 3. > apt-get dist-upgrade > > At this point you will be warned that the running kernel will be > removed. This is because of a necessary downgrade of udev. > Allow it to happen. > > :-( Warning - your system is unbootable starting from this point. > > But, in fact,udev *is not* downgraded when we do the apt-get > dist-upgrade. It looks like apt has been modified to use the same > algorithm as aptitude and not consider downgrades when we ask it to > upgrade. > > An extra step has to be added, before the "apt-get dist-upgrade" we > need a "apt-get install udev" which will force the install of our old > version of udev. > > There is still a problem with the creation of the rules.d directory, > but at least that should get things working better. > > > ok, cool! as easy as this :D Thanks John, I'll try it on friday.... -- Sergi Barroso Linux user #313577 PGPID: D318F5E8 http://www.lionclan.org |
|
From: John H. <john@Calva.COM> - 2009-04-02 10:23:29
|
I've updated the instructions at http://deb.openssi.org/alpha/openssi-lenny/ to cope with the changes in apt-get's behaviour and show how to set up the udev/rules.d directory correctly. The important bit is: 1. apt-get dist-upgrade This should replace all the standard versions of the packages by our modified versions. However apt-get seems to have changed its behaviour, it no longer considers some downgrades, so now we have to do: 2. apt-get install udev At this point you will be warned that the running kernel will be removed. This is because of a necessary downgrade of udev. Allow it to happen. :-( Warning - your system is unbootable starting from this point. (We only need this step because apt-get seems not to notice that udev needs downgrading on an "apt-get dist-upgrade", it used to work. This is annoying). 3. As the udev install is not smart enough to fix it's configuration files after a downgrade we need to do it manualy: rm /etc/udev/rules.d/* sh -c 'source /var/lib/dpkg/info/udev.postinst abort-deconfigure; create_rules_symlink' Admittedly the shell command is rather barbaric, but it does the job. |
|
From: jhansen <jef...@gm...> - 2009-04-04 03:22:16
|
Hi,
I got to this point:
apt-get install udev
and the program said udev is already at latest version and did not install
anything and my kernal was not replaced.
rm /etc/udev/rules.d/*
sh -c 'source /var/lib/dpkg/info/udev.postinst abort-deconfigure;
create_rules_symlink'
When I ran the above sh command I recieved an error "command
create_rules_symlink not found"
What do you think?
--
View this message in context: http://www.nabble.com/can%27t-access-public-nic-tp22751847p22879688.html
Sent from the ssic-linux-users mailing list archive at Nabble.com.
|
|
From: John H. <john@Calva.COM> - 2009-04-04 12:11:13
|
jhansen wrote: > Hi, > I got to this point: > apt-get install udev > > and the program said udev is already at latest version and did not install > anything and my kernal was not replaced. > > rm /etc/udev/rules.d/* > sh -c 'source /var/lib/dpkg/info/udev.postinst abort-deconfigure; > create_rules_symlink' > > When I ran the above sh command I recieved an error "command > create_rules_symlink not found" > > What do you think? > dpkg -l udev says what? |
|
From: jhansen <jef...@gm...> - 2009-04-04 18:09:43
|
dpkg -l udev says what? Desired = Unknown/Install/Remove/Purge/Hold|Status=Not/Inst/Cfg-files/Unpacked/Failed-cfd/Half-inst/trig-aWait/Trig-Pend|Err?=(none)/Hold/Reinst-required/x=both-problems(Status,Err: uppercase = bad) udev 0.125-7 /dev/ add hotplug management daemon Also, question the Pin Priority am I supposed 1000 or 1001? I've done it both ways with the same results so far. -- View this message in context: http://www.nabble.com/can%27t-access-public-nic-tp22751847p22886261.html Sent from the ssic-linux-users mailing list archive at Nabble.com. |
|
From: John H. <john@Calva.COM> - 2009-04-06 08:28:38
|
jhansen wrote: > dpkg -l udev > > says what? > > Desired = > Unknown/Install/Remove/Purge/Hold|Status=Not/Inst/Cfg-files/Unpacked/Failed-cfd/Half-inst/trig-aWait/Trig-Pend|Err?=(none)/Hold/Reinst-required/x=both-problems(Status,Err: > uppercase = bad) > > udev 0.125-7 /dev/ add hotplug management daemon > > > Also, question the Pin Priority am I supposed 1000 or 1001? I've done it > both ways with the same results so far. > You've still got the wrong udev installed. pin-priority should be 1001 What is the output of "apt-cache policy udev" Please post your /etc/apt/preferences and /etc/apt/source.list files. |
|
From: jhansen <jef...@gm...> - 2009-04-07 03:11:54
|
What is the output of "apt-cache policy udev"
udev:
Installed: 0.125-7
Candidate: 0.125-7
Version table
***0.125-7 -
500 http://ftp.us.debian.org lenny/main Packages
100 /var/lib/dpkg/status
0.080-1 0
1000 http://deb.openssi.org./ Packages
Please post your /etc/apt/preferences
(note: i created this file from scratch as it was not present.
--------------------preferences---------------------
Package: *
Pin: origin deb.openssi.org.org
Pin-Priority:1000 (i've had this both ways, i'll set back to 1001 per
above)
-----------------------------------------------------
and /etc/apt/source.list files.
----------------------sources.list------------------------------
# deb http://ftps.us.gebian.org/debian lenny main
deb http://ftp.us.debian.org/debian/ lenny main
deb-src http://ftp.us.debian.org/debian/ lenny main
deb http://security.debian.org/ lenny/updates main
deb-src http://security.debian.org/ lenny/updates main
deb http://volatile.debian.org/debian-volatile lenny/volatile main
deb-src http://volatile.debian.org/debian-volatile lenny/volatile main
deb http://deb.openssi.org/alpha/openss-lenny ./
deb http://deb.openssi.org/alpha/openssi-lenny-extras ./
---------------------------------------------------
(forgive any minor typos, I typed these instead of trying to pull them off
the server as my public nic is not working ;) )
--
View this message in context: http://www.nabble.com/can%27t-access-public-nic-tp22751847p22921448.html
Sent from the ssic-linux-users mailing list archive at Nabble.com.
|
|
From: John H. <john@Calva.COM> - 2009-04-07 08:24:34
|
jhansen wrote: > What is the output of "apt-cache policy udev" > > > udev: > Installed: 0.125-7 > Candidate: 0.125-7 > Version table > ***0.125-7 - > 500 http://ftp.us.debian.org lenny/main Packages > 100 /var/lib/dpkg/status > 0.080-1 0 > 1000 http://deb.openssi.org./ Packages > So do an "apt-get install udev" to install version 0.80-1 > > Please post your /etc/apt/preferences > (note: i created this file from scratch as it was not present. > --------------------preferences--------------------- > Package: * > Pin: origin deb.openssi.org.org > Pin-Priority:1000 (i've had this both ways, i'll set back to 1001 per > above) > ----------------------------------------------------- > Yup, should be 1001 > > > and /etc/apt/source.list files. > > ----------------------sources.list------------------------------ > # deb http://ftps.us.gebian.org/debian lenny main > > deb http://ftp.us.debian.org/debian/ lenny main > deb-src http://ftp.us.debian.org/debian/ lenny main > > deb http://security.debian.org/ lenny/updates main > deb-src http://security.debian.org/ lenny/updates main > > deb http://volatile.debian.org/debian-volatile lenny/volatile main > deb-src http://volatile.debian.org/debian-volatile lenny/volatile main > Do you need this? Why? > deb http://deb.openssi.org/alpha/openss-lenny ./ > deb http://deb.openssi.org/alpha/openssi-lenny-extras ./ > Good. > --------------------------------------------------- > > (forgive any minor typos, I typed these instead of trying to pull them off > the server as my public nic is not working ;) ) > |
|
From: jhansen <jef...@gm...> - 2009-04-08 03:34:33
|
Getting closer but still not quite there.
So do an "apt-get install udev" to install version 0.80-1
ok, this worked this time (wiered it didn't work first time i verified
that i did run it previously). and I got the warning message and installed
new packages. dpkg -l udev now shows version 0.80-1
> deb http://volatile.debian.org/debian-volatile lenny/volatile main
> deb-src http://volatile.debian.org/debian-volatile lenny/volatile main
>
Do you need this? Why?
This was here as part of the install. I commented this out.
I when to run the shell command line and I am still getting
"sh: create_rules_symlink: ommand not found."
--
View this message in context: http://www.nabble.com/can%27t-access-public-nic-tp22751847p22942406.html
Sent from the ssic-linux-users mailing list archive at Nabble.com.
|
|
From: John H. <john@Calva.COM> - 2009-04-08 09:43:45
|
jhansen wrote:
> I when to run the shell command line and I am still getting
> "sh: create_rules_symlink: ommand not found."
>
>
This is so frustrating - I don't see why it works for me and not for you.
What does:
grep symlink /var/lib/dpkg/info/udev.postinst
show?
(For me it's:
# grep symlink /var/lib/dpkg/info/udev.postinst
# create a default symlink if the directory exists and is empty
create_rules_symlink() {
# make symlinks to the sockets and pipes on the old /dev
create_rules_symlink
|
|
From: jhansen <jef...@gm...> - 2009-04-08 15:29:06
|
.
What does:
grep symlink /var/lib/dpkg/info/udev.postinst
show?
(For me it's:
# grep symlink /var/lib/dpkg/info/udev.postinst
# create a default symlink if the directory exists and is empty
create_rules_symlink() {
# make symlinks to the sockets and pipes on the old /dev
create_rules_symlink
I got the same as you. So, I did the following from bash shell:
. /var/lib/dpkg/info/udev.postinst abort-deconfigure (return)
create_rules_symlink (return)
That seemed to work and I've got rules.d populated now. Next step is to
install openssi, i'll do that tonight and let you know how it worked.
Thanks!
--
View this message in context: http://www.nabble.com/can%27t-access-public-nic-tp22751847p22952958.html
Sent from the ssic-linux-users mailing list archive at Nabble.com.
|
Thanks for helping keep SourceForge clean.
X