On Sun, 11 Jun 2017 17:03:40 +0900
Joel Rees wrote:
> On Sun, Jun 11, 2017 at 4:57 PM, Joe wrote:
> >
> > I've seen this kind of behaviour a very long time ago, and I can't
> > really believe it is still happening, but...
>
> See the other sub-thread. But it does go to class C instead of the
On Sun, Jun 11, 2017 at 4:57 PM, Joe wrote:
> On Sat, 10 Jun 2017 10:57:47 +0900
> Joel Rees wrote:
>
>> Experimenting from the command line, I find myself puzzled about the
>> arguments for ifconfig.
>>
>> Reading the manual, it would appear that the arguments for ifconfig
>> should be something
On Sat, 10 Jun 2017 10:57:47 +0900
Joel Rees wrote:
> Experimenting from the command line, I find myself puzzled about the
> arguments for ifconfig.
>
> Reading the manual, it would appear that the arguments for ifconfig
> should be something like this:
>
> ifconfig eth0 netmask 255.255.255
I now have connection for both the wireless and the netbook that is acting
as the AP. I took out the bridge entirely, quit trying to play with
port forwarding,
just used dead simple setup. dnsmasq was the only missing piece, if I had
not been focusing on bridging. Bridging is probably for the othe
Sorry my typing is so lame.
On Sat, Jun 10, 2017 at 10:57 AM, Joel Rees wrote:
> Experimenting from the command line, I find myself puzzled about the
> arguments for ifconfig.
>
> Reading the manual, it would appear that the arguments for ifconfig
> should be something like this:
>
> ifconfig
I posted the following to Randy, yesterday, intending it to go to the list.
I'll post it back to the list (with Randy's permission), with a bit of further
comment:
> On Friday, June 09, 2017 02:14:17 AM Joel Rees wrote:
>> (With aplogies for html mail)
>>
>> 2017/06/08 23:46 :
>> > On Thursday, Ju
Experimenting from the command line, I find myself puzzled about the
arguments for ifconfig.
Reading the manual, it would appear that the arguments for ifconfig
should be something like this:
ifconfig eth0 netmask 255.255.255.224 netmask 255.255.255.224
broadcast 10.19.23.223 10.19.23.94
But
On Thu, Jun 08, 2017 at 08:31:04PM +0200, didier gaumet wrote:
> Le 08/06/2017 à 16:00, Joel Rees a écrit :
> > On Thu, Jun 8, 2017 at 5:03 PM, didier gaumet
> > wrote:
> [...]
> >>
> >> https://wiki.debian.org/BridgeNetworkConnections#Bridging_with_a_wireless_NIC
> >
> > Maybe I'm misundersta
Le 08/06/2017 à 16:00, Joel Rees a écrit :
> On Thu, Jun 8, 2017 at 5:03 PM, didier gaumet wrote:
[...]
>>
>> https://wiki.debian.org/BridgeNetworkConnections#Bridging_with_a_wireless_NIC
>
> Maybe I'm misunderstanding that wiki, but it seems to be describing this
> kind of setup:
>
>WAN <
On Thursday, June 08, 2017 10:00:17 AM Joel Rees wrote:
> Maybe I'm misunderstanding that wiki, but it seems to be describing this
> kind of setup:
>
>WAN <--> foreign AP <-wireless-> debian box <-> more devices
>
> But what I'm wanting is
>
>WAN <-wired-> router/modem <-wired-> debian n
On Thu, Jun 8, 2017 at 5:03 PM, didier gaumet wrote:
> Le 08/06/2017 à 02:29, Joel Rees a écrit :
>
> [...]
>> # Setup bridge
>> iface br0 inet manual
>> bridge_ports wlan0 eth0:0
> [...]
>
> I am sorry, network wise, I am a true dumb, so I cannot be of a great
> help, but:
>
> - the Archlinux
A little more detail, with the following pair of configurations, I get
on the boot console,
Configuring network interfaces...can't add wlan0 to bridge br0:
Operation not supported
SIOCSIFFLAGS: Cannot assign requested address
SIOCSIFFLAGS: Cannot assign requested address
Waiting for b
Le 08/06/2017 à 02:29, Joel Rees a écrit :
[...]
> # Setup bridge
> iface br0 inet manual
> bridge_ports wlan0 eth0:0
[...]
I am sorry, network wise, I am a true dumb, so I cannot be of a great
help, but:
- the Archlinux wiki indicates that the wireless interface should not be
added to the b
On Wed, Jun 7, 2017 at 2:08 PM, Joel Rees wrote:
> On Tue, Jun 6, 2017 at 4:10 PM, didier gaumet wrote:
>> Le 06/06/2017 à 03:58, Joel Rees a écrit :
>> [...]
>> can anyone point me to a good how-to?
>> [...]
>>
>> these should do the trick:
>> https://agentoss.wordpress.com/2011/10/31/creating-a
On Tue, Jun 6, 2017 at 4:10 PM, didier gaumet wrote:
> Le 06/06/2017 à 03:58, Joel Rees a écrit :
> [...]
> can anyone point me to a good how-to?
> [...]
>
> these should do the trick:
> https://agentoss.wordpress.com/2011/10/31/creating-a-wireless-access-point-with-debian-linux/
> https://wiki.ar
On Tue, Jun 6, 2017 at 7:30 PM, Dan Ritter wrote:
> On Tue, Jun 06, 2017 at 10:58:09AM +0900, Joel Rees wrote:
>> I've seen a lot of answers that say "NOT POSSIBLE!!", as if the device
>> manufacturers really want us to believe that it can only be done on
>> MSWindows and MacOSX.
>>
>> I've seen a
On Tue, Jun 06, 2017 at 10:58:09AM +0900, Joel Rees wrote:
> I've seen a lot of answers that say "NOT POSSIBLE!!", as if the device
> manufacturers really want us to believe that it can only be done on
> MSWindows and MacOSX.
>
> I've seen a bit of talk about what appears to me to be the reverse o
Le 06/06/2017 à 03:58, Joel Rees a écrit :
[...]
can anyone point me to a good how-to?
[...]
these should do the trick:
https://agentoss.wordpress.com/2011/10/31/creating-a-wireless-access-point-with-debian-linux/
https://wiki.archlinux.org/index.php/Software_access_point
http://oob.freeshell.org/
18 matches
Mail list logo
